This session is aimed at those who want to learn how a large enterprise organization adapted their teams, tooling, and methodology to successfully migrate and operate business critical functions in the cloud. You also learn how the organization used migration as a launchpad for additional innovation. Session Sponsored by Cloudreach

1. Fitch Ratings: Migrating to the Cloud to
Transform Business Services Delivery
K e i t h H o c h b e r g – S r . D i r e c t o r – I n f r a s t r u c t u r e – F i t c h G r o u p
C h r i s L a l o r – D i r e c t o r – C l o u d E n g i n e e r i n g – F i t c h G r o u p
C l a r k W h i t e w a y – C l o u d E n a b l e m e n t L e a d e r – C l o u d r e a c h I n c
ENT317
November 29, 2017
AWS re:INVENT

2. Who We Are
Keith Hochberg
Sr. Director, Infrastructure
Chris Lalor
Director, Cloud Engineering
Clark Whiteway
Cloud Enablement Leader

3. Our 2 Year Journey:
2015 2016 2017
Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4
Get the
business ready
Get team ready Pilot Migrate!
Run
Ops

4. Get the business ready (6 critical months)
First 3 months: Discovery & Planning
• Engaged Cloudreach
• Conducted inventory of our estate
• Assessed costs and risks
• Developed preliminary plans
Next 3 months: Executive Buy-in
• Reviewed plans with Exec team,
Chief Risk Officer, Compliance, and
Board
• Recast plans to minimize risk

5. Our Business Case
• Objectives:
- Improve reliability, resiliency, and security
- More productive and flexible environment for
developers
- Lower infrastructure and support costs
• Think “cloud first” and “cloud only”
• Migration plans around carefully managing risk
- Strong partner
- Migrate in small increments
- Well-established governance, design, documentation,
test procedures, etc.
Migration Snapshot
by the numbers
100Applications
3,500 Users
55 Offices
30 Countries
Strategic
Planning and
Cost Modeling
Q1 2016

6. Get the team ready(6 critical months)
First 3 months: Build Discipline
• Build detailed designs
• Implement VPC, IAM, and AD
• Set up Packer, Bamboo, and Chef
• Develop preliminary plans
• Begin training early specialists
Next 3 months: Build Out
• Build Cloud Engineering group
• Create Checklists and Process
• Write recipes and stack templates
• Build basics for Financial Reporting

7. Building a Strong Foundation
Spent 6 months building foundational architecture.
Why?
• It starts at the ground up
• We are a highly regulated agency
• Wanted to migrate efficiently
• Moved DevOps tools to the cloud

8. Pilot: migrated Fitchratings.com

9. Migrate!(6 months)
KEY STRATEGIES
• Factory Approach
• Extensive testing, checklists &
documentation
• “Just move it!” …Every Week
• Regular stakeholder meetings

10. Team Structure for Migration
AWS Migration
Program Office
AWS Cloud
Engineering
Team
Migration
Factory
Security Testing
& Surveillance
Disaster &
Recovery
Testing
Development
Teams, Dev Ops,
QA, TAMs
Steering
Committee
Fitch
Cloudreach with Fitch
New Fitch Team

11. Our Migration Factory Approach
• The benefits of shifting to an agile process
• Just move it
• More in-flight = more opportunities to go live
• JIRA script for creating automated Epics per
app
• Migration Day every week
• Balancing velocity with engineering quality
• Focus on staff morale
• Documentation and Knowledge Transfer

12. Building with Epics

13. Weekly Migration Day
1
8
6
9
2
3
4
7
2
1
3
12
2
4
1
0
3
12
0
2
0
2
1
0
2
4
6
8
10
12
14
4-Jan
11-Jan
18-Jan
25-Jan
1-Feb
8-Feb
15-Feb
22-Feb
1-Mar
8-Mar
15-Mar
22-Mar
29-Mar
5-Apr
12-Apr
19-Apr
26-Apr
6-May
12-May
19-May
2-Jun
15-Jun
Aug.18
Applicationsmoved
Migration week

14. Run Ops:
OPERATING PRINCIPLES
• Pet to cattle
• Problem, Process, Toolchain
• GIT is critical
• Linking knowledge to commits
• Tag everything
• Partner with Finance -- cloudFin
TOOLS OF THE TRADE
• Chef, AWS CloudFormation, and
Cloureach Sceptre
• Languages of choice
• AWS Config and AWS Lambda for
DevSecOps

15. Discipline for Operating in the Cloud
Metric-driven
Engineering
Infrastructure
as Code
DevSecOps
Service
Optimization
Monthly
FinOps

16. Evolving our Discipline
• Leveraging new AWS services
• AWS Organizations
• Learning to build Cloud Native
• PaaS and containerization of workloads

17. Delivering Business Services with AWS
Nimbleness
PerformanceProductivity
Accountability

18. Summary:
OUR JOURNEY WHAT WORKED WELL
Get the business ready • 6 months – well worth it
Get the team ready
• Another great 6 months
• Hiring the key members
• Investing in design & base configuration
Pilot • Start small and slow
Migrate!
• Factory approach
• Move something every week
• Process, governance key
Run Ops
• Hand-off and phasing out of consultants
• Cloud best practices

20. Remember to complete your evaluations!

21. Thank you