Exit criteria

Your Partner Solution 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 Partner Solution deployment guide.

Minimum architectural requirements

Partner Solutions 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 Partner Solution. If you’re unable to meet these requirements, email us (the AWS Integration & Automation team) to discuss exceptions.

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)

Partner Solutions for demo use

While Partner Solutions can be used for proofs of concept or demos, they must still satisfy the production architectural requirements. For example, if you include demo data as a selectable option, you must set the default value of the demo option to No. Whenever possible, use AWS public datasets for your demo data.