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 9: Generating CloudFormation Templates Using AWS CDK

  1. Constructs are building blocks of CDK. Any block of CDK, such as App, Stack, Asset, or Resource is considered to be a Construct.
  2. You have to define each stack separately by assigning a stack class to it as a value.
  3. By adding subnet configuration to the VPC construct. Originally, CDK was developed by TypeScript, but there are libraries for Python, Java, C#, and JavaScript. The CDK development team is working on more languages to support in CDK.
  4. No, CDK will use the default credentials and config to connect to AWS. But it is recommended to provide an account ID and Region when using CDK in production.