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

Summary

In this chapter, we learned how to perform testing against CloudFormation stacks and what the best practices are for CD with CloudFormation.

We also created our very first pipeline using development services in AWS, such as CodeCommit, CodeBuild, and CodePipeline.

Although this pipeline is working and doing what it is supposed to do, there is always room for improvement. Ask yourself what you could add to the pipeline or change to make it more effective.

We should move the creation of the temporary stack from CodeBuild to CodePipeline as an extra stage so we can save some money since, in CodeBuild, you pay for build execution time. Simply put, while CodeBuild waits until the temporary stack has been created, the build job is being billed.

Another thing is that by using the same temporary stack name (core-tmp), we are not able to run multiple builds at the same time. If another build runs while core-tmp is being deleted by a previous build, we will receive an error...