Setting a goal for your teams to move a large number of workloads to AWS in a short period of time can be a great way to motivate teams to migrate quickly. Cardinal Health created a migration factory composed of teams, tools, and processes that streamlined the movement of workloads from on-premises to AWS. In this session, hear from Cardinal Health about how they used a migration factory to successfully move thousands of applications to the AWS Cloud. In addition, learn best practices for creating an effective migration platform and process in your organization.

1. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
AWS re:INVENT
How a G l obal Heal thcare Company Bui l t a
Mi grati on F actory to Qui ckl y Move Hund red s of
Appl i cati ons to AWS
P a t r i c k S t o n e k i n g – A W S A d v i s o r y S e r v i c e s
B r i a n H a n l i n , J o e D a l y – C a r d i n a l H e a l t h
E N T 3 2 0
N o v e m b e r 2 9 , 2 0 1 7

2. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
What can I expect from this session?
• Insight into leading practices supporting migrations of applications at scale using
the AWS Migration Factory process
• Understanding of how Cardinal Health built and leveraged their migration factory
to successfully migrate a large number of applications
• Insight into how Cardinal Health maximized operational cost optimization with
respect to Architectural Design and Operational Monitoring
• Actionable ideas to take back to the office to implement immediately

3. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
AWS Perspective on
Migration at Scale

4. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
CUSTOMER CLOUD CENTER OF EXCELLENCE (COE)
AWS CLOUD ADOPTION FRAMEWORK DELIVERY KITS
PROJECT
FOUNDATION
MIGRATION
REINVENTION
INNOVATION
RETIRE
TECH
DEBT
Value
Time
Today’s
focus
AWS Cloud Stages of Adoption

5. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Disconnected
and Incomplete Data
Asset
Inventories
CMBD
Tribal
Knowledge
SLA/OLA
App
Configuration
Data
Performance
Information
Architecture
Outcomes
Cost Model
Migration Patterns
Factory Model
Project Plan
Business Case
Gathering Data and Organizing
“Discovery & Planning”
AWS Application
Discovery Service
Applications
Infrastructure
Performance
So how do we get started?

6. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
• Project control
• Strategy (business
driver)
• Key stakeholders
and team
• Plan (scope,
schedule, resources)
• Cost estimation
• Portfolio discovery
• Migration plan
• Operational integration
Plan
• Prioritized backlog
• Application groups
• Migration strategy
• Success criteria
• Ops integration –
foundations and
landing zone (target
zone setup)
• Setup migration
factory (tools,
teams, process)
• Pilot migration
Activate
Execute
• Application
optimization
• Process optimization
• Operational
optimization
• Cost optimization
Optimize
Discover
Design
Build
Integrate
Validate
Cutover
AWS Migration Framework
Prioritized
backlog
(PLAN)

7. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
AWS Migration Patterns (Path to Cloud)
Discover/Assess/Prioritize
Applications
Use Migration
Tools
Transition Production
Retain
/ Not
Moving
Redesign
Application/
Infrastructure Architecture
App Code
Development
Purchase COTS/
SaaS & licensing
Validation
Modify underlying
Infrastructure
Full ALM /
SDLC
Manual Config
Manual
Deploy
Manual
Install
Retire /
Decommission
Determine
Migration
Path
Automate
Manual Install
& Setup
Integration
Determine
new platform

8. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
AWS Migration Factory

9. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Migration
Factory
Engineering
Office
Migration
Project Manager
Portfolio
Lead
Cloud Infrastructure
Architect
Cloud
Security Lead
Cloud
Operations Lead
Cloud
Applications
Business
Office
Executive
Sponsor
Migration Program
Manager
App
owners
and support
teams
Migration—Key Roles

10. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
AWS
ProServe
Advisor/
SME
App Migrators/Ops
Project Manager
Portfolio
Analyst
Security
Liaison
AWS Cloud
Architect
Database/
Storage
Migration Factory Tiger Team

11. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
TCO/Resource Planning Migration/Integration Tools Validation ToolsDiscovery Tools
Tools to Assist with Migration Scaling
AWS
Migration
Hub
AWS
Application
Discovery
Service
AWS
DMS
AWS
Snowball
AWS
SMS

12. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
And now the Cardinal story…

13. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Cloud Migration Program
(CMP)
Phase 1 Migration

14. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
37,000
employees
worldwide
on the
Fortune 500
#15
$120B+
annual revenue
Over
Acute Retail Physician
Offices
Manufacturer/
Supplier
Payor Patient
© Copyright 2016, Cardinal Health. All rights reserved.
CARDINAL HEALTH, the Cardinal Health LOGO and
ESSENTIAL TO CARE are trademarks or registered
trademarks of Cardinal Health.

15. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Why the cloud for Cardinal?
• The AWS cloud was identified in 2016 to assist with Cardinal’s goals of:
• Hardware/software savings
• Increased personnel efficiencies—self service, automation
• Increased speed, agility, and innovation to support Cardinal’s strategic
business goals

16. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Cardinal’s Migration Journey
1) Evaluate
Opportunity
2) Discover,
Analyze, and
Plan
3) Application
Design
4) Migrate,
Integrate, and
Validate
5) Operate and
Optimize
Application 3 Application 3
Application 2 Application 2
Application 1 Application 1
Existing IT
Estate
Evaluation
Planning and
Discovery
Operation

17. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Phase 1: Migrate, Innovate, and Learn
Cardinal’s Phase 1 Goals:
• Migrate 85% of the non-prod environment to the cloud
• Define and execute a repeatable and scalable migration factory
• Develop a backlog and prioritization process—focus on lift and shift with minor
re-platforming
• Perform server rationalization—focus on decommissioning where possible rather
than wholesale migration
• Identify and use tools as accelerators as appropriate
• Application discovery
• Server migration—Velostrata
• Data migration
• Innovate and experiment—develop leading practices for Phase 2

18. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Cardinal’s Cloud Migration Factory

19. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Results So Far
• Phase 1: From an initial list of 1,300 non-prod, Windows and Linux
servers to migrate:
• Migrated 750+ test/dev/QA servers to AWS
• Transitioned 200+ servers to AWS green field builds (new build)
• Retired ~30% of servers via Application Rationalization
• Phase 1 completed September 2017

20. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
What did Cardinal learn in Phase 1?
 Application Discovery is as important as the Migration itself. While migrating is
straightforward, understanding how all applications function and operate is a
challenge. Leverage tools as accelerators and force multipliers at every
opportunity
 Large-scale server migration can result in significant manual effort if tools and
a scalable factory process are not put into place.
 Complex application interdependencies are often poorly understood at project
start which makes a focused data discovery process key to success (example—
interoperability between on-premises DC and Cloud)
 Difficulty of testing server migrations iteratively makes them less confident
about the migration process

21. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Next Steps
• Phase 2: Stage/Prod Migration currently being planned
• Leveraging learnings and factory design from Phase 1
• 4000 Stage/Prod Servers expected to be migrated to AWS
• Expected start November 2017

22. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Cloud Migration Program—
Operate and Optimize

23. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Leading principle:
“Only pay for what we use”
• Simple concept to understand, harder to incorporate as part of the
culture of how we work
• Cost optimization is a culture change
• Reinforcement through continuous measurement and optimization

24. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Establish a Cost Optimization Team
Cloud Cost Optimization Team
Driving a culture of cost-conscious and active management of our IT and
business solutions
Right Sizing
• CPU
• RAM
• Network
bandwidth
• Instance
family &
generation
Right Storage
• Object storage
o Amazon S3 –
hot
o Amazon S3 - IA
– warm
o Amazon Glacier
– cold
• Block storage
• Snapshot
management
Increase
Elasticity
• Turn off
unused
instances
• Scheduled
starts and
stops
Right Pricing
• Reserved
Instances
• On-Demand
• Spot Instances
• “RI Czar”
o Purchases
o Modifications
o RI coverage
o RI utilization
Measure and Report
• Dashboards
• Reporting
• Recommendations
• Chargebacks
• Leading practices
• Case studies

25. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
So what was the Cardinal process?

26. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Step 1: Get the Size Right
• Utilize T2 family where applicable─great
for non-prod use
• Provision smallest viable resource, scale as
your requirements dictate
• Utilize AWS Linux as OS
*REMEMBER – EBS is charged based on the amount provisioned.
Only provision what you are going to use.

27. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Step 2: Automate Instance Run Time
Identify and stop instances with significant down time, especially non-
prod
• Tag every non-prod instance to “Stop” each night
• Automate the stopping process
• Teach app teams how to “Restart” environments when needed

28. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Step 3: Manage the Instance Portfolio
• Manage a Reserved Instance portfolio for the enterprise
• Buy convertible Reserved Instances where appropriate
• Cardinal’s focus is on leveraging three-year, $0 upfront, convertible RIs
• Actively manage: Exchange under-utilized RIs for needed RI coverage
• Pro tips Utilize instance size flexibility

29. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Step 4: Democratize the Data
• Chargeback for cost transparency
• Move costs to cost “causers”
• Utilize analysis and visualization tools such as Cloudability so solution
owners have visibility into environments and the resulting cost
implications
• Uncover “AHA!” moments
• Tags

30. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Results
• In four months, daily Amazon EC2 compute hours doubled while daily costs
went down
• Patience and persistence—this is a major change of perspective and it takes
time to change habits
• Change your scale—pay attention to nickels and dimes, they add up over the
course of a year
• Get Finance buy-in—Finance will become IT’s advocates

31. Remember to complete your
evaluations!

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