This document discusses Amazon's approach to DevOps. It explains how Amazon transitioned from monolithic development to microservices and empowered small, cross-functional teams to work independently and deploy code frequently using agile methodologies and DevOps practices. It outlines Amazon's organizational changes, including establishing 2-pizza teams, encouraging collaboration over silos, and building shared tools and practices. The document also provides lessons learned from Amazon's experience and recommends starting a DevOps transformation by aligning the organization, establishing guardrails, and learning through a small pilot team.

1. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Moving to DevOps the Amazon Way

2. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
© 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Agenda
The DevOps pretext
How Amazon did it
Lessons learned
Where to start your DevOps journey

3. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Enterprises need speed and agility

4. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
© 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Reduce the cost of
supporting current
technology
Two big goals for IT today
Lead innovation and
transformation of business

5. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
© 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
What we all are really trying to achieve …
Infrastructure
Support
Innovation
Infrastructure
Support
Innovation
Innovation
Support

6. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
© 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
What it means in numbers …
30x
More frequent
deployments
440x
Shorter lead times
60x
Fewer failures
-21%
Unplanned rework
44%
New work
Source: Puppet State of DevOps Report 2017

7. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
© 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
AWS pace of innovation
0
250
500
750
1000
1250
1500
1750
2000
2010 2012 2014 2016 2018
Launches
1,957 new
features/services
launched in 2018
As of January 2018
AWS has been continually expanding
its services to support virtually any
cloud workload
61
159
516
1957
1017

8. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
© 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
= Millions of deployments a year
Thousands of teams
× Microservice architecture
× Continuous delivery
× Multiple environments
Several types of deployments

9. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
© 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
How ?

10. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
How Amazon did it

11. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
© 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Organizational mindset alignment,
engineering enablement, and builder
empowerment
Cultural
Philosophy
Practices
and
Patterns
Tools

12. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
© 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved.

13. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
© 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved.

14. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
© 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Monolith development lifecycle
ReleaseTestBuild
Developers
Services Delivery pipeline

15. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
© 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Need then became
Become agile again?

16. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
© 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Identify and break processes into fine-grained units
Shipping
Labeling
Cart
Checkout
Stock
Search
Listing
Assign those units to small teams

17. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
© 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Process: Store products into slots
Microservice
(Software)
Builds Uses
Dev Team
Now, let each team operate as a start-up
Outcome: Customer obsession, ownership, freedom to innovate, agility

18. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
© 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Optimized flow by dedicating single-threaded teams
Dedicated product teams
ProductDevelopment
ProductGo-ToMarket
ProductManagers
ProjectManagers
Developers
Testers
Implementers
Operations&Support
Product Team B
Product Team A
Product Team C
Backlog A
• Story 1
• Story 2
• Story 3
• Story 4
Backlog B
• Story 1
• Story 2
• Story 3
• Story 4
Backlog C
• Story 1
• Story 2
• Story 3
• Story 4

19. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
© 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Example of scrum roles
Scrum master, developers, product owner
Teams adopted agile methodologies
Example of scrum board

20. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
© 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
“Silos” got discouraged in the organization
Operations
Database
team
Quality assurance
Application
security
Software dev
team
“We’re blocked waiting
the Dev environment setup”
“We’re blocked waiting
a new table/SQL script”
“We’re blocked waiting
performance tests”
”We’re blocked waiting source
code manual inspection”
”We’re blocked waiting
database security approvals”
”We’re blocked waiting
security tests to complete”
”We’re blocked waiting the
creation of security certificates”
“We’re blocked waiting the
setup of the database hosts”
“We’re blocked waiting new test hosts”

21. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
© 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Teams learned to work together (DevOps)
Operations
Database
Administrator
Quality Assurance
(Testers)
Application
Security
Software Dev
Team
“Working together”

22. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
© 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Our 2-Pizza Teams learned to do these
• Write application and infrastructure code
• Review code of others
• Write unit/integration/performance tests
• Create SQL queries
• Create and automate CI/CD pipelines
• Provision test and production hosts
• Use secure APIs and apply security policies
• Monitor production environments
• Be on-call on a rotation-basis

23. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
© 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
We built “guardrails”

24. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
© 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
We invested in sharing the
learnings, patterns, and
practices

25. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
© 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
AWS Native Services
Cloud
Mgmt.
AWS
Service Catalog
AWS
CloudTrail
AWS
Config
AWS Trusted
Advisor
AWS X-Ray
AWS
OpsWorks
Amazon
CloudWatch
AWS
CloudFormation
AWS Snowball
AWS SMS
AWS
Systems
Manager
AWS KMS
IAM
AWS DMS
Amazon Inspector
Amazon Macie
Amazon
GuardDuty
Service
request
Inventory and
classification
Monitoring
and analytics
Packaging
and delivery*
Provisioning
and orchestration
Cost management and
resource optimization
Cloud migration,
backup, and DR
Identity, security,
and compliance
AWS ConfigAWS CodeDeploy
AWS CodeCommit
AWS CodePipeline
AWS CodeBuild
* Not part of Gartner representation
Source: Gartner Evaluation Criteria for Cloud Management Platforms and Tools May 2018

26. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Lessons learned

27. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
© 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Lessons Learned
1. Enterprise-wide inclusiveness
2. Use belts and suspenders
3. Patterns of efficiency
4. Implement resilience testing
5. Implement observability

28. © 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Where to start your DevOps implementation?

29. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
© 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
DevOps is an ongoing journey,
not a destination

30. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
© 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
We did it, you can too!

31. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.
© 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Where to start the DevOps journey
TIME
Align
Organization
Align 3P
Define Operating model
Identify MVP scope
Form Pilot team
Decouple application services
Create e-2-e delivery platform
Create guardrails
Integrate functional groups
Adaptive Learning
Rinse and repeat ∞ parallel
De-coupling
Observability
AiOps
Well Architected
Operating model
Guardrails
Chaos engineering
Get help from coaches
Define Pilot team
1. Start small, learn, iterate
2. Set framework to scale
3. Teach

32. Thank you!
© 2019, Amazon Web Services, Inc. or its Affiliates. All rights reserved.