I'm expanding my VPC by adding a few more availability zones in US-East-1, specifically 1e and 1f. I've noticed that there are no Graviton instances available at any size within the 1e zone, which I usually utilize for T4g instances. Is this just a glitch, or has this availability zone been neglected?
5 Answers
AWS uses an API to show availability based on AZs. If you're curious, you can run a command that lists available instance types in your specific AZ, letting you see what's up with the T4g offering in your region. Just keep in mind that not all AZs support every instance type.
Good to know, I’ll definitely remember that.
It's interesting how availability zones can feel random sometimes! Just so you know, AZ identifiers like 1e can differ from user to user. There’s a theory that AWS could be winding down the T series as they haven’t released new ones since 2019. I asked about this in another thread and got quite the backlash for even considering using T series anymore. Pretty wild!
Hey, don't worry about it! Everyone has different needs, right? Not everyone runs the same workload.
Yeah, if I remember correctly, the naming is mixed up for everyone, but 1e should be the same for us all.
Honestly, I wouldn't worry too much. AZ 1e isn't neglected— it just doesn’t support all instance types like 1a or 1b. It's all about what AWS chooses to offer in each zone.
The rollout for Graviton instances can be pretty inconsistent! In some places, like Montreal, we waited for a good nine months to see full AZ coverage. It seems AWS prioritizes based on demand rather than evenly distributing these resources.
You might have stumbled upon the old AZ in US-East-1 that doesn’t seem to get new instance types regularly. It's been a consistent issue for a while now, and it could be the reason you’re not seeing Graviton instances in 1e.
That's really useful info— I'll have to try that out!