AWS Migration

6R

rehost: lift and shift

simple migrations by re-hosting on AWS
no cloud optimizations being done, application is migrated as is
could save as much as 30 on cost
example
- migrate using AWS VM import/export, AWS Server Migration Service

replatform

example
- migrate your database to RDS
- migrate your application to Elastic Beanstalk
not changing the core architecture, but leverage some cloud optimizations

repurchase: drop and shop

moving to a different product while moving to the cloud
often you move to a SaaS platform
Expensive in the short term, but quick to deploy
example
- CRM to salesforce.com
- HR to workday
- CMS to Drupal

refactoring/re-architecting

reimagining how the application is architected using CloudNative features
driven by the need of the business to add features, scale, performance
example
- move an application to Serverless

Retire

turn off things you don’t need
helps with reducing the surface areas for attacks
save cost
focus your attention on resources that must be maintained

Retain

do nothing for now
it’s still a decision to make in a Cloud migration

Components

DMS/SCT

quickly and securely migrate databases to AWS, resilient, self healing
continuous data replication using CDC
must create an EC2 instance to perform the replication tasks
works over VPC peering, VPN, Direct Connect
supports Full Load, Full Load + CDC, or CDC only

CART

AWS Cloud Adoption Readiness Tool

helps organizations develop efficient and effective plans for cloud adoption and migrations
transforms your data of moving to the cloud into a detailed plan that follows AWS best practice
generate a custom report on your level of migration readiness

AWS Fault Injection Simulator

a fully managed service for running fault injection experiments on AWS workloads
Chaos Engineering - stressing an application by creating disruptive events, observing how the system responds, and implementing improvements

Application Discovery Service

plan migration projects by gathering information about on-premises data centers
server utilization data and dependency mapping are important for migrations
Agentless - AWS agentless discovery connector
Agent-based - AWS Application discovery agent
resulting data can be exported as CSV or viewed within AWS migration hub

AWS Application Discovery Service – Migration Hub Data Exploration

Allows you to use Amazon Athena to analyze data collected from on-premises servers during discovery
Data is automatically stored in S3 bucket at regular intervals
Use Pre-defined or custom queries in Amazon Athena to analyze data
Example: type of processes running on each server
Ability to upload additional data sources such as Configuration Management Database (CMDB) exports
Integrate Athena with QuickSight to visualize data

Application Migration Service

Lift and shift (rehost) solution which simplify migrating applications to AWS
converts your physical, virtual, and cloud-based servers to run natively on AWS
supports wide range of platforms, OSs, DBs
minimal downtime, reduced costs

Elastic Disaster Recovery

quickly and easily recover your physical, virtual, and cloud-based servers into AWS
example
- protect your most critical DB, protect your data from ransomeware attacks
continuous block-level replication for your servers

AWS Migration Evaluator

Helps you build a data-driven business case for migration to AWS
Provides a clear baseline of what your organization is running today
Install Agentless Collector to conduct broad-based discovery
Take a snapshot of on-premises foot-print, server dependencies, …
Analyze current state, define target state, then develop migration plan

AWS Backup

Fully managed service
Centrally manage and automate backups across AWS services
No need to create custom scripts and manual processes
Supported services:
- Amazon EC2 / Amazon EBS
- Amazon S3
- Amazon RDS (all DBs engines) / Amazon Aurora / Amazon DynamoDB
- Amazon DocumentDB / Amazon Neptune
- Amazon EFS / Amazon FSx (Lustre & Windows File Server)
- AWS Storage Gateway (Volume Gateway)
Supports cross-region backups
Supports cross-account backups
Supports PITR for supported services
On-Demand and Scheduled backups
Tag-based backup policies
You create backup policies known as Backup Plans
- Backup frequency (every 12 hours, daily, weekly, monthly, cron expression)
- Backup window
- Transition to Cold Storage (Never, Days,Weeks, Months,Years)
- Retention Period (Always, Days,Weeks, Months,Years)

Key Factors

Snowball Transfer Slow

Perform multiple write operations at one time – To do this, run each command from multiple terminal windows on a computer with a network connection to a single AWS Snowball Edge device.
Transfer small files in batches – Each copy operation has some overhead because of encryption. To speed up the process, batch files together in a single archive. When you batch files together, they can be auto-extracted when they are imported into Amazon S3.
Write from multiple computers – A single AWS Snowball Edge device can be connected to many computers on a network. Each computer can connect to any of the three network interfaces at once.
Don’t perform other operations on files during transfer – Renaming files during transfer, changing their metadata, or writing data to the files during a copy operation has a negative impact on transfer performance. AWS recommends that your files remain in a static state while you transfer them.
Reduce local network use – Your AWS Snowball Edge device communicates across your local network. So you can improve data transfer speeds by reducing other local network traffic between the AWS Snowball Edge device, the switch it’s connected to, and the computer that hosts your data source.
Eliminate unnecessary hops – AWS recommends that you set up your AWS Snowball Edge device, your data source, and the computer running the terminal connection between them so that they’re the only machines communicating across a single switch. Doing so can improve data transfer speeds.