Book Image

Mastering AWS CloudFormation - Second Edition

By : Karen Tovmasyan
Book Image

Mastering AWS CloudFormation - Second Edition

By: Karen Tovmasyan

Overview of this book

The advent of DevOps and the cloud revolution has compelled software engineers and operations teams to rethink how to manage complex infrastructures and build resilient solutions. With this AWS book, you’ll find out how you can use Infrastructure as Code (IaC) to simplify infrastructure operations and manage the modern cloud with AWS CloudFormation. This guide covers AWS CloudFormation comprehensively, from template structures to developing complex and reusable infrastructure stacks. It takes you through template validation, stack deployment, and handling deployment failures. It also demonstrates the use of AWS CodeBuild and CodePipeline for automating resource delivery and implementing continuous integration and continuous delivery (CI/CD) practices. As you advance, you’ll learn how to modularize and unify your template on the fly using macros or by fixating the version using modules. You’ll create resources outside of AWS with custom resources and catalog them with the CloudFormation registry. Finally, you’ll improve the way you manage the modern cloud environment on AWS by extending CloudFormation through the AWS serverless application model (SAM) and the AWS cloud development kit (CDK). By the end of this book, you’ll have mastered key AWS CloudFormation concepts and will be able to extend its capabilities for developing and deploying your own infrastructure.
Table of Contents (19 chapters)
Free Chapter
1
Part 1: CloudFormation Internals
4
Part 2: Provisioning and Deployment at Scale
9
Part 3: Extending CloudFormation

The legacy way of multi-regional and multi-account infrastructure management

Until now, our stack deployment was primarily focused on provisioning resources within a single AWS account and region. But what if we needed to provision the same stack in several regions? Let’s say we need to provision the same stack in Ireland, North Virginia, and Frankfurt.

Usually, the default region (for example, the API endpoint that we want to connect to) is chosen either from environment variables or from a local config file. When you invoke any command via awscli, it will connect to that specific default region.

We can also specify the region manually as an argument. So, if we want to provision the same stack in different regions, we have to repeat the same command that changes the argument value, as illustrated here:

aws cloudformation deploy --region eu-west-1 --template-file foo.yamlaws cloudformation deploy --region us-east-1 --template-file foo.yaml
aws cloudformation deploy...