SlideShare a Scribd company logo
How Discovery Migrated 80% of
Their IT to AWS with Cloudreach
Tom Ray - Head of Cloudreach, USA, Cloudreach
Jarrod Carpenter - Project & Engagement Manager, Cloudreach
Sai Reddy Thangirala - Solutions Architect, AWS
What sets AWS apart?
Building and managing cloud since 2006
70+ services to support any cloud workload
History of rapid, customer-driven releases
16 regions, 42 availability zones, 68 edge locations
51 proactive price reductions to date
Thousands of partners; 2,700+ Marketplace products
Experience
Service Breadth & Depth
Pace of Innovation
Global Footprint
Pricing Philosophy
Ecosystem
What are customers achieving with the AWS ?
Scale
Consumes 40%
of US internet
bandwidth at
peak hours
Security
Believes they can be
more secure on AWS
than in any private
data center
Cost-Effectiveness
Has reduced total
cost of IT ownership
by 52%
High-Performance
Has reduced
latency by more
than 90%
Barriers to Cloud Adoption
Existing Investments Skeptical Stakeholders Upfront Costs
Application Interdependencies Fear of downtime during migration Lack of Cloud Expertise
Even if you’re ready to adopt, some real barriers make migrating
quickly and cost-effectively a challenge:
Overcome these barriers with AWS and APN Partners
APN Migration partners can help you:
Determine your migration
strategy
Get a clearer roadmap to
achieving your desired
end-state
Reduce project timeline,
cost, and risk
Keep your people
focused on business
innovation
Opportunity
evaluation
Operations and
optimization
Discovery,
analysis,
and planning
Design Migration,
integration and
validation
AWS Migration Process
AWS Core Migration Services
 AWS Application Discovery Service
 AWS Server Migration Service
 AWS Database Migration Service
 AWS Snowball
 AWS Snowball Edge
 AWS Snowmobile
Asset Discovery/Migration Data Transfer
Discovery Communications
 Discovery Communications, Inc. is a global mass media
and entertainment company
 The company started as a single channel in 1985, The
Discovery Channel
 Headquartered in Silver Spring, Maryland
 Discovery around the world: 220+ countries and
territories with 3 Billion global viewers
The challenge
Discovery chose AWS as their
preferred cloud platform.
Discovery set a goal of migrating
80% of their corporate IT
environment to the AWS Cloud
Discovery planned to move 20 datacenters
around the world onto AWS.
In the beginning...
 Have acquired several different companies with
varying infrastructures. The customer has elected
to move onto AWS to gain benefits of the AWS
cloud surrounding cost, simplicity and scalability.
 Selected AWS due to its strong reputation in the
market and the array of new services AWS
delivers, which align well to the needs of a media
company like Discovery.
Choosing a platform: Why AWS?
In the beginning...
Choosing a platform: Why Cloudreach?
Expertise Global footprint and
presence
Velocity and agility Cultural fit
Where we started: The Cloud Migration Assessment
High Level Design
 AWS design & connectivity
requirements
 High availability requirements
 Disaster recovery requirements
 Backup strategy and monitoring
requirements
 Security and compliance
requirements
 Billing, tags, and alerts
Governance and shared services
design in AWS
 Networking
 Connectivity
 Asset naming conventions
 Security
Availability/disaster recovery
Governance model
 Tagging
 Scheduling
 Billing model
 Cost-driven infrastructure
Cloud Migration Assessment Report
(CMAR)
 Initial scope (hosts & workloads)
 Workload migration path (AWS’ 6
‘R’s)
Migration Factory Design
 Tooling
 Initial schedule targets
 Resourcing
Security & Governance Migration Report & Plan
Time to complete: 8 weeks
Where we started: The Cloud Migration Assessment
~800 workloads across ~2,000
servers reviewed
Discovery’s assessment journey- Key achievements
Scope narrowed to 290+
workloads across 600+ servers
 Play-out workloads, retirement
targets, Exadata-based
workloads descoped
Global Workstream Design
Where we started: The Cloud Migration Assessment
Workloads spread across siloed business
units under DCI umbrella
Solution: Excellent communication &
collaboration, designation of key POCs
Solution: Iterative analysis and review
Solution: Direct engagement with
stakeholders AND leveraging in-place
monitoring solutions
Discovery’s assessment journey- Joint challenges
Assessing during in-progress CMDB
refresh effort
Limited penetration of automated estate-
discovery tooling
Where we’ve been: Shared services setup
Time to complete: 8 weeks
Tooling Procurement &
Project Preparation
 Tooling
 Project Preparation
