This session provides an overview of how organizations can migrate workloads to the AWS cloud at scale. We will go through available migration frameworks and best practices with common use case examples during this session.

3. Application Migrations at Scale
Vijay Rangarajan
Senior Cloud Architect,
AWS Professional Services
Neal Ardeljan
Senior IT Transformation Consultant,
AWS Professional Services

4. What to expect in this session
US: Sharing our experience with high velocity migrations
at scale (>500 servers)
YOU: Will learn about proven migration patterns,
methods and tools that AWS has delivered successfully to
hundreds of enterprise customers globally that will help you
accelerate migrations, reduce risk and quickly realize
value

5. Why migrate to Cloud?
Higher cost of operating on-premise infrastructure
Disruption demands a response: innovation and agility

6. Typical Migration Challenges
Misconceptions about the cloud such as perceived security
concerns
Incomplete/outdated inventory of your IT portfolio
COTS and legacy applications that are not cloud ready
Skill gap of existing IT staff
Operations/Run function implications

7. We’ve helped Organizations of all sizes migrate to AWS

8. Condé Nast Migration
67 application groups
500+ servers
1PB+ storage
100+ databases
Cost Savings
&
Up-lift in Operational Performance
40%

9. Transformation - Stages of Adoption
Optimization
Migration
Foundation
Project

10. Cloud adoption is a journey
It requires planning and an adoption roadmap
Cloud adoption strategy should be aligned closely with business
goals and objectives
It can be disruptive and will drive significant change
Most start small, learn, iterate and accelerate
Value can be achieved quickly
Every journey to the cloud is different…

11. What is your
journey?

12. Migration Journey

13. Opportunity Evaluation

14. 7 Perspectives
Step-by-step process to build your cloud roadmap
Execution and delivery approach
Comprehensive framework to efficiently and effectively
align your cloud adoption journey to your business
objectives. The AWS CAF is comprised of:
AWS CAF:
7 PerspectivesAWS CAF whitepaper: http://bit.ly/AWSCAF
…Let the AWS Cloud Adoption Framework
be your guide

15. AWS CAF Core Perspectives
Process Perspective
Managing portfolios, programs and projects
to deliver expected business outcome on
time and within budget, while keeping risks
at acceptable levels.
People Perspective
Defining and acquiring the skills needed to
adopt the AWS cloud platform. Examples
guidance include role descriptions, training,
certification and mentoring.
Maturity Perspective
Defining the target state architecture of the
organization and creating the required
blueprints and roadmaps.
Platform Perspective
Represents the technology services of the
AWS cloud platform. Provides patterns,
guidance, and tools for optimal use of the
technology services and services to
implement.
Operating Perspective
Represents the ongoing management of the
functioning IT environment of AWS.
Provides process, guidance and tools for
optimum operational service management of
the AWS environment.
Security Perspective
Defining and implementing the required
levels of security, governance, and risk
management to achieve compliance.
Business Perspective
Identifying, delivering, and measuring
business impact using architectural
approaches that align technical delivery to
business imperatives.

16. Portfolio Discovery and Planning

17. AWS Application Discovery Service
Agents deployed on source hosts
Windows & Linux support
Capture system inventory, performance,
and dependencies
Capture and store secured data to AWS
API access to discovered assets
Output to CSV or XML
Can be imported into a third-party migration or
visualization tool
Discovery
Agents
Discovery DB
AWS Application
Discovery ServiceOn-premises data center
Encrypted
data
Internet

18. IT Portfolio Assessment

19. Migration Options

