Book Image

Mastering AWS CloudFormation

By : Karen Tovmasyan
Book Image

Mastering AWS CloudFormation

By: Karen Tovmasyan

Overview of this book

DevOps and the cloud revolution have forced software engineers and operations teams to rethink how to manage infrastructures. With this AWS book, you'll understand how you can use Infrastructure as Code (IaC) to simplify IT operations and manage the modern cloud infrastructure effectively with AWS CloudFormation. This comprehensive guide will help you explore AWS CloudFormation from template structures through to developing complex and reusable infrastructure stacks. You'll then delve into validating templates, deploying stacks, and handling deployment failures. The book will also show you how to leverage AWS CodeBuild and CodePipeline to automate resource delivery and apply continuous integration and continuous delivery (CI/CD) practices to the stack. As you advance, you'll learn how to generate templates on the fly using macros and create resources outside AWS with custom resources. Finally, you'll improve the way you manage the modern cloud in AWS by extending CloudFormation using AWS serverless application model (SAM) and AWS cloud development kit (CDK). By the end of this book, you'll have mastered all the major AWS CloudFormation concepts and be able to simplify infrastructure management.
Table of Contents (17 chapters)
1
Section 1: CloudFormation Internals
4
Section 2: Provisioning and Deployment at Scale
9
Section 3: Extending CloudFormation

Deploying to multiple accounts

Now let's begin working with multiple accounts. For this section, I've created two additional accounts in AWS Organizations: testing and production.

Important note

Since this book is not about multi-account strategies (MAS), we're not going to cover the creation of child accounts and organizational units in this book. If you need to learn about these, then you can start looking at AWS Organizations (https://aws.amazon.com/organizations/). If you don't use a multi-account strategy and don't plan to, then you may skip this section.

Since we will work in various accounts, we need to tweak our StackSet permissions template. We've separated it into two templates—one for administrator role and one for an execution role. We don't need to create an execution role in our main (or to use the terms of AWS, our payer) account, because no stack instance will be created in it.

Our StackSet administrator role is...