Environment
Verification
Bonus!
Expedited Migration Targets
 Active Directory connectivity
 VPC configuration
 Security groups, IAM roles, etc.
 Paris disaster recovery site
 Miami-based datacenter
Where we are: Datacenter migration
How we do it: The Migration Factory
Design
 Deep-dive into workloads
 Builds on High Level Design
 Confirm migration path
 Execution of workload designation
 Rehost = “Lift & Shift” migration
 CloudEndure
 Build = Replatform
 CloudFormation
 Sceptre
 Build
 Handover AWS infrastructure
 Support end-user testing
 Migrate
 Cut-over coordination
 Support end-user testing
Build/Migrate Cut-Over & Test
Where we are: Datacenter migration
LLD and Prep
x
Apps
x
Apps
x
Apps
x
Apps
x
Apps
x
Apps
Build/Migrate
x
Apps
x
Apps
x
Apps
x
Apps
x
Apps
Cut-Over & Test
x
Apps
x
Apps
x
Apps
x
Apps
How we do it: The Migration Factory
1 Cloud Engagement Manager
1 Cloud Architect
1 Project Manager
2 Dedicated Cloud Team Members
2 U.S.-based Systems Developers
2 Paris-based Systems Developers
 InfoSec Support
 Network Team Support
 Platform & Infrastructure Team Support
 Application Owner Groups
Datacenter migration: Team composition
Where We Are: Datacenter Migration
Work on the Conveyor
Nordics datacenters
 Leveraging Cloudreach
U.S. & France
Paris datacenter 2
 Cloudreach France
 Support from Cloudreach
U.S.
Work Being Planned
 Globally distributed data
centers with smaller
workload counts
 SharePoint-based
workloads
Joint Challenges
 Maintaining velocity
amongst competing
Discovery responsibilities
 Homogenization of
infrastructure across BUs
Datacenters Migrated
 Paris data center
1 - 4 weeks
 Miami - 2 weeks
 U.S. data center
1 - 10 weeks
Week 19 of 40 – The journey continues….
Questions & Answers
Upcoming Events
Date: Wednesday, May 3rd
Time: 11:30am – 1:30pm CST
Location: AWS Office
227 West Monroe Street
Suite 1400
Chicago, Illinois 60606
Date: Tuesday, May 2nd
Time:11:30am – 1:30pm CST
Location: AWS Office
3333 Piedmont Road NE
4th Floor
Atlanta, GA 30305
Date: Wednesday, April 26th
Time: 12:30pm – 2:30pm EST
Location: AWS Office
7 West 34th St.
6th Floor
New York, NY 10001

More Related Content

