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

Including a template in your application

You will recall from the previous chapters that we had several templates for different tiers. We had core (network and security), web (frontend), middleware (backend), and database tiers.

So far, we haven’t stored our templates in the version control system, but since we need to apply CD, we need to figure out the proper way to store them. Normally, it all depends on how you want to organize your workflow. If you have a separate operations or cloud team that is responsible for infrastructure and operations, it is wise to keep all the templates in a single repository. Developers will then supply you with any desired changes to the infrastructure or with the new version of the application.

Our flow is as follows:

  1. The developer publishes a new version of an app.
  2. The developer provides the operations team with the new version and/or changes.
  3. The operations team makes changes to parameters and/or templates.
  4. The operations...