© 2015, Amazon Web Services, Inc. or its Affiliates. All rights reserved.

Keith Hochberg, Vice President, Cloud Services

Keith Carlson, EVP Services, 2nd Watch

October 2015

ISM201

Preparing for MigrationDeveloping a Roadmap to AWS for

7,700 Systems and 5 Global Data Centers

Welcome

Keith Hochberg, Vice President, Cloud

Services

Keith Carlson, EVP Services, 2nd Watch

What to Expect from the Session

• Developing a cloud strategy

• Cloud IaaS selection criteria

• How to approach a cloud migration

• Workload and organizational assessment

• Developing application dependency mapping

• Creating optimized cost estimates for cloud-ready

workloads

How our cloud journey began…

• Objectives

• Where can cloud services provide business

benefit? (Broke down our workloads into classes)

• Catalyst for data center consolidation

• Improve time to market and agility

• Improve transparency into cost

• Quickly scale for events

• Geolocate services

How our cloud journey began…

• We embraced OpenStack in early 2014 and improved

our service, but…

• We were still managing hardware and cloud software

• Couldn’t geolocate services

• Had to upgrade OpenStack every 6 months for new features

• Chasing public cloud service capabilities

• Migrated workloads to OpenStack (approx. 1,000 VMs) but

then paused

First steps toward public cloud

1. Created a cloud architect role that focused 100% on

cloud technology

2. Defined public cloud selection criteria

3. Started researching and testing public cloud service

providers

Public cloud IaaS criteria

• Global presence

• Maturity / variety of services

• Innovation pace

• Enterprise support

• Ecosystem of partners

• Pricing model

• Ability to show back cost by workload

• “Direct connect” options

What came next?

At re:Invent 2014, we concluded that AWS was the “right

choice”; now what?

How do we tackle this?

• Had to keep the OpenStack lights on

• Started selling it to upper management

• Secure budget

• Wanted to conduct a cloud readiness assessment

• Can we do this on our own?

Crossing the chasm

• This transformation was about more than technology

• We needed to understand the TCO

• We wanted validation of our foundational architecture

• We needed to understand how our development group would

leverage it

• We didn’t know how ready the organization was for this

change

• We did not have the time to do all of it ourselves NOW

Selection criteria for a partner

• Premier partner

• Skill set

• Ability to execute

• Knowledge of putting the solution together

• Customer service

• Mature team

Cloud readiness assessment

Cloud Readiness

Assessment

Operational Requirements

High Level Designs

Detail Level Designs

Application Dependency

Mapping

Cost Model and Resource

Tagging

Application Assessment

Migration Plan

Workload Cost Estimate

Staff Development

Plan

Developing a roadmap

• Organization readiness

• Foundational architecture

• Application mapping and assessment

• Cost model and governance

• AWS cost estimate and TCO

• Migration design and planning

Roadmap – Organizational readiness

When you know where you’re going…

• Will you be ready when you get there ?

Education is key for existing players

• Planned and executed strategic workshop for existing groups

• Met with individual team members

• Provide training plan by team, including budget estimate

• Provided living scorecard system for leadership to take action on

Design for long-term agility and manageability:

• Risk management

• Incident response

• Problem management

• Security and governance

Roadmap – Foundational architecture

• Requirements based design –

Both business and technical

• Define network topology and

security

• Understand and document

shared services (active

directory, LDAP, etc.)

• Establish not only a granular

design, but best practices for

extending the environment

(e.g., VPC and account

strategy)

Roadmap – Application mapping and assessment

• Discovery

• 7,000 servers across 3 data centers

• 1,000 applications

• Automated workload detection

• Collection of runtime metrics

• Identification of the network gravity of individual applications

• Manual workload discovery – How are applications used ? How

should they behave ? What do they do ?

• Assess and classify applications

• Re-host, Refactor, Revise, Rebuild, Replace

• Build an application dependency stack

• Prioritize applications for cloud migration (Re-host and Refactor

categories)

Roadmap – Cost model and governance

• Developed AWS resource tagging methodology

• Define tagging strategy (scope, tag keys, tag values)

• Define reporting structure and frequency for cost and

usage data

• Leverage 2W Insight

Roadmap – AWS cost estimate and TCO

• Used Automated Discovery activities to help develop a

more accurate baseline for Run-It costs on AWS

• Refined this estimate and laid a framework and

established best practices for ongoing financial

optimization.

• Conducted a “Gut Check” TCO comparison using these

numbers to validate expected savings

Roadmap – Migration design and planning

• Profile applications into similar patterns

• Recommended migration methodology and tools appropriate

for each given pattern

• Defined structure for migration team

• Developed a detailed migration process

• Developed Runbook templates for execution

• Piloted the migration with two applications

• Developed a high level plan identifying “waves” of

applications grouped together. Actual schedules to be

defined.

Where are we in the journey today?

• Executing on the multi-platform migration

• Transforming to DevOps

• Researching a new container model

• Finalizing our data center consolidation roadmap

Remember to complete

your evaluations!

Thank you!

Keith Hochberg, Vice President, Cloud Services

Keith Carlson, EVP Services, 2nd Watch