by awslabs

In few hours, quickly learn how to effectively leverage various AWS services to improve developer pr...

501 Stars 285 Forks Last release: Not found Apache License 2.0 80 Commits 0 Releases

Available items

No Items, yet!

The developer of this repository has not created any items for sale yet. Need a bug fixed? Help with integration? A different license? Create a request here:

AWS DevOps Essentials

An Introductory Workshop on CI/CD Practices

In few hours, quickly learn how to effectively leverage various AWS services to improve developer productivity and reduce the overall time to market for new product capabilities. In this session, we will demonstrate a prescriptive approach to incrementally adopt and embrace some of the best practices around continuous integration & delivery using AWS Developer Tools and 3rd party solutions including, AWS CodeCommit (a managed source control service), AWS CodeBuild (a fully managed build service), Jenkins (an open source automated build server), CodePipeline (a fully managed continuous delivery service), and CodeDeploy (an automated application deployment service). We will also highlight some best practices and productivity tips that can help make your software release process fast, automated, and reliable.

See the diagram below for a depiction of the complete architecture.

DevOps Workshop Architecture


  • Configure AWS CodeCommit: The easiest way to set up AWS CodeCommit is to configure HTTPS Git credentials for AWS CodeCommit. On the user details page in IAM console, choose the Security Credentials tab, and in HTTPS Git credentials for AWS CodeCommit, choose Generate. HTTPS Git Credential 💡 Note: Make Note of the Git HTTP credentials handy. It will be used for cloning and pushing changes to Repo. Also, You can find detail instruction on how to configure HTTPS Git Credential here
  • IAM Permissions: Finally, for the AWS account ensure you have sufficient privileges. You must have permissions for the following services:

AWS Identity and Access Management

Amazon Simple Storage Service

AWS CodeCommit

AWS CodeBuild

AWS CloudFormation

AWS CodeDeploy

AWS CodePipeline

AWS Cloud9

Amazon EC2

Amazon SNS

Amazon CloudWatch Events


Preferred regions for lab - North Virginia US-EAST-1 - Oregon US-WEST-2

If you want to your region choice for the lab. Kindly the select the region which has all four Code* services and Cloud9 service. You can find the region services list. Stick to the same region throughout all labs. Make sure you have not reached the VPC or Internet Gateway limits for that region. If you already have 5 VPCs/IGWs, delete at least one before you proceed or choose an alternate region.


This workshop is broken into multiple labs. You must complete each Lab before proceeding to the next.

  1. Lab 1 - Build project on the cloud
  2. Lab 2 - Automate deployment for testing
  3. Lab 3 - Setup CI/CD using AWS CodePipeline
  4. Lab 4 (Optional) - Using Lambda as Test Stage in CodePipeline

Clean up

  1. Visit CodePipeline console, select the created pipeline. Select the Edit and click Delete.
  2. Visit CodeDeploy console, select the created application. In the next page, click Delete Application.
  3. Visit CodeBuild console, select the created project. Select the Action and click Delete.
  4. Visit CodeCommit console, select the created repository. Go to setting and click Delete repository.
  5. Visit Lambda console, select the created function. Select the Action and click Delete.
  6. Visit Cloudformation console, select the created stacks. Select the Action and click Delete Stack.
  7. Visit Cloud9 console, select the created Environment. Select the Action and click Delete.
  8. Visit Simple Notification Service console, select Topics. Select the created topic. Select the Action and click Delete topics. Next select Subscriptions. Select the created subscription. Select the Action and click Delete subscriptions.


This library is licensed under the Apache 2.0 License.

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.