Exit criteria

Your Quick Start can be scheduled for publication when it meets the following criteria:

Templates meet the architectural requirements listed below.

Templates pass all tests consistently in all supported regions.

You’ve reviewed our edits and resolved all outstanding questions in the Quick Start deployment guide.

Minimum architectural requirements

Quick Starts are designed for production use and must comply with AWS best practices. You must meet the following standards and practices when designing your architecture and developing your AWS CloudFormation templates. Otherwise, we won’t be able to publish your templates as an AWS Quick Start. If you’re unable to meet these requirements, contact us to discuss your exception case.

Multi-AZ architecture (details)

Support for the majority of AWS Regions (details)

New VPC and existing VPC deployment options (details)

Product instances in private subnets (details)

NAT gateways for outbound Internet access from private subnets (details)

Marketplace AMIs whenever possible; no prebaked AMIs (details)

AMI mappings; no hardcoded AMIs (details)

User-friendly parameter labels and groups (details)

CIDR block lockdown for external admin access (details)

Security groups with principle of least privilege (details)

No software bits with deployment (details)

No hardcoded passwords (details)

No sensitive data in EC2 instance user data or other clear text (details)

No use of 0.0.0.0/0 for open remote management access (details)

No resources created automatically outside stack (details)

Quick Starts for demo use

Quick Starts can also be used for PoCs or demos, but they must still satisfy the requirements listed above for production. For example, you can include demo data as a selectable option, but you must set the default to no demo. Whenever possible, use AWS public datasets for your demo data.