Book Image

AWS CDK in Practice

By : Mark Avdi, Leo Lam
Book Image

AWS CDK in Practice

By: Mark Avdi, Leo Lam

Overview of this book

As cloud applications are becoming more complex, multiple tools and services have emerged to cater to the challenges of running reliable solutions. Although infrastructure as code, containers, and orchestration tools, such as Kubernetes, have proved to be efficient in solving these challenges, AWS CDK represents a paradigm shift in building easily developed, extended, and maintained applications. With AWS CDK in Practice, you’ll start by setting up basic day-to-day infrastructure while understanding the new prospects that CDK offers. You’ll learn how to set up pipelines for building CDK applications on the cloud that are long-lasting, agile, and maintainable. You’ll also gain practical knowledge of container-based and serverless application development. Furthermore, you’ll discover how to leverage AWS CDK to build cloud solutions using code instead of configuration files. Finally, you’ll explore current community best practices for solving production issues when dealing with CDK applications. By the end of this book, you’ll have practical knowledge of CDK, and you’ll be able to leverage the power of AWS with code that is simple to write and maintain using AWS CDK.
Table of Contents (17 chapters)
Part 1: An Introduction to AWS CDK
Part 2: Practical Cloud Development with AWS CDK
Part 3: Serverless Development with AWS CDK
Part 4: Advanced Architectural Concepts

Setting up and building the stack

If you haven’t done so already, go ahead and clone the following repository:

The Code in Action video for this chapter can be viewed at:

Heads up

In this chapter, we will also be using Docker tooling. You can find the installation setup for your operating system by visiting

You will find the code for this chapter in the relevantly named chapter-3-building-a-full-stack-app-with-cdk directory. Just like we did with the last chapter, we have separated the code into the following main directories:

  • infrastructure will hold our CDK components
  • server will contain the code for our Express.js-based API
  • web is essentially a React-based frontend that hooks up to the API

If you dig into any of these directories, you will see that they each have their own README files, package.json, and various other relevant...