Infrastructure & Automation

Category: AWS CloudFormation

screenshot of code

Conditionally launch AWS CloudFormation resources based on user input

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.

Read More
two region diagram with lambda zip files bucket in region 1

Deploying AWS Lambda functions using AWS CloudFormation (the portable way)

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.

Read More