Demonstration 3 Create 4 Stage Pipeline

​

Pipeline Overview

​

1. Source Stage with CodeCommit

1. Open the AWS CodeCommit console and create a new repository named kodekloudcpdemo.

2. Enter Repository name as kodekloudcpdemo and click Create.

3. Clone the repo locally:

git clone https://git-codecommit.us-east-2.amazonaws.com/v1/repos/KodeKloudCPDemo

4. Back in the console, click Upload file to add your application files (after_install, application_start, appspec.yml, etc.). For each file, provide an author name and email, then commit.

5. After each commit, you’ll see a success notification:

6. When all nine files are uploaded, your repo should list them as shown:

​

2. Build Stage with CodeBuild

1. Navigate to the AWS CodeBuild console and click Create build project.

2. Set Project name to KodeKloudCPdemo.

3. Under Source, select AWS CodeCommit, choose kodekloudcpdemo, and branch main.

4. In Environment, pick:
   • Operating system: Linux
   • Runtime: Standard
   • Image: aws/codebuild/standard:2.0
5. Keep service role and log settings at their defaults, then click Create build project.

6. Confirm your project is ready:

​

Adjusting the Buildspec

version: 0.2
phases:
  install:
    runtime-versions:
      nodejs: 10
    commands:
      - echo "Installing dependencies"
      - npm install
  build:
    commands:
      - echo "Building the application"
      - npm run build
artifacts:
  files:
    - '**/*'

​

3. Prepare EC2 Instances for CodeDeploy

1. In the EC2 console, click Launch Instance.
2. Name the instance CodePipelineCPdemo and choose an Ubuntu AMI.
3. Select or create a key pair.
4. Open HTTP (port 80) and HTTPS (port 443) in the security group.
5. Enable Auto-assign Public IP.
6. Under Advanced Details, attach an IAM instance profile with CodeDeploy permissions.
7. Click Launch Instance.

​

4. Deploy Stage with CodeDeploy

1. Go to the AWS CodeDeploy console and click Create application.
2. Name it KodeKloudCPdemo and choose EC2/On-premises as the compute platform.

3. Create a deployment group:
   • Name: KodeKloudCPdemo
   • Service role: CodeDeployDefault (or your custom role)
   • Uncheck load balancer integration.
   • Environment: EC2/On-premises
   • Tag key/value matching your EC2 instance (Name=CodePipelineCPdemo).

4. Select the EC2 instance by tag:

5. (Optional) Install or verify the CodeDeploy agent via Systems Manager, then click Create deployment group.

​

5. Create the Four-Stage Pipeline

1. Open the AWS CodePipeline console and click Create pipeline.
2. Name it KodeKloudCPdemo and use the default service role.

​

Source Stage

• Provider: AWS CodeCommit
• Repository: kodekloudcpdemo
• Branch: main

​

Build Stage

• Provider: AWS CodeBuild
• Project name: KodeKloudCPdemo

​

Deploy Stage

• Provider: AWS CodeDeploy
• Region: your AWS Region
• Application: KodeKloudCPdemo
• Deployment group: KodeKloudCPdemo

​

6. Adding the Test Stage

1. Click Edit in the pipeline view.
2. Under the Build stage, click Add stage, name it Test, then Add stage.

3. Inside Test, click Add action group and configure:
   • Action name: TestAction
   • Provider: AWS CodeBuild
   • Input artifact: BuildArtifact
   • Project name: KodeKloudCPdemo

4. Save changes and click Release change. The pipeline will now run all four stages in sequence, ending with a green success status across Source, Build, Test, and Deploy.

​

Summary

1. Source: CodeCommit
2. Build: CodeBuild
3. Test: CodeBuild
4. Deploy: CodeDeploy

​

Links and References

• AWS CodePipeline Documentation
• AWS CodeCommit Documentation
• AWS CodeBuild Documentation
• AWS CodeDeploy Documentation
• EC2 Instance Connect