In this full-day workshop, you will learn strategies for planning and migrating existing workloads to the AWS Cloud, including basic knowledge of planning for a migration, Application Discovery Service, AWS Migration Hub, Migration Tools e.g. CloudEndure, how to do data transfer, and last but not least, AWS Database Migration Services. There are altogether 5 modules, each represents a deep dive on the topics suggested. The first half provides an overview of migration planning principles and best practices, and the second part focuses on migration design, tools and implementation, with hands-on labs to reinforce concepts.

1. © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.
The Migration Process

2. © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Re-factoring
(Re-writing/Decoupling
applications)
Redesign
Application/
Infrastructure Architecture
App Code
Development
Full ALM /
SDLC
Integration
Re-architect
(Replace -
Drop & Shop)
Purchase COTS/
SaaS & licensing
Manual Install
& Setup
Re-platform
(Lift & Reshape) Modify underlying
Infrastructure
Determine
new platform
Retain /
Revisit
Manual
Manual Config
Manual Deploy
Manual Install
Retire /
Decommission
Re-host
(Lift and
Shift)
Discover/Assess/Prioritize
Applications
Determine
Migration
Path
Use Migration Tools
Transition ProductionValidation
Automate
App Migration Patterns

3. © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.© 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.
A Closer Look At The 6 R’s

4. © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.© 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Retain (…And Revisit!)
• Unsupported OS and applications
• Legacy applications that do not have a
business justification for migrating to the
cloud
Physical Machine/Virtual Machine Image
App Binary
Operating System Files
Disk Volumes
Disk Drives
Memory
NIC
User Data
Retain Retire Rehost Replatform Refactor
Rearchitect
(Replace)

5. © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.© 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Retire
• Duplicate resources due to M&A
• Resources part of an existing
decommissioning program scope
• Clustered hosts for DR purposes
• Alternative HA hosts
Physical Machine/Virtual Machine Image
App Binary
Operating System Files
Disk Volumes
Disk Drives
Memory
NIC
User Data
Retain Retire Rehost Replatform Refactor
Rearchitect
(Replace)

6. © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.© 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Rehost
Physical Machine/Virtual Machine Image
App Binary
Operating System Files
Disk Volumes
Disk Drives
Memory
NIC
User Data
Amazon EC2
New Disk Volumes
Operating System Files
App Binary User Data
Rehost
• Servers running
packaged software
• Applications without
an active roadmap
• Ad hoc, dev and test
environments
Retain Retire Rehost Replatform Refactor
Rearchitect
(Replace)

7. © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.© 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Rehost Best Practice
• Utilize AWS and/or partner tools for increased velocity of your
migration initiative
• Set up Migration Factory with AWS/Partner help
• Evaluate and understand your infrastructure environment
• Challenge yourself to improved architecture
• Exercise migration before doing a cutover
AWS Server
Migration Service
(AWS SMS)
Retain Retire Rehost Replatform Refactor
Rearchitect
(Replace)
AWS DataSync

8. © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.
How CloudEndure Migration Works
Lightweight Staging Area
in Target Region
Source
Data Center
Target Subnet(s)
Continuous data
replication traffic
(compressed and
encrypted)
Lightweight Linux
Replication Server
Low-Cost
Block Storage
Orchestration &
system conversion
ready to run
workloads in
minutes regardless
of disk size
• CloudEndure continuously replicates any application or database from any source into AWS
• Business outcome: Allow self-service, rapid, reliable migrations with minimal business disruption

9. © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.
AWS Server Migration Service (SMS)
• Support VMware and Hyper-V VMs
migration
• Agentless VM migration
• Capture incremental change made
to on-premises VMs and
automatically transfer to AWS
• Migrate a group of VMs
simultaneously and orchestrates
multiple migrations
• AWS Management Console and
API/CLI access
• Launch EC2 instances from
Amazon Machine Images (AMI)
Source: On-premises server AWS Server Migration Service Target: Amazon Machine Image

10. © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Choosing Between CloudEndure Migration & SMS
Decision Factor Recommendation
What types of source infrastructure are
you migrating from?
• Prefer agent-less (hypervisor-based) approach for VMware and Hyper-V sources: SMS
• Prefer unified agent-based approach for multiple types of sources such as VMware, Hyper-
V, Physical, other clouds: CloudEndure
P2V servers? (on-premises virtual
servers previously converted from)
• Recommend CloudEndure
What level of automation are you looking
for in your migration?
• Two-step provisioning via launching AMIs (longer cutover window): SMS
• Target machines automatically provisioned (cutover in minutes): CloudEndure
Cutover window length? • OK with 1-hour+ cutover window: SMS
• Require cutover in minutes: CloudEndure
Looking to implement disaster recovery
in addition to migration?
• Recommend CloudEndure Disaster Recovery to help customers achieve sub-second
RPOs, RTO within minutes, point-in-time recovery, failover/failback.
• In addition to CloudEndure’s overall DR benefits, an existing DR deployment can be used
to proceed to a very simple migration using CloudEndure (no need to deploy or configure
anything else. Just cutover).
• Following a migration using CloudEndure, the customer can also easily enable cross
regional resilience in AWS using CloudEndure DR.
What type of storage needs to be
replicated?
• SMS requires VMDK-attached disks. Network-attached disks cannot be replicated.
• CloudEndure replicates any local/network disk presented to the OS as a block device.

11. © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.© 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Replatform
Physical Machine/Virtual Machine Image
App Binary
Operating System Files
Disk Volumes
Disk Drives
Memory
NIC
User Data
EC2
New Disk Volumes
Fresh New OS
App Binary User Data
Replatform
• Changing the OS or
DB engine
• Upgrading to the
latest release of an
application
• Upgrading the OS
from Windows 2003 to
Windows 2008/2012
• Upgrading from
Oracle 8 to Oracle 11
Retain Retire Rehost Replatform Refactor
Rearchitect
(Replace)

12. © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.© 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Replatform Best Practice
• Evaluate code dependencies on OS
• Identify any modifications required in the code to port it on a new
OS
• Consider hybrid environment and plan your migration appropriately
• Whenever possible, break up each functional component and test
them individually
• If environments are running in parallel, consider DNS switch method
post successful testing
AWS DMS
Retain Retire Rehost Replatform Refactor
Rearchitect
(Replace)

13. © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.
The order matters
On-Premise AWS Cloud
Database
DNS
AWS DataSync
File system Amazon Simple Storage Service (S3)
AWS DataSyncAmazon S3
VPN
Connection
Amazon Route53
InstanceInstance
InstanceInstance
InstanceInstance
InstanceInstance
Amazon RDS
Amazon Route53
Amazon VPC
AMS
DMS
Amazon RDS
Amazon EC2

14. © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.© 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Refactor
Physical Machine/Virtual Machine Image
App Binary
Operating System Files
Disk Volumes
Disk Drives
Memory
NIC
User Data
EC2
New Disk Volumes
New Operating System
App Binary User DataRefactor
• Changing middleware
• Recoding application
components
• Changing application
code to utilize cloud
native feature for
performance, scaling,
agility
Retain Retire Rehost Replatform Refactor
Rearchitect
(Replace)

15. © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.© 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Refactor Best Practice
• Scope your Refactoring initiative to a desired business outcome -
don’t make it a reengineering project
• Make sure your code is working as expected and baseline current
functionality and features
• Make sure you have documented test procedures (and tools) for
regular testing after each component of your code is refactored
• Use this as an opportunity to introduce good CI/CD practice and tools
- allow quick development, testing, rollout and rollback
AWS
CodePipeline
AWS
CodeCommit
Retain Retire Rehost Replatform Refactor
Rearchitect
(Replace)

16. © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.© 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Rearchitect (Replace)
Physical Machine/Virtual Machine Image
App Binary
Operating System Files
Disk Volumes
Disk Drives
Memory
NIC
User Data User DataRearchitect
$aaS on
Hosted Solution
• Changing from RISC to x86
• Changing application
components
• Rebuilding application
architecture
• Replacing the application
with a SaaS offering or
COTS product
• Purchasing a cloud-
compatible license
Retain Retire Rehost Replatform Refactor
Rearchitect
(Replace)

17. © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.© 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Rearchitect Best Practice
• Evaluate your options, not just from technical functionality perspective, but also
consider integrations with partners, financial viability, and security/compliance or
regulatory requirements
• Build and run in parallel and identify options to keep data between the on
premises and newer system in sync
• Test functionalities in batches; employee detail vs. sign-up vs. payroll and so on
• Identify user base that will be testing each functional component of the new
system, migrate in batches as well
Retain Retire Rehost Replatform Refactor
Rearchitect
(Replace)

18. © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.© 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved.
Mapping Drivers To A Migration Strategy
BusinessAgility/Value
Migration Effort
Low High
High
Retire
Retain (Revisit)
Rehost
Replatform
Refactor
Rearchitect (Replace)

19. Thank you!