EC2 - out of capacity

When you encounter an "EC2 is out of capacity" error with your EMR cluster, it means AWS currently doesn't have enough available capacity of the requested instance type (m6a.12xlarge) in the specified Availability Zone (us-east-1c). This is a temporary condition that occurs when demand for a specific instance type exceeds available supply in a particular location.

Since you've already tried different machines in the same region, different regions, and different time zones without success, here are some additional approaches to resolve this issue:

1. Try a different instance type with similar capabilities to m6a.12xlarge. Look for instance types that have comparable CPU, memory, and network performance characteristics.

2. Select a subnet in a different Availability Zone within the same region. For example, if you're currently using us-east-1c, try us-east-1a or us-east-1b instead.

3. Consider modifying your instance group or fleet configurations to include multiple instance types with similar capabilities. This gives EMR more flexibility to fulfill your capacity request.

4. If you're using a specific subnet that resolves to us-east-1c, choose a different subnet that resolves to another Availability Zone where the instance type might be available.

5. If you have flexibility with timing, you can wait and retry later as capacity fluctuates frequently.

When troubleshooting a failed EMR cluster due to capacity issues, you can check the ErrorDetail information returned from the DescribeCluster and ListClusters APIs to get more specific information about which instance type and Availability Zone are affected.
Sources
Amazon EMR cluster error: EC2 is out of capacity - Amazon EMR
INTERNAL_ERROR_EC2_INSUFFICIENT_CAPACITY_AZ - Amazon EMR