20. Migration
Pattern
Migration
Pattern Name
Pattern Description Example
Retain • Client will keep host/application in their source environment
• Minimal analysis/validation of scope and application affinity
• Dependency on integrating service management
• Mainframe
• Unix host / applications
• Offshore locations
Retire • Application and host decommission on source
• No migration to target
• Application owner approvals needed
• Existing decommissioning program
• UNIX, SCO, Clustered host for DR,
alternative HA hosts
Re-Host • Like for like application migration
• Minimal change to application architecture
• Storage migration will be needed (without conversion)
• UAT – Some level of application testing
• Simple to medium V2V, P2V
• Storage: Local to DASD
• RHEL 6 above
• Win 2008 Above
Re-Factor • Database to AWS RDS
• Middleware and application change to “cloudify” an application
• UAT required
• MS SQL same technology (RDS)
• Middleware, IBM products
Re-platform • Up-version of the OS and/or Database onto the target cloud
• OS and/or Database porting
• Storage migration will be needed (without conversion)
• Some level of application changes
• Data conversion; Database transition to MySQL, Aurora, etc..
• Application reinstallation on the target
• UAT is highly recommended
• W2K3 to Win 2012; Win 2008 below;
RHEL 6 below, Oracle 8 to 11; All
databases
• AIX to Linux
• Oracle to SQL, SQL to Aurora
• New application releases
• All clusters (MS clusters, DR)
Re-Architect • Application architecture changes may also require Up-Version or
Porting
• Middleware, data modernization, application consolidation/stacking
• UAT required; HPC Grid, No ITIL
• Any custom application change
• Complex / Highly complex application
migration
ApplicationModernization/ChangeEffort
R1
R2
R3
R4
R5
R6
Migration Patterns

21. Planning your Migration
Perform IT
Portfolio
Assessment
Plan
Cloud Unfit
Re-engineer
Cloud fit
Build
Re-Host
Replace
Refactor
Re-platform
Retain / Retire
A
B
C
TestingandIntegrating

22. Planning Your Migration
Migrating to the cloud can take one of many paths…

23. On-Premises Infrastructure Mapped to AWS – Compute, Storage &
Content Delivery and Networking
Technology On-Premises AWS
Network VPN, MPLS Amazon VPC, AWS Direct Connect
Storage DAS, SAN, NAS, SSD
Amazon EBS, Amazon S3, Amazon EC2 instance storage,
Amazon EFS, distributed & clustered FS on Amazon EC2
Compute Hardware, virtualization Amazon EC2, Amazon ECS, AWS Lambda
Content delivery Third-party CDN Amazon CloudFront
Load balancing Hardware and software load balancers Elastic Load Balancing, software load balancers
Scaling & cluster
management
Hardware and software clustering tools Auto Scaling, software clustering solutions
Archiving Tape library, off-site data storage Amazon S3, Amazon Glacier
DNS BIND, Windows Server, third party Amazon Route 53, third-party DNS software on EC2

24. Determine Optimal Architecture - Infrastructure
Application and service grouping
Visualize complex communication between
different resources and application
dependencies using auto discovery
Rate and performance detail
Understand latency and even loss % of
traffic between resources
Build capacity by location
Plan network capacity by understanding
location to location network requirements
Determine AWS environment
Instance sizing, DX or VPN, network
topology/IP addressing, security groups,
WAF, IDS/IPS, Elastic Load Balancer,
Amazon CloudFront, Amazon Route 53,
AWS Directory Service, network logging…
Communication density
between dependent
workloads
Dependent server & communication protocol

25. Determining Optimal Architecture - Applications
Application topology
Automatically discover and
visualize application topology
and interdependencies
Business transactions
Auto-discover end-to-end
business transactions and
performance
Determine AWS environment
Auto Scaling, Amazon RDS,
Amazon Redshift, Amazon
Aurora, Amazon SQS, Amazon
DynamoDB, Amazon EMR

26. Migration Prioritisation
AWS has developed an approach to collect, manage, and analyze application architectures.
This model leverages a weighted scale and prioritization to deliver a report identifying
logical application groupings for a phased migration into AWS.

27. Migration Factory

28. Application Migration Design and Planning Process
Solution Design
• Conduct Workshop
• Architect well-
defined Target
Infrastructure
Environment
• Select automated
migration tooling to
support app patterns
• Establish Security
and Governance
structure
Migration Plan
• Adopt agile sprint
planning
• Estimate migration
efforts
• Establish
performance
validation and
acceptance criteria
• Build migration
checklist and
execution plan
Pilot Run
• Conduct migration
pilot – Initial Trial
Run
• Validate assumption
and migration
checklist
Application Migration Execution Plan
A well-defined target environment with well-constructed fundamental services are
key success to migration factory and accelerate velocity.

