Infrastructure & Automation

See best practices that you can apply in developing AWS Quick Starts to help gain broad customer reach and impact.

Here are two patterns that you can add to AWS CloudFormation to customize automated deployments based on values provided during the launch. The first pattern is for designing nested stacks that are optional. The second pattern allows you to change template URLs based on the current scenario.

This second post in a two-part series covers how you can streamline your automated deployments by orchestrating Windows PowerShell Desired State Configuration within AWS Systems Manager Automation documents.

In this first post of a two-part series, read about the benefits of using AWS CloudFormation and AWS Systems Manager together to streamline deployment, and outputting logs to Amazon CloudWatch for centralized troubleshooting.

Automate the documentation of AWS CloudFormation templates by using a serverless solution that eliminates the need to run local scripts.

Deploy your Quick Starts and other AWS CloudFormation templates securely at the click of a button by using the AWS IoT Button.

AWS CloudFormation nested stacks execute in the same account and AWS Region as the parent stack. This post shows you how to nest stacks in different accounts, Regions, or IAM identities.

Instead of manually cleaning up your temporary AWS CloudFormation stacks, use this mechanism to automatically delete your demonstration stacks after a specified amount of time has elapsed.

AWS Lambda requires its source code to be hosted in an Amazon S3 bucket in the same AWS Region as the Lambda function, which poses challenges when writing AWS CloudFormation templates that are portable across different regions. This post discusses three patterns to address that at stack.

The content of this post has been removed. For the most recent information, see the TaskCat documentation (https://aws-quickstart.github.io/taskcat/).