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

Creating reusable templates

We already know that we are going to deploy a three-tier application, but we’re going to have more than three stacks.

The first stack we will create is our core stack.

This stack will consist of the following:

  • Network (VPC, subnets, and so on)
  • IAM (roles and users)

We will have two environments for our application: test and production. These environments will differ in terms of size, the amount of resources, and security settings.

The code of our templates is going to be huge, so you will only see blocks that are specific to the topic; the entire source code can be found in Packt’s repository.

Before we start, let’s think about how we are going to organize the template and its parameters. Since we are going to reuse the same template for two different stacks (production and test), we will need to separate the network ranges and use different naming conventions.

In terms of network, our stack will have...