Modular and Scalable Amazon EKS Architecture
Amazon EKS Quick Start

The AWS Documentation website is getting a new look!
Try it now and let us know what you think. Switch to the new look >>

You can return to the original look by selecting English in the language selector above.


Q. I encountered a CREATE_FAILED error when I launched the Quick Start.

A. If AWS CloudFormation fails to create the stack, 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 instances will be left running, so you can troubleshoot the issue.


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

For additional information, see Troubleshooting AWS CloudFormation on the AWS website.

Q. The Custom::KubeManifest/Custom::Helm resources failed on stack create, update, or deletion.

A. These resources are backed by Lambda functions that are defined in the Functions stack. Their logs are stored in Amazon CloudWatch Logs and can be accessed by navigating to the Lambda console, selecting the relevant Lambda function and choosing Open in CloudWatch Logs.

Q. I encountered a size limitation error when I deployed the AWS CloudFormation templates.

A. We recommend that you launch the Quick Start templates from the links in this guide or from another S3 bucket. If you deploy the templates from a local copy on your computer or from a non-S3 location, you might encounter template size limitations when you create the stack. For more information about AWS CloudFormation limits, see the AWS documentation.