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

Chapter 1

  1. CreateStack is invoked; CloudFormation then calls service APIs to create stack resources.
  2. A CloudFormation service role is an IAM role that is assumed by CloudFormation before stack operations are performed. The policies attached to that role will then be used to perform stack operations.
  3. The API credentials that are attached to the IAM entity (user or role), when we run the 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), the call will fail with a 400 AlreadyExists error.
  6. If we run a stack update without any changes in a template or parameters, nothing will happen, as there are no changes. CloudFormation will not notice if the resource has been deleted manually. However, if we update the deleted resource, the operation will fail because the CloudFormation resource still exists in the state...