Common Issues

The following is a compilation of common issues encountered throughout the stack creation process.

Instance Type is Not Supported in Availability Zone

The following message occurs when a specific instance type is not available in a given availability zone. To correct, re-launch the stack and select subnets that do not correspond to the unavailable zone.

Your requested instance type (m3.medium) is not supported in your requested Availability Zone (us-east-1c).
Please retry your request by not specifying an Availability Zone or choosing us-east-1a, us-east-1b, us-east-1e, us-east-1d.

---

Cannot create a db.m3.medium Multi-AZ instance

The following message occurs in the nested RDS CloudFormation stack on Professional and Enterprise builds when attempting to launch in subnets not compatible with the default db.m3.medium RDS type. To correct, re-launch the stack and select from one of the recommended subnets/availability zones referenced in the message.

Cannot create a db.m3.medium Multi-AZ instance because at least 2 subnets must exist in availability zones with sufficient capacity for VPC and storage type : standard for db.m3.medium, so 1 more must be created in other availability zones; choose from these availability zones: us-east-1e, us-east-1a, us-east-1d.