Book Image

AWS CDK in Practice

By : Mark Avdi, Leo Lam
3.5 (2)
Book Image

AWS CDK in Practice

3.5 (2)
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)
1
Part 1: An Introduction to AWS CDK
4
Part 2: Practical Cloud Development with AWS CDK
9
Part 3: Serverless Development with AWS CDK
12
Part 4: Advanced Architectural Concepts

Technical requirements

Just like previous chapters, the source code for this chapter can be found in the following GitHub directory: https://github.com/PacktPublishing/AWS-CDK-in-Practice/tree/main/chapter-5-continuous-integration-with-cdk-powered-apps.

The Code in Action video for this chapter can be viewed at: https://packt.link/vd91G.

GitHub personal access token

CodePipeline is a CI/CD tool that needs to get the latest changes from the code repository. AWS has its own GitHub repository hosting platform named CodeCommit, which we would use in the blink of an eye had we not found the UI to be eye-wateringly horrendous (there goes our AWS partnership status), since like everything else, the integration with CodePipeline is a breeze.

For now, it’s cool to stick to GitHub and we need to figure out a way for CodePipeline to access the GitHub repo and be informed of changes. Thankfully, CodePipeline does most of that for us with a Source step. This Source step needs...