As software development teams transition to cloud-based architectures and adopt agile processes, the tools they need to support application development in this new world will change. In this session, we'll take you the transition that Amazon made to a service-oriented architecture over a decade ago, and introduce you to some of the processes and tools that we built and adopted along the way. We’ll share what lessons we’ve learned, explain how we’ve achieved better agility and reliability in our software development and deployment processes, and present an overview of tools we’ve used to help get us there that have since become services such as AWS CodeCommit, AWS CodePipeline, AWS CodeDeploy, and more.

1. CHICAGO
©2015, Amazon Web Services, Inc. or its affiliates. All rights reserved

2. ©2015, Amazon Web Services, Inc. or its affiliates. All rights reserved
Transforming Software Development
(DevOps at Amazon)
Rob Brigham
Product Management, AWS Developer Tools

3. Prelude

4. Agenda
• The Amazon DevOps story
• New developer tools for everyone
– AWS CodeDeploy
– AWS CodePipeline
– AWS CodeCommit

5. What is DevOps?
DevOps = efficiencies that speed up this lifecycle
developers customers
releasetestbuild
plan monitor
delivery pipeline
feedback loop
Software development lifecycle

6. ©2015, Amazon Web Services, Inc. or its affiliates. All rights reserved
The Amazon DevOps story
©2015, Amazon Web Services, Inc. or its affiliates. All rights reserved

8. Monolith development lifecycle
developers
releasetestbuild
delivery pipelineapp

9. • Service-Oriented
Architecture (SOA)
• Single-purpose
• Connect only
through APIs
• “Microservices”

10. • Two-pizza teams
• Full ownership
• Full accountability
• Aligned incentives
• “DevOps”

11. Missing tools
developers delivery pipelineservices
???

12. • Self-service
• Technology-agnostic
• Encourage best
practices
• Single-purpose
services

13. • Deployment service
• No downtime
deployments
• Health checking
• Versioned artifacts
and rollbacks

14. • Continuous
delivery
• From check-in to
production
• Automated actions
and transitions
• >90% of teams
Pipelines

15. Microservice development lifecycle
developers delivery pipelinesservices
releasetestbuild
releasetestbuild
releasetestbuild
releasetestbuild
releasetestbuild
releasetestbuild

16. = 50 million deployments a year
Thousands of teams
× Microservice architecture
× Continuous delivery
× Multiple environments

18. Setting up a delivery pipeline
1) Automate your software deployments
2) Automate your release process
deploy deploy deploy deploy
development test staging production
release: source > build > test > staging > production

19. Setting up a delivery pipeline
1) Automate your software deployments
AWS CodeDeploy
2) Automate your release process
AWS CodePipeline

20. ©2015, Amazon Web Services, Inc. or its affiliates. All rights reserved
AWS CodeDeploy
©2015, Amazon Web Services, Inc. or its affiliates. All rights reserved

21. The image cannot be displayed. Your computer may not have
enough memory to open the image, or the image may have
been corrupted. Restart your computer, and then open the file
again. If the red x still appears, you may have to delete the
image and then insert it again.
AWS CodeDeploy
• Scale from one instance to thousands
• Deploy to any server: AWS or on-premises
• Centrally control and monitor
Test
CodeDeployv1, v2, v3
Production
Dev
Coordinate automated deployments, just like Amazon
application
revisions
deployment groups
The image cannot be displayed. Your computer may not have
enough memory to open the image, or the image may have
been corrupted. Restart your computer, and then open the
file again. If the red x still appears, you may have to delete
the image and then insert it again.

22. 1) Package app 2) Specify targets 3) Deploy!
version: 0.0
os: linux
files:
- source: chef/
destination: /etc/chef/codedeploy
- source: target/hello.war
destination: /var/lib/tomcat6/webapps
hooks:
ApplicationStop:
- location: deploy_hooks/stop-tomcat.sh
BeforeInstall:
- location: deploy_hooks/install-chef.sh
- location: deploy_hooks/chef-solo.sh
ApplicationStart:
- location: deploy_hooks/start-tomcat.sh
ValidateService:
- location: deploy_hooks/verify_service.sh

23. 1) Package app 2) Specify targets 3) Deploy!
version: 0.0
os: linux
files:
- source: chef/
destination: /etc/chef/codedeploy
- source: target/hello.war
destination: /var/lib/tomcat6/webapps
hooks:
ApplicationStop:
- location: deploy_hooks/stop-tomcat.sh
BeforeInstall:
- location: deploy_hooks/install-chef.sh
- location: deploy_hooks/chef-solo.sh
ApplicationStart:
- location: deploy_hooks/start-tomcat.sh
ValidateService:
- location: deploy_hooks/verify_service.sh

