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

Examining CDK deployment logs

Another way to troubleshoot a CDK application is by looking at its internal logs. This is often useful if a certain resource gets stuck when being created, which, for example, happens when an ECS container fails to stabilize. In such situations, looking at the verbose CDK logs could shine a light on what is happening.

This can be achieved by passing the following flags to cdk commands:

  • -v: Verbose
  • -vv: Very verbose
  • -vvv: Extremely verbose

For instance, when deploying using cdk deploy, you can see a lot more information about the status of the deployment if you pass in one of the aforementioned flags, like so:

$ cdk deploy --profile cdk -vv

There is also the -debug flag. The -debug flag is used to enable debug mode for the cdk command. It will cause the CDK to display additional debug information about the deployment process, including detailed information about the CloudFormation stack events and the individual AWS SDK calls...