Building a Modular and Scalable Virtual Network Architecture with Amazon VPC
VPC Quick Start


When you deploy the Quick Start, if you encounter a CREATE_FAILED error instead of the CREATE_COMPLETE status code, we recommend that you relaunch the template with Rollback on failure set to No. (This setting is under Advanced in the AWS CloudFormation console, Options page.) With this setting, the stack’s state will be retained and the instance will be left running, so you can troubleshoot the issue. (You'll want to look at the log files in %ProgramFiles%\Amazon\EC2ConfigService and in the C:\cfn\log folder.)


When you set Rollback on failure to No, you'll continue to incur AWS charges for this stack. Please make sure to delete the stack when you've finished troubleshooting.

The following table lists specific CREATE_FAILED error messages you might encounter.

Error message Possible cause What to do
API: ec2: RunInstances Not authorized for images: ami-ID The template is referencing an AMI that has expired. We refresh AMIs on a regular basis, but our updates sometimes lag behind AWS AMI changes. If you get this error message, notify us, and we’ll update the template with the new AMI ID.

If you’d like to fix the template yourself, you can download it and update the Mappings section with the latest AMI ID for your region.

We currently do not have sufficient instance-type capacity in the AZ you requested The NAT instance requires a larger or different instance type Switch to an instance type that supports higher capacity. If a higher-capacity instance type isn’t available, try a different Availability Zone or region. Or you can complete the request form in the AWS Support Center to increase the Amazon EC2 limit for the instance type or region. Limit increases are tied to the region they were requested for.
Instance ID did not stabilize You have exceeded your IOPS for the region. Request a limit increase by completing the request form in the AWS Support Center.

If you encounter a template validation error during deployment, check for a mismatch in the values of the Availability Zones and Number of Availability Zones parameters. If you select more Availability Zones than you request, the AWS CloudFormation template won’t validate. Correct the parameters so that they’re in sync, and re-deploy the Quick Start.

For additional information, see Troubleshooting AWS CloudFormation on the AWS website. If the problem you encounter isn’t covered on that page or in the table, please visit the AWS Support Center. If you’re filing a support ticket, please attach the install.log file from the master instance (this is the log file that is located in the /root/install folder) to the ticket.