29. AWS Application Migration Framework
Agile Migration Factory
Strategy Plan Build (Move) Run
DomainPhase
AWSMigrationProcess
AWSCloudAdoptionFramework(CAF)
Initiate Discover Design Migrate Integrate Validate Operate Optimize
Migration
Initiation
Application
Portfolio
Discovery
Application
Analysis
Migration Design Migration Integration Validation Operate Optimize
Services
Enablement
Baseline
Foundations
Build Plan/Team
Models
App Portfolio
Assessment
Build Pipeline
Architect Target
Environment
Application
Assessment
App Selection &
Prioritization
Execution Plan
Process & tools
refinement
Capture
Infrastructure
Move
Apps/Infra/Data
RightSizing AWS
Resources
Application
Integration
Infrastructure
Integration
Operational
Integration
Functional
Validation
Secure ACL
BU Acceptance
Monitoring
Daily Operations
Optimization
Support
50% Automation 50% Automation 30% Automation 50% Automation 50% Automation
Continuous Migration Evaluation and Feedback
Prioritized
Migration List
Migrated
Applications
Business
Strategy &
Objectives
Activities
MigrationMigration
Candidates

30. Migration Factory Considerations
Prioritize recent applications
Decommission old applications where possible
Iterate using sprints
Build a cloud centre of excellence to accelerate learning

31. Considerations Workload-oriented Activity-oriented
Scope Small to Medium size migrations (1-500 apps) Large size migrations (>500 apps)
Application Complexity Low to Medium High
Number of teams 1-4 9-10
Team Size 6-10 2-4
Agility (ability to shift
focus during a sprint)
High Low
Expertise in all
migration activities
High Low
Sprint scope All activities happen in sequence within a sprint
and each sprint must complete before moving to
the next.
Each activity is handled by a different sprint
team, sprints run in parallel and sprints from one
activity can overlap with another sprint’s activity.
Use case Team members have intimate knowledge of
applications and their underlying infrastructure.
Team members are highly specialized in their
activity (i.e.: discovery).
Sprint Team Design Options

32. Migration Sprint Team Considerations
Customer
Migration
Lead
Partner
Migration
Lead
Partner
Technical
Lead
Customer
Technical
Lead
Project Control Technical Leadership
Sprint Team #1
CIO – Executive Sponsor Cloud Migration Leader
Sprint Team #2 Sprint Team #4Sprint Team #3

33. Migration Sprint Team Structure
Additional Teams
Lift & Shift Migration
Migrates large quantities of simple
applications that don’t require
refactoring or re-platform. Heavy
utilization of migration automation
tools. Rapidly delivering large
quantities of small incremental
value
Re-Platform Migration
Designs, Architects, and migrates
more complex applications that
require a change of platform or a
change in application architecture.
Migrating fewer applications that
provide a higher return per
migration
Innovation
Works in coordination with
foundation, migration, and
transition teams to develop
repeatable pattern solutions
that will expedite migrations
and transition to operations
Lift and Shift
Migration
Teams
Re-Platform
Migration
Teams
Re-Factor
Builds and validates
appropriate foundational
components that ensure Dev,
Test, Prod environments are
scalable and appropriately
maintained and monitored
Re-Factor
Migration
Teams
Innovation
Teams
Core Teams
Foundations & Operations
Builds and validates
appropriate foundational
components that ensure Dev,
Test, Prod environments are
scalable and appropriately
maintained and monitored
Portfolio Discovery
Accelerates downstream
activities by executing full
application discovery and
rationalization. Works to
eliminate objections and
minimize wasted effort.

34. Migration Plan (Example)
1.0 MVP Month 0-3 1.1 Iteration-1 Month 4-6 1.2 Iteration-2 Month 7-9
Platform
Build
SDLC
CCoE
Application Migration
(Business risk appetite)
Demonstrate high
value apps on
AWS
Network, IAM &
Security
Financial
Reporting
Basic EC2, RDS, EBS Templates
Standard Pipelines & Developer Tools
Standard Cloud SOE
AMI Baking Process
Standard
Release, Change, Event
Management
Self-
Service
Service
Catalog
Move simple, low-
risk apps
Non-critical apps
move using CI/CD
Critical apps
move using CI/CD
Legacy apps
move using lift &
shift
SDLC Security, Resilience
& Compliance
Production ITIL workflow
automation
Incident, Problem,
Management
Production
Assurance
Testing
Value
Time
Usage spike as Self-
Service becomes
available

