Find out more about how Scania is using Amazon DevOps

1. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Joakim Stolpe, AWS and Anders Lundsgård, Scania
May 3, 2017
DevOps at Amazon
A Look at Our Tools and Processes

2. What to expect from this session
The Amazon DevOps story
The Scania DevOps story
New developer tools for everyone

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

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

6. Monolith development lifecycle
developers
releasetestbuild
delivery pipelineapp

7. Service-Oriented
Architecture (SOA)
Single-purpose
Connected through APIs
Highly decoupled
“Microservices”

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

9. Missing tools
developers delivery pipelineservices
???

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

11. Deployment service
No downtime
deployments
Health tracking
Versioned artifacts and
rollbacks

12. Pipelines
Continuous delivery
Automated release
process
Faster and more reliable
releases
>90% of teams

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

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

15. How can others do this?

16. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Anders Lundsgård
Senior Engineer - Connected Services, Delivery Engineering Team
May 3, 2017
DevOps @ Scania

17. ~250.000 connected vehicles
~100 engineers
~15 years of age
Scania Connected Services
Anders Lundsgård
Senior Engineer
@anderslundsgard

18. Our software evolution
‘90s
Spaghetti Code
‘00s
Growing monoliths
‘10s
Microservices era

19. The reality today

20. Cloud Adoption
20162014

21. We at infra need to be an enabler for
developers. Enable automatic deployments
and roll-backs.
Creating tools/dashboards with relevant
KPI’s so that the developer can fast and
easily see the consequences of a deployment.
- Mattias Järnhäll, Infrastructure manager
2014.03.03 on Scania social network

22. in the early days…
DevOps movement
More features
quicker Stability

23. Smaller increments
enables stability
Today

24. DevOps @ Scania (2020)

25. “DevOps moments”

26. Version Control
Pull & Push several
times a day
Continuous
Integration
Server Target Servers
(Dev, Staging, Prod)
Version Everything
- Code
- Tests
- Configuration
- Database
- Infrastructure
10 minutes
Continuous Delivery is mandatory
Continuous Deployment is optional
Deploy
Orchestrator
… for application changes

27. Deploy frequency
• 2016
– Autonomous Teams
•Continuous Delivery
•30+ deploys per day
• Pre 2016
– Agile teams
•Continuous Integration
•12 deploys per year
• Pre 2012
– Software projects
•2-3 in parallel
•3 deploys per year
Biggest enablers
1. Microservice architecture
2. Trust and courage from
management

28. of
AWS Foundation Services
Compute Storage Database Networking
AWS Global
Infrastructure Regions
Availability Zones
Edge Locations

29. in
AWS Foundation Services
Compute Storage Database Networking
AWS Global
Infrastructure Regions
Availability Zones
Edge Locations
Client-side Data
Encryption
Server-side Data
Encryption
Network Traffic
Protection
Platform, Applications, Identity & Access Management
Operating System, Network, & Firewall Configuration
Customer applications & content
Customers

30. Application
Development
Delivery
Engineering
Infrastructure
Provisioning
Feature TeamsDeveloper Teams
Delivery Engineering
DevOps
Corporate IT
Corporate IT
Connected Services
Shared responsibility
Traditional silos

31. Application
Development
Delivery
Engineering
Infrastructure
Provisioning
Feature Teams
Delivery Engineering
Corporate IT
Connected Services
Shared responsibility
Manage their own
CI/CD pipeline
Infrastructure as Code
for their
Microservices
AWS accounting
IP-plan
Corporate Security
Cloud education
Common tooling
Common infra templates

32. Cloud movement

33. Zero Downtime

34. Infrastructure as a Ticket

35. Infrastructure as Code

36. Decisions
• Multi account
• Reduce blast radius
• Dev – One AWS account per team
• Prod – One AWS account for many teams
• Versioning our teams
• Team prefix
• Team cloud lead
• “Developers have full AWS access to the development environment
and we’ve just enabled read-only production IAM access”

37. Thank you!
…and yes, we are hiring cloud engineers:
https://www.scania.com/group/en/available-positions

38. AWS Code* Services
AWS CodeCommit AWS CodeBuild AWS CodeDeploy AWS CodePipeline

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

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

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

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

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

44. AWS Code Services
Source Build Test Production
Software Release Steps:
EC2 On-Prem
AWS CodeDeploy

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

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

47. Next steps
FOR GUIDANCE
Talk to a SA or our Devops specialized partners
HANDS ON
Available in the console!
LEARN MORE
aws.amazon.com/awscode

48. Thank you!