Continuous Integration and Continuous Delivery helps developers rapidly and reliably release updates for their applications in a standardized and safe manner. The faster you can release new features and fix bugs, the quicker you can innovate and respond to customer needs. Infrastructure as Code is a practice by where traditional infrastructure management techniques are supplemented and often replaced by using code based tools and software development techniques. Amazon Web Services provides developer tools that help you define your infrastructure as code as well as continuously iterate on and develop said infrastructure. In this session, we’ll discuss how to build multi-stage pipelines that let you build and test your software defined infrastructure in an automated way using AWS CodeCommit, AWS CodePipeline, AWS CodeBuild, and AWS Cloudformation. We’ll look at how to orchestrate pipelines across multiple AWS accounts in a secure and scalable fashion.

1. © 2016, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Harvey Bendaña, Enterprise Solutions Architecture
August 10th, 2017
CI/CD Pipelines for Your Infrastructure…
as Code!
AWS Seattle Meetup

2. Hi J

4. What we’ll cover…
What is DevOps?
Infrastructure as Code
CI/CD
Demos J

5. What is DevOps?

6. Is it…
• A philosophy? Cultural change? Paradigm shift?
• Alignment of development and IT operations with better communication
and collaboration? Breaking down barriers between development and
IT operations?
• Improvement in software deployment?
• Akin to Agile software development applied to infrastructure and IT
operations?
• …?

7. Yes…J

8. Level set…
DevOps is the combination of cultural philosophies,
practices, and tools that increases your organization’s
ability to deliver applications and services at high velocity.
This enables your organization to be more responsive to
the needs of your customers.

9. Reliability
Benefits of DevOps
Speed
Scale
Rapid DeliveryImproved Collaboration
Security

10. Infrastructure as Code

11. Level Set…
Infrastructure as Code is a practice by where traditional
infrastructure management techniques are supplemented
and often replaced by using code based tools and software
development techniques.

12. AWS CloudFormation
JSON or YAML formatted file
Parameter definition
Resource creation
Configuration actions
Framework
Stack creation
Stack updates
Error detection and rollback
Configured AWS resources
Comprehensive service support
Service event aware
Customizable
Template CloudFormation Stack

13. This turns into this…

14. Benefits of IaC with CloudFormation
Templated resource
provisioning
Portable and
reusable
Declarative
and flexible
Easy to use

15. CI/CD

16. Level set…
Continuous Integration and Continuous Delivery helps
developers rapidly and reliably release updates for their
applications in a standardized and safe manner. The faster
you can release new features and fix bugs, the quicker you
can innovate and respond to customer needs.

17. • Integration
tests with
other systems
• Load testing
• UI tests
• Penetration
testing
Release processes have four major phases
Source Build Test Production
• Check-in
source code
such as .java
files.
• Peer review
new code
• Compile code
• Unit tests
• Style checkers
• Code metrics
• Create
container
images
• Deployment
to production
environments
Continuous integration
Continuous delivery
Continuous deployment

18. AWS Code Services
AWS CodePipeline AWS CodeCommit AWS CodeBuildAWS CodeDeployAWS CodeStar

19. AWS Code Services
Source Build Test Production
Software Release Steps:

20. AWS Code Services
Source Build Test Production
Software Release Steps:
AWS CodeCommit

21. AWS Code Services
Source Build Test Production
Software Release Steps:
AWS CodeBuild

22. AWS Code Services
Source Build Test Production
Third Party
Tooling
Software Release Steps:

23. AWS Code Services
Source Build Test Production
Software Release Steps:
AWS CodeDeploy

24. Source Build Test Production
AWS CodeCommit AWS CodeBuild AWS CodeDeploy
AWS CodePipeline
AWS Code Services
Software Release Steps:
Third Party
Tooling

25. Source Build Test Production
AWS CodeCommit AWS CodeBuild AWS CodeDeploy
AWS CodePipeline
AWS Code Services
Software Release Steps:
Third Party
Tooling

26. Use Case: VPC CI/CD Pipeline

28. lab
system
integration
continuous
integration
staging
production
CloudFormationS3 BucketCodeCommit
CodePipeline
CodeBuild
IAM Service Role
IAM Service Role
IAM Service Role
CloudFormation
Template(s)

29. Works great…right?

30. What about…
• Deploying to multiple accounts?
• I’ve hit resource limits in an individual account
• I use AWS Organizations to manage multiple accounts
• Security when deploying to multiple accounts?
• I want to encrypt my data at rest AND in transit
• I want to make sure my artifacts bucket is only accessible
from AWS accounts I own
• ……?

31. production
staging
system-integration
source
continuous-Integration
lab

32. Check this out…
AWS Resources
• https://aws.amazon.com/blogs/devops/
• https://aws.amazon.com/cloudformation/
• https://aws.amazon.com/codecommit/
• https://aws.amazon.com/codepipeline/
• https://aws.amazon.com/codebuild/
CloudFormation Linters
• https://github.com/stelligent/cfn_nag
• https://github.com/Versent/cfn-check
• https://github.com/martysweet/cfn-lint

33. Thank you!
bendanah@amazon.com