35. Migration Sprint Schedule (Example)
Q1 Q2 Q3 Q4
Productivity
3 Sprints
@2Wk
4-5 Sprints
@2Wk
4-5 Sprints
@2Wk
3 Sprints
@2Wk
R R R R 2Wk retrospective
Sprints Sprints Sprints Sprints
Datacenter
Decommissioning
2016 2017 2018
Q1 Q2 Q3 Q4
Productivity
R R R R
Sprints Sprints Sprints Sprints
Application/System Migrations
Q1 Q2 Q3 Q4
Productivity
R R R R
Sprints Sprints Sprints Sprints
Application/System Migrations

36. Migration Tools
AWS Snowball
Simple large-
scale data
transfer
AWS Database
Migration Service
Migrate between on-
premises and cloud
databases
VM Import /
Export
Deploy
workloads
across your
infrastructure
AWS
Marketplace
2,750+ products to
help you with
migrations and a
cloud operating model
AWS Server
Migration Service
Streamlines
migration of
existing
virtualized
applications

37. Migration Portfolio
Validation Tools
Optimization (Performance/Cost)
Discovery Tools TCO/Resource Planning Migration/ Integration Tools Service Management
Integrate Validate Operate Optimize
Cloud Management Service
Monitoring
CI/CD
Analysis Design
Discover Design Migrate
Transition Operate Improve

38. Migration Best Practices

39. Step 1: Identifying applications to move
Standalone applications are easy to move
Loosely coupled (SOA based integrations) applications are good candidates
New Applications have more documentation and organizational knowledge
Tightly Integrated Applications needs more planning
Low hanging fruit:
Dev/Test applications, self-contained web applications (LAMP stack), social media product marketing
campaigns, training environments, pre-sales demo portal, software downloads, trial applications
Watch out for…
32 bit, non-Linux/Windows, multicast clustered systems, engineered systems (Exadata, Netezza, NAS)
vertically challenged software/applications

40. Step 2: Conduct a TCO (Minimum Information)
Compute: Number of servers/VMs including RAM, CPU, OS, and boot drive size
(Amazon EC2)
Storage mapping to transactional, backup, archival,and log/file system/applications
(Amazon EBS, Amazon Glacier, and Amazon S3)
Region(s) where processing is happening
Data transfer out for networking
Internet or dedicated networking, including security requirements
(AWS Direct Connect and VPN)
Performance utilization of the current infrastructure and applications
License costs and support for Oracle, Microsoft, SAP, etc…

41. HA requirements for each workload (ELB, Amazon Route 53)
Scalability requirements for each workload (Auto Scaling, Elastic Load
Balancing, Amazon Route 53, Amazon CloudFront)
Disaster Recovery (DR) requirements for each workload
Storage IOPS requirements for each workload
Compute requirements for management/monitoring
Backup requirements for each workload that can not be supported by Amazon
EBS snapshots
Step 2: Conduct a TCO (Nice To Have)

42. Step 3: Migration Pilot
Answer tons of questions and get your feet wet with AWS quickly
Help identify gaps and touch points
Give you a correct estimation of the migration and
operational costs
Your initial migration will…
“There is no compression algorithm for experience”

43. Migration Success Stories

44. 4 Months
500 Servers
5 People
Australian Bank
Auto + manual discovery
Auto migration
24 Months
800 Servers
10+ People
Pharmaceutical Company
Manual discovery
Manual migration
Large Scale Migration
Retail Commerce
Manual discovery
Manual migration
6 Months /
150 Servers
10 People

45. Migration Success Factors
Build Migration Playbooks
Automate, Automate, Automate
Bring in your A-Team
Build a plan around Application Modernization
Deliberately scale your Migration Plan(s)

46. The AWS Cloud…
"AWS is our trusted partner that is going to run
our company for the next 140 years.”
Jim Fowler – CIO, General Electric
and move faster
What if you could devote more resources to
the things that matter
while being more secure?