How Discovery Migrated 80% of Their IT to AWS with Cloudreach

  • 1. How Discovery Migrated 80% of Their IT to AWS with Cloudreach Tom Ray - Head of Cloudreach, USA, Cloudreach Jarrod Carpenter - Project & Engagement Manager, Cloudreach Sai Reddy Thangirala - Solutions Architect, AWS
  • 2. What sets AWS apart? Building and managing cloud since 2006 70+ services to support any cloud workload History of rapid, customer-driven releases 16 regions, 42 availability zones, 68 edge locations 51 proactive price reductions to date Thousands of partners; 2,700+ Marketplace products Experience Service Breadth & Depth Pace of Innovation Global Footprint Pricing Philosophy Ecosystem
  • 3. What are customers achieving with the AWS ? Scale Consumes 40% of US internet bandwidth at peak hours Security Believes they can be more secure on AWS than in any private data center Cost-Effectiveness Has reduced total cost of IT ownership by 52% High-Performance Has reduced latency by more than 90%
  • 4. Barriers to Cloud Adoption Existing Investments Skeptical Stakeholders Upfront Costs Application Interdependencies Fear of downtime during migration Lack of Cloud Expertise Even if you’re ready to adopt, some real barriers make migrating quickly and cost-effectively a challenge:
  • 5. Overcome these barriers with AWS and APN Partners APN Migration partners can help you: Determine your migration strategy Get a clearer roadmap to achieving your desired end-state Reduce project timeline, cost, and risk Keep your people focused on business innovation
  • 6. Opportunity evaluation Operations and optimization Discovery, analysis, and planning Design Migration, integration and validation AWS Migration Process
  • 7. AWS Core Migration Services  AWS Application Discovery Service  AWS Server Migration Service  AWS Database Migration Service  AWS Snowball  AWS Snowball Edge  AWS Snowmobile Asset Discovery/Migration Data Transfer
  • 8. Discovery Communications  Discovery Communications, Inc. is a global mass media and entertainment company  The company started as a single channel in 1985, The Discovery Channel  Headquartered in Silver Spring, Maryland  Discovery around the world: 220+ countries and territories with 3 Billion global viewers
  • 9. The challenge Discovery chose AWS as their preferred cloud platform. Discovery set a goal of migrating 80% of their corporate IT environment to the AWS Cloud Discovery planned to move 20 datacenters around the world onto AWS.
  • 10. In the beginning...  Have acquired several different companies with varying infrastructures. The customer has elected to move onto AWS to gain benefits of the AWS cloud surrounding cost, simplicity and scalability.  Selected AWS due to its strong reputation in the market and the array of new services AWS delivers, which align well to the needs of a media company like Discovery. Choosing a platform: Why AWS?
  • 11. In the beginning... Choosing a platform: Why Cloudreach? Expertise Global footprint and presence Velocity and agility Cultural fit
  • 12. Where we started: The Cloud Migration Assessment High Level Design  AWS design & connectivity requirements  High availability requirements  Disaster recovery requirements  Backup strategy and monitoring requirements  Security and compliance requirements  Billing, tags, and alerts Governance and shared services design in AWS  Networking  Connectivity  Asset naming conventions  Security Availability/disaster recovery Governance model  Tagging  Scheduling  Billing model  Cost-driven infrastructure Cloud Migration Assessment Report (CMAR)  Initial scope (hosts & workloads)  Workload migration path (AWS’ 6 ‘R’s) Migration Factory Design  Tooling  Initial schedule targets  Resourcing Security & Governance Migration Report & Plan Time to complete: 8 weeks
  • 13. Where we started: The Cloud Migration Assessment ~800 workloads across ~2,000 servers reviewed Discovery’s assessment journey- Key achievements Scope narrowed to 290+ workloads across 600+ servers  Play-out workloads, retirement targets, Exadata-based workloads descoped Global Workstream Design
  • 14. Where we started: The Cloud Migration Assessment Workloads spread across siloed business units under DCI umbrella Solution: Excellent communication & collaboration, designation of key POCs Solution: Iterative analysis and review Solution: Direct engagement with stakeholders AND leveraging in-place monitoring solutions Discovery’s assessment journey- Joint challenges Assessing during in-progress CMDB refresh effort Limited penetration of automated estate- discovery tooling
  • 15. Where we’ve been: Shared services setup Time to complete: 8 weeks Tooling Procurement & Project Preparation  Tooling  Project Preparation Environment Verification Bonus! Expedited Migration Targets  Active Directory connectivity  VPC configuration  Security groups, IAM roles, etc.  Paris disaster recovery site  Miami-based datacenter
  • 16. Where we are: Datacenter migration How we do it: The Migration Factory Design  Deep-dive into workloads  Builds on High Level Design  Confirm migration path  Execution of workload designation  Rehost = “Lift & Shift” migration  CloudEndure  Build = Replatform  CloudFormation  Sceptre  Build  Handover AWS infrastructure  Support end-user testing  Migrate  Cut-over coordination  Support end-user testing Build/Migrate Cut-Over & Test
  • 17. Where we are: Datacenter migration LLD and Prep x Apps x Apps x Apps x Apps x Apps x Apps Build/Migrate x Apps x Apps x Apps x Apps x Apps Cut-Over & Test x Apps x Apps x Apps x Apps How we do it: The Migration Factory
  • 18. 1 Cloud Engagement Manager 1 Cloud Architect 1 Project Manager 2 Dedicated Cloud Team Members 2 U.S.-based Systems Developers 2 Paris-based Systems Developers  InfoSec Support  Network Team Support  Platform & Infrastructure Team Support  Application Owner Groups Datacenter migration: Team composition
  • 19. Where We Are: Datacenter Migration Work on the Conveyor Nordics datacenters  Leveraging Cloudreach U.S. & France Paris datacenter 2  Cloudreach France  Support from Cloudreach U.S. Work Being Planned  Globally distributed data centers with smaller workload counts  SharePoint-based workloads Joint Challenges  Maintaining velocity amongst competing Discovery responsibilities  Homogenization of infrastructure across BUs Datacenters Migrated  Paris data center 1 - 4 weeks  Miami - 2 weeks  U.S. data center 1 - 10 weeks Week 19 of 40 – The journey continues….
  • 21. Upcoming Events Date: Wednesday, May 3rd Time: 11:30am – 1:30pm CST Location: AWS Office 227 West Monroe Street Suite 1400 Chicago, Illinois 60606 Date: Tuesday, May 2nd Time:11:30am – 1:30pm CST Location: AWS Office 3333 Piedmont Road NE 4th Floor Atlanta, GA 30305 Date: Wednesday, April 26th Time: 12:30pm – 2:30pm EST Location: AWS Office 7 West 34th St. 6th Floor New York, NY 10001