Public presentation about Scania's Cloud migration. Why Scania goes for public cloud and how we organize and utilize cloud computing. New content is (among other details from latest learnings) an example on serverless code hosted on AWS.

2. The Cloud Journey in an
Enterprise
ANDERS LUNDSGARD, SCANIA CONNECTED SERVICES
2018-10-11, Copenhagen

5. • Why Cloud?
• How does Scania Cloud?
• Our Rules of Play
Agenda

6. ~350.000 connected vehicles
~150 engineers
~15 years old
Scania Connected Services
24/7
/5
(Q3 2017)

7. ~350.000 connected vehicles
~150 engineers
~15 years old
Scania Connected Services
24/7
/5
Anders Lundsgård
Senior Engineer, Delivery Engineering
@anderslundsgard
(Q3 2017)

8. ~350.000 connected vehicles
~150 engineers
~15 years old
Scania Connected Services
24/7
/5
Anders Lundsgård
Senior Engineer, Delivery Engineering
@anderslundsgard
(Q3 2017)

9. 9
Scania Connected Services
Message Platform
Remote Diagnostics
Fleet Management
Tacho
Does not scale!

10. 10
Scania Connected Services

11. • 3-8 people
• Requirements
• Technologies
• Quality
• Deployment
• Operations
11
Autonomous Teams that fully own their services

12. • 3-8 people
• Requirements
• Technologies
• Quality
• Deployment
• Operations
12
Autonomous Teams that fully own their services

13. Deploy frequency
• 2015
– Agile teams
• 12 deploys per year
• 2016
– Autonomous Teams
• Continuous Delivery
• 30+ deploys per day
• 2011
– Software projects
• 2-3 in parallel
• 3 deploys per year
1. Microservice Architecture
2. Trust and courage from
management
Continuous Integration

14. Version Control
Pull & Push several
times a day
Continuous
Integration
Server Target Servers
(Dev, Staging, Prod)
Version Everything
Code
Tests
Configuration
Database
Pipeline
Infrastructure
10 minutes
Deploy
Orchestrator
Reliable changes must also include Infrastructure
TO MASTER!!
Infrastructure

15. Quiz
Who is this?
15

16. Cloud
16

17. Cloud Adoption
20162014
Cloud First
2019
Cloud Only

18. Cloud – Return on Investment
Resistance
Legacy
Education
Value
benefits of
cloud

19. Organize for 1500+ Engineers
= Feature TeamFT DE = Delivery Engineering (Supporting)
DE
FT
FT
FT
FT
FT
FT
FT
FT
DE
FT
FT
FT
FT
FT
DE
FT
FT
FT
FT
FT
FT
FT
FT
FT
FT
FT
FT
FT
FT
FT
FT
FT
FT
FT
FT
FT
FT
FT
FT
FT
FT
FT
FT
FT
FT
FT
FT
FT
FT
FT
FT
Multiple other departments
co-located in same building
Cloud Adoption
Lift and shift
Greenfield
Dev-teams that move to
“DevOps”-teams with no
investment tend to struggle
in their cloud journey

20. Supporting Cloud engineers
What should they NOT DO?
20
Deployments

21. 1. Enabling feature teams to iterate as fast as possible
2. Cloud on-boarding and education
3. Core infrastructure
− Networking, IAM, DNS, …
4. Automation tooling
5. Security awareness
− Automated audits to Security Lead
− Security Compliance Validator (cfn_nag)
6. Cost awareness
− Billing reports to Cloud Leads
21
Supporting Cloud engineers mission

22. Key decisions in our AWS setup
Version Control
cloud enabled
AWS multi
account strategy
Immutable
infrastructure
In each
Feature Team!
Read Only in Prod
for human beings
FREE
NO
BASTION

23. 23
Warning – some code will be shown

24. Example – ScaniaCoin microservice
(Code for a backend API used in The Game by Scania)
API Gateway
Lambda
DynamoDB
GitLab CI

29. Code
Tests
Infrastructure
Database
Deployment Pipeline

30. …in the past…
Code is the same
as in the past
Tests are the same
as in the past
Manual
tweaks in
Jenkins pipe
Ordering of
servers
No patching of
servers
Order of DNS
aliases
Order of
backups
No licensing of
software
No downtime
on releases No downtime
on releases
Order of
FQDN in Load
Balancer
Order of
alarms
No capacity
planning
No order of
service users
No secrets!!

31. No heroes!

32. 32
Thank You!
Anders Lundsgård
@anderslundsgard