24. 1) Package app 2) Specify targets 3) Deploy!
version: 0.0
os: linux
files:
- source: chef/
destination: /etc/chef/codedeploy
- source: target/hello.war
destination: /var/lib/tomcat6/webapps
hooks:
ApplicationStop:
- location: deploy_hooks/stop-tomcat.sh
BeforeInstall:
- location: deploy_hooks/install-chef.sh
- location: deploy_hooks/chef-solo.sh
ApplicationStart:
- location: deploy_hooks/start-tomcat.sh
ValidateService:
- location: deploy_hooks/verify_service.sh

25. 1) Package app 2) Specify targets 3) Deploy!
Agent Agent Agent
Test
Agent Agent
Agent Agent
Agent
Agent
Production
Deployment groupDeployment group
Group instances by:
• Auto Scaling group
• Amazon EC2 tag
• On-premises tag

26. 1) Package app 2) Specify targets 3) Deploy!
aws deploy create-deployment
--application-name MyApp
--deployment-group-name TargetGroup
--s3-location bucket=MyBucket,key=MyApp.zip
AWS CLI & SDKs
AWS Console
CI / CD Partners
GitHub

27. Rolling update – Deploy without downtime
v1v1 v1
Load Balancer

28. Rolling update – Deploy without downtime
v1v2 v1
Load Balancer

29. Rolling update – Deploy without downtime
v2v2 v1
Load Balancer

30. Rolling update – Deploy without downtime
v2v2v2
Load Balancer

31. Rolling update – Deploy without downtime
v2v2 v2
Load Balancer

32. Health tracking – Catch deployment problems
v2v2 v2
Load Balancer

33. Health tracking – Catch deployment problems
v3 v2 v2Stop
Load Balancer

34. Health tracking – Catch deployment problems
v2v2 v2
Load Balancer
Rollback

35. Health tracking – Catch deployment problems
v2v2 v2
Load Balancer

36. Deployment config – Choose speed
v2 v1 v1 v1 v1 v1 v1 v1
v2 v2 v2 v2 v1 v1 v1 v1
v2 v2 v2 v2 v2 v2 v2 v2
one at a time
half at a time
all at once

37. Demo

38. Product integrations

39. ©2015, Amazon Web Services, Inc. or its affiliates. All rights reserved
AWS CodePipeline
©2015, Amazon Web Services, Inc. or its affiliates. All rights reserved

40. AWS CodePipeline
• Model your release process
• Integrate with your systems
• Visually monitor your pipeline status
Continuous delivery and release automation, just like Amazon
Build
1) Build
2) Unit test
1) Deploy
2) UI test
Source Beta Production
1) Deploy
2) Perf test
Gamma
1) Deploy canary
2) Deploy region 1
3) Deploy region 2
1) Pull

41. Why automate your release process?
Launch
quickly
Ensure
quality

42. Demo

43. ©2015, Amazon Web Services, Inc. or its affiliates. All rights reserved
AWS CodeCommit
©2015, Amazon Web Services, Inc. or its affiliates. All rights reserved

44. Source control in the cloud
Secure Fully
managed
High
availability
Store
anything

45. AWS CodeCommit
• Data redundancy across Availability Zones
• Data-at-rest encryption
• Integrated with AWS Identity and Access Management
• No repo size limit
git
pull/push
CodeCommit
Git objects in
Amazon S3
Git index in
Amazon
DynamoDB
Encryption key
in AWS KMS
SSH or HTTPS
Secure, scalable, and managed Git source control

46. Same Git experience
$ git clone https://git-codecommit.us-east-1.amazonaws.com/v1/repos/aws-cli
Cloning into 'aws-cli'...
Receiving objects: 100% (16032/16032), 5.55 MiB | 1.25 MiB/s, done.
Resolving deltas: 100% (9900/9900), done.
Checking connectivity... done.
$ nano README.rst
$ git commit -am 'updated README'
[master 4fa0318] updated README
1 file changed, 1 insertion(+)
$ git push
Counting objects: 3, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (3/3), done.
Writing objects: 100% (3/3), 297 bytes | 0 bytes/s, done.
Total 3 (delta 2), reused 0 (delta 0)
remote:
To https://git-codecommit.us-east-1.amazonaws.com/v1/repos/aws-cli
4dacd6d..4fa0318 master -> master

47. ©2015, Amazon Web Services, Inc. or its affiliates. All rights reserved
Summary
©2015, Amazon Web Services, Inc. or its affiliates. All rights reserved

48. AWS Code services
CodeCommit
coming soon
CodePipeline
coming soon
CodeDeploy
launched Nov 2014

49. CHICAGO

50. Your Feedback is Important to AWS
Please complete the session evaluation. Tell us what you think!