Create a Continuous Delivery Pipeline : AWS Project

Create a Continuous Delivery Pipeline : AWS Project

Introduction

This project implements a Continuous Delivery (CD) pipeline using AWS CodePipeline, AWS CodeBuild, and AWS Elastic Beanstalk to automate deployments. The setup provides a structured approach to code deployment, enhancing reliability and minimizing manual processes—ideal for agile development teams aiming for efficient, high-frequency deployments.

Tech Stack

• AWS CodePipeline: Manages the entire deployment flow, coordinating the build, test, and deployment stages.




• AWS CodeBuild: Automates the building and testing of code, ensuring that each change is thoroughly validated before deployment.




• AWS Elastic Beanstalk: Manages the deployment of the web application, ensuring it is hosted in a high-availability, scalable environment.




• Amazon EC2 with Auto Scaling: Ensures scalable, fault-tolerant infrastructure to support application load, with ALB (Application Load Balancer) for even traffic distribution.

Prerequisites

• AWS Account: Required for configuring the CD pipeline and associated services.




• Code Repository: A source code repository such as GitHub or CodeCommit that integrates with CodePipeline.




• Basic CI/CD Knowledge: Familiarity with the principles of continuous integration and continuous delivery.




• AWS CLI: To facilitate configuration and command-line management.

Problem Statement or Use Case

Problem: Manually deploying updates to web applications is error-prone, time-consuming, and can lead to inconsistent deployment practices, especially in fast-paced development environments.

Solution: The Continuous Delivery Pipeline ensures that each code change is automatically built, tested, and deployed to a managed environment, reducing manual intervention. This setup allows developers to push code more frequently, get faster feedback, and minimize deployment risks.

Real-World Relevance: In production settings, a CD pipeline is crucial for agile teams who need reliable, frequent deployments without impacting application uptime or performance. This project demonstrates how AWS can automate and manage application deployments, making it ideal for high-availability and fast-paced development scenarios.

Architecture Diagram

.

1. In a new browser tab, navigate to repo.




2. Choose the white Fork button on the top right corner of the screen. Next, you will see a small window asking you where you would like to fork the repo.




3. Verify it is showing your account and choose Create a fork. After a few seconds, your browser will display a copy of the repo in your account under Repositories.

Push a change to your new repo

1. Go to the

   
   
   
   
   

   1. If you’re on a Mac or Linux computer, open your terminal. If you’re on Windows, launch Git Bash.

   
   
   2. 
      

      In the terminal or Bash platform, whichever you are using, enter the following command and paste the URL you just copied in Step 2 when you clicked the clipboard icon. Be sure to change “YOUR-USERNAME” to your GitHub username. You should see a message in your terminal that starts with Cloning into. This command creates a new folder that has a copy of the files from the GitHub repo.

      
      
      

      git clone .

   
   

   3. In the left navigation panel, under Repositories, select the one named aws-elastic-beanstalk-express-js-sample.

   
   

   4. Choose the app.js file. The contents of the file, including your change, should be displayed.

   
   
   
   
   

   
   
   
   Application architecture
   

   
   
   

   Here is what our architecture looks like right now:

   
   
   

   .




2. Choose the orange Create Application button.




3. Choose Web server environment under the Configure environment heading.




4. In the text box under the heading Application name, enter DevOpsGettingStarted*.*




5. In the Platform dropdown menu, under the Platform heading, select Node.js . Platform branch and Platform version will automatically populate with default selections.




6. Confirm that the radio button next to Sample application under the Application code heading is selected.




7. Confirm that the radio button next to Single instance (free tier eligible) under the Presets heading is selected.




8. Select Next.

to create an IAM Role that you can subsequently select for the EC2 instance profile. Then, return back to this step.

1. Choose Skip to Review on the Configure service access page.

This will select the default values for this step and skip the optional steps.

While waiting for deployment, you should see:

• A screen that will display status messages for your environment.




• After a few minutes have passed, you will see a green banner with a checkmark at the top of the environment screen.

Once you see the banner, you have successfully created an AWS Elastic Beanstalk application and deployed it to an environment.

Test your web app

1. To test your sample web app, select the link under the name of your environment.

Application architecture

Now that we are done with this module, our architecture will look like this:

.

We have created a build project on AWS CodeBuild to run the build process of the Hello World! web app from our GitHub repository. We will be using this build project as the build step in our continuous delivery pipeline, which we will create in the next module.

Module 4: Create Delivery Pipeline

Create a new pipeline

1. In a browser window, open the

   
   
   

   We have created a continuous delivery pipeline on AWS CodePipeline with three stages: source, build, and deploy. The source code from the GitHub repo created in Module 1 is part of the source stage. That source code is then built by AWS CodeBuild in the build stage. Finally, the built code is deployed to the AWS Elastic Beanstalk environment created in Module 3.

   
   
   

   
   
   
   Module 5: Finalize Pipeline and Test
   

   
   
   

   
   
   
   Create a review stage in pipeline
   

   
   
   
   
   

   1. Open the .

   
   

   2. Select the pipeline named Pipeline-DevOpsGettingStarted. You should see the Source and Build stages switch from blue to green.

   
   

   3. When the Review stage switches to blue, choose the white Review button.

   
   

   4. Write an approval comment in the Comments textbox.

   
   

   5. Choose the orange Approve button.

   
   

   6. Wait for the Review and Deploy stages to switch to green.

   
   

   7. Select the AWS Elastic Beanstalk link in the Deploy stage. A new tab listing your Elastic Beanstalk environments will open.

   
   

   8. Select the URL in the Devopsgettingstarted-env row. You should see a webpage with a white background and the text you had in your most recent GitHub commit.

   
   
   
   
   
   
   
   • Congratulations! You have a fully functional continuous delivery pipeline hosted on AWS.
   
   
   
   
   

   
   
   
   Application architecture
   

   
   
   

   With all modules now completed, here is the architecture of what you built:

   
   
   

   .




2. In the left navigation menu, click on “Applications.” You should see the “DevOpsGettingStarted” application listed under “All applications.”




3. Select the radio button next to “DevOpsGettingStarted.”




4. Click the white dropdown “Actions” button at the top of the page.




5. Select “Delete application” under the dropdown menu.




6. Type “DevOpsGettingStarted” in the text box to confirm deletion.




7. Click the orange “Delete” button.

Delete pipeline in AWS CodePipeline

1. In a new browser window, open the .




2. You should see a bucket named “codepipeline-us-west-2” followed by your AWS account number. Click on this bucket. Inside this bucket, you should see a folder named “Pipeline-DevOpsGettingStarted.”




3. Select the checkbox next to the “Pipeline-DevOpsGettingStarted” folder.




4. Click the white “Actions” button from the dropdown menu.




5. Select “Delete” under the dropdown menu.




6. Click the blue “Delete” button.

Delete build project in AWS CodeBuild

1. In a new browser window, open the

   
   
   

   
   

   Shubham Murti — Aspiring Cloud Security Engineer | Weekly Cloud Learning !!

   
   

   
   
   

   Let’s connect: , Github

   Vollständiger Original-Bericht

   Ausführliche Details, Code-Beispiele & Hersteller-Stellungnahme auf dev.to.

   ↗ Original-Artikel auf dev.to lesen