RSSAmplifier

Hello internet · Mar 10, 2021

AWS AZs: Not all are Equal

Read inOriginalenesdefrptjaitzh
0
Sign in to vote or save

This site took too long to answer. You can still read it on the original site — the toolbar below keeps your place in the directory.

(Short version: there’s more context below, but for readers who just want to know which AZ doesn’t support Nitro, it’s use1-az3 .) What this is about Link to heading Not all AZs support all instance types Availability zone names aren’t consistent across AWS accounts Availability zone IDs are consistent across AWS accounts! How to find out which zone IDs support a given…

(Short version: there’s more context below, but for readers who just want to know which AZ doesn’t support Nitro, it’s use1-az3.)

What this is about Link to heading

  1. Not all AZs support all instance types
  2. Availability zone names aren’t consistent across AWS accounts
  3. Availability zone IDs are consistent across AWS accounts!
  4. How to find out which zone IDs support a given instance type
  5. How to automatically exclude those unsupported AZs using Terraform

Not all AZs are equal Link to heading

When choosing what AWS region to use, practitioners will often discover the AWS Regional Services List describing what services a region supports. What’s less well-known is that even within a given region, not all availability zones are equal. This is most visible for services that offer a choice of instance types such as EC2, RDS, Elasticache, etc. That’s because some AZs are older than others and don’t support newer Nitro or Graviton2 instances.

Read on wolfman.dev ↗

Comments

Nothing yet. Say the first thing.

    Sign in to join the conversation.