In this quick recap, I feature five blog posts that show how you can use custom resources to extend AWS CloudFormation templates, from start to stack cleanup, when you’re building automated deployments.
Learn how to build an AMI from an Amazon EC2 instance at CloudFormation launch time, and then use the AMI for fast bootstrapping of the Auto Scaling group instances.
While Quick Start reference architectures eliminate code that customers would have to write themselves, technology partners actively contribute to improve the standards and feature sets. As an example, read about how Alfresco achieved key enhancements to the Amazon EKS Architecture Quick Start.
In this second post of a two-part series, learn how to enhance the security of your bastion hosts by using Amazon EC2 Instance Connect. With EC2 Instance Connect, you no longer have to associate a key pair to the instance, and you don’t need to permanently add user keys to authorized keys.
Learn how to extend AWS CloudFormation by using AWS CodeBuild as a long-lived compute environment. This example is based on the AWX Quick Start.
Learn how to create robust AWS CloudFormation custom resources by using the custom resource helper (crhelper) and AWS Lambda.
David B. Schott, Senior Business Development Engineer at CloudBees, Inc., details his technology adventures building, with a tight deadline and a learning curve, a Quick Start for the CloudBees Core CI/CD product.
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.