CDK: The Modern Approach to AWS Resources Part 2

Gupta Bless
5 min readSep 10
Source

Introduction

In my last blog (https://gupta-bless.medium.com/cdk-the-modern-approach-to-aws-resources-6facbfdcc37e), we explored the fundamentals of CDK; in this blog, we will describe CDK integration with the CD/CD pipeline. In my earlier blog, I also addressed how integrating your CDK with CD/Cd will assist your organization. There are various types of CD/CD pipelines accessible, such as Jenkins, Gitlab, AWS code pipeline, and so on, but which one we want to use depends on the organizational structure. In this blog, we used the AWS CodePipeline to learn about CI/CD.

CI/CD integration enables automated integration, faster feedback, automated testing, consistency, version control, rollback and code recovery, and other benefits while ensuring compliance and security. BY adopting CD/CD various steps of software pipelines that ensure code updates are built correctly, tested, and delivered in a consistent and efficient manner.

How integration with AWS CodePipeline works

Source

It has couple of stages, let us discuss them:

Source stage

This is a pipeline entry point where it typically monitors the code repository, which can be Github, AWS CodeCommit, or Bitbucket. As a result, any changes in these sources start the pipeline.

Build and test stage

The code pipeline starts and automatically builds your code based on changes, then performs tests on those builds. This phase is simply to ensure that the application is stable and ready to be deployed.

Deployment stage

At this point, the code has been tested and, if successful, will be deployed to your AWS environment via the codepipeline. Deployment is not limited to web servers; it can involve any AWS service or even a serverless architecture.

Post deployment stage

The documentation and any relevant teams can be notified of any changes after a deployment has taken place. Organizations…

Gupta Bless

Security enthusiast working to secure web for others.