Day 53: CI/CD Pipeline On AWS-Part 4 CodeCommit
TABLE OF CONTENTS
- AWS CodePipeline
- Tasks
- Create a CodePipeline that gets the code from CodeCommit, Builds the code using CodeBuild, and deploys it to a Deployment Group.
- Step 1: Choose pipeline settings
- Step 2: Add source stage
- Step 3: Add build stage
- Step 4: Add the deploy stage
AWS CodePipeline
AWS CodePipeline is a continuous delivery service you can use to model, visualize, and automate the steps required to release your software.
You can quickly model and configure the different stages of a software release process. CodePipeline automates the steps required to release your software changes continuously.
You can refer to the official documentation by AWS to learn more about CodePipeline. The link is here: https://docs.aws.amazon.com/codepipeline/index.html
Tasks
Create a CodePipeline that gets the code from CodeCommit, Builds the code using CodeBuild, and deploys it to a Deployment Group.
We need to have a Deployment group for this activity. You can follow this link for that: https://muditm12.hashnode.dev/day-52-cicd-pipeline-on-aws-part-3-codecommit
Now in the AWS Management Console > Navigate to CodePipeline > Click on pipelines > Create Pipeline
Step 1: Choose pipeline settings
Pipeline name: day53-app > Select New Service Role > Click on Next
Step 2: Add source stage
Source Provider: AWS CodeCommit > Repository name & Branch Name: Select your repository & branch > Change detection options: AWS CodePipeline > Click on Next
Step 3: Add build stage
Build provider: AWS CodeBuild > Project Name: Select your Build Project > Click on Next
Step 4: Add the deploy stage
Deploy provider: AWS CodeDeploy > Application name & Deployment group : Select your respective choices > Click on Next
Review your options and click on Create Pipeline.
Once your pipeline is successfully created, you can see that this pipeline automatically triggers the code thereby automating the process.
And yay our pipeline is successfully run. To verify this let us reach our NginX server via our EC2 instance’s Public IPv4.
In this blog, I have used the AWS CodePipeline service. If you have any questions or want to share your experiences, please comment below. Don’t forget to read my blogs and connect with me on LinkedIn and let’s have a conversation.
To help me improve my blog and correct my mistakes, I am available on LinkedIn as Mudit Mathur. Do reach me, and I am open to suggestions and corrections.
#Day53 #90daysofdevops
