Availability roadmap for T3 and Nitro instance families in AZ us-east-1e

Question

Hello AWS community,

We are currently running workloads in us-east-1e utilizing previous-generation instance types (such as T2, M4, and C4). Recently, we have been encountering frequent InsufficientInstanceCapacity errors when attempting to start T2 instances in this availability zone.

**Prior Research & Steps Taken:**

We ran aws ec2 describe-instance-type-offerings filtered for us-east-1e and confirmed that current-generation Nitro-based families (such as t3, t3a, m6i, c6i) are not offered in this AZ for our account's physical mapping.

We evaluated migrating workloads to another AZ (e.g., us-east-1f), but due to requirements around retaining existing private IP addresses, recreation of subnets introduces significant operational complexity.

**Question:**
Is there any roadmap or expectation for AWS to introduce T3 or other modern Nitro-based instance types into us-east-1e? Or is us-east-1e considered a legacy physical AZ where newer hardware generations will generally not be deployed?

Any insights into AWS's hardware deployment strategy for this AZ would be greatly appreciated to help us decide between waiting or committing to a cross-AZ migration.

re:Post Agent · Answer

AWS does not publicly share roadmaps or timelines for when specific instance types will become available in particular Availability Zones. The availability of instance types can vary by AZ based on physical infrastructure and capacity planning decisions that AWS makes internally.

Regarding the instance families you mentioned: T3 instances are built on the AWS Nitro System and represent a current-generation burstable instance type offering improved performance and cost efficiency compared to T2 instances. The Nitro System is AWS's underlying platform for next-generation EC2 instances, enabling faster innovation, reduced costs, increased security, and new instance types. Nitro-based instances boot from EBS volumes using an NVMe interface and include families like M5, C5, R5, and T3, among many others.

If you're experiencing InsufficientInstanceCapacity errors with T2 instances in your current AZ and cannot access T3 or other Nitro-based instances there, your best path forward would be to contact AWS Support directly through the AWS Support Center at https://console.aws.amazon.com/support/. They can provide account-specific guidance about instance type availability in your Availability Zones and discuss potential solutions for your capacity challenges.

For immediate relief from capacity constraints, you might also consider reviewing your AWS Support plan options, as higher-tier plans can provide faster response times and more direct assistance with architectural decisions like AZ migration strategies.  
**Sources**  
[Amazon EC2 T3 Instances – Amazon Web Services (AWS)](https://aws.amazon.com/ec2/instance-types/t3/)  
[Mastering Windows Server migration to Amazon EC2: Key tactics for success – Part 2 | Microsoft Workloads on AWS](https://aws.amazon.com/blogs/modernizing-with-aws/mastering-windows-server-migration-to-amazon-ec2-key-tactics-for-success-part-2/)  
[Instances built on the AWS Nitro System - Amazon EC2](https://docs.aws.amazon.com/ec2/latest/instancetypes/ec2-nitro-instances.html)

Availability roadmap for T3 and Nitro instance families in AZ us-east-1e

Add your answer

Relevant content