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

Summary

In this chapter, we learned how to perform testing against CloudFormation stacks and what the best practices are for Continuous Delivery 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...