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

Chapter 1: CloudFormation Refresher

  1. CreateStack.
  2. CloudFormation Service Role is an IAM Role that is assumed by CloudFormation before stack operations are performed. The policies attached to that role will be then used to perform stack operations.
  3. The ones that are attached to the IAM entity (User or Role), which run CloudFormation stack operations.
  4. This information (physical resource ID and its metadata) is stored in CloudFormation's state.
  5. If we try to create the same stack (that is, invoke the CreateStack API call), that call will fail with a 400 AlreadyExists error.
  6. If we run a stack update without any changes in a template or parameters, nothing would happen as there are no changes. CloudFormation will not notice if the resource has been deleted manually. But if we update the deleted resource, the operation will fail, because the CloudFormation resource still exists in the state and CloudFormation believes it is still there.
  7. Because CloudFormation...