If you’ve spent any time in the land of DevOps over the last few years you will have no doubt heard of the term “Infrastructure as Code”… The idea of defining your infrastructure environment in source code so that it’s easier to track changes and manage versions over time.
An automated solution in a cost effective way to have RDS snapshots shared on a timed schedule with different AWS accounts in order to centrally manage the data also in a different location. The solution mainly caters for standing an infrastructure and bringing the system back to continue the operations for the business continuity within the approved RPO and RTO when any of the disaster events kicks in.
In the final part of this series, I will demonstrate how to configure EC2 Instance Metadata Service (IMDS) through the use of AWS Systems Manager (SSM) Run Commands using a tag based approach to target EC2 instances to run our IMDS commands against. In addition, I will look at automating this process using EventBridge to maintain IMDS on a periodic basis.
In this two-part series, I will explain and demonstrate how to update your EC2 instances to use IMDSv2 as well as automate this process through the use of SSM Documents that can be provisioned within your CloudFormation templates.
In this post we look at one of the most common problems Terraform encounters – managing rolling updates to AWS AutoScaling Groups – and how you can utilise CloudFormation to solve this.