1. AWS provides tools to facilitate hybrid IT and migration to the cloud in a step-by-step process.
2. A 5-step recipe is outlined for deploying hybrid IT, integrating operations, synchronizing data, transitioning load, and eventually decommissioning on-premises environments.
3. Hybrid IT is presented as an intermediate step toward fully migrating to the cloud ("All-In"), rather than the end goal, allowing organizations to build competence and confidence in AWS.
4. Three Claims
1. AWS provides rich tooling to facilitate migration to the
cloud.
2. Hybrid IT is a key component for cloud migration.
3. Hybrid IT is a step on the path to All-In,
NOT the destination.
5. Migration and hybrid IT offerings
The Obvious:
AWS
Import/Export
AWS Database
Migration Service
AWS Server
Migration Service
AWS Direct
Connect
AWS
CodeDeploy
AWS
OpsWorks
AWS
Directory Services
Amazon
WorkSpaces
Amazon Virtual
Private Cloud
AWS
Storage Gateway
6. Migration and hybrid IT offerings
The Non-Obvious:
Amazon
CloudFront
Amazon
Route 53
AWS
CloudFormation
AWS
WAF
Amazon
SNS
Amazon
API Gateway
Amazon
SWF
Amazon
SQS
Amazon
CloudWatch
AWS
KMS
7. 5-Step Recipe
1. Deploy hybrid IT
2. Integrate operational control
3. Synchronize data
4. Transition load
5. Decommission on-premises environment
8. Let’s bake this approach
Scenario
• My company, Awesome IoT!, sells IoT buttons.
• AWS IoT service is generating huge demand for our products.
• We must move our commerce platform into AWS to scale.
• We have minimal experience, and sunk cost in on-premises gear.
10. Goals:
• Establish network connectivity
• Deploy core IT services
• Migrate low-risk activities
• Build confidence/competence
1. Deploy hybrid IT
Actions:
• Create a VPC
• Deploy Direct Connect and/or VPN
• Configure Directory Services
• Launch WorkSpaces
11. Step 1
corporate data center
Internet
websrv1 websrv2
Load-Balancer
Load-Balancer
DNS Provider
adsrv2
adsrv1
us-west-2
Private Subnet A Private Subnet B
Public Subnet A Public Subnet B
12.
13. Goals:
• Unify operational management
• Build in-cloud Prod environment
• Deploy to both environments
• Build confidence/competence
2. Integrate operational control
Actions:
• Enable EC2 Run Command
• Integrate CodeDeploy
• Leverage OpsWorks
• Build Prod Environment
14. Step 2
corporate data center
Internet
websrv1 websrv2
Load-Balancer
Load-Balancer
DNS Provider
adsrv2
adsrv1
us-west-2
Private Subnet A Private Subnet B
Public Subnet A Public Subnet B
web1 web2
15.
16. Goals:
• Migrate data
• Enable local read & write tables
• Unify read data
• Build confidence/competence
3. Synchronize data
Actions:
• Deploy DMS
• Continuously replicate into AWS
• Add read-only tables on-prem
• Continuously replicate a unified
data view to read-only on-prem
• Split read and write on-prem
17. Step 3
corporate data center
Internet
websrv1 websrv2
Load-Balancer
Load-Balancer
DNS Provider
adsrv2
adsrv1
us-west-2
Private Subnet A Private Subnet B
Public Subnet A Public Subnet B
web1 web2
Write
Only
Read
Only
18. Caveats
• For most customers, simple cut-over works well.
• For this advanced pattern:
• Be aware of key partition requirements
• Understand your application well
• Accommodate propagation delay
• Plan for network partition impact
• Transition pattern, not an operational pattern
21. Step 4
corporate data center
Internet
websrv1 websrv2
Load-Balancer
Load-Balancer
DNS Provider
adsrv2
adsrv1
us-west-2
Private Subnet A Private Subnet B
Public Subnet A Public Subnet B
web1 web2
Write
Only
Read
Only
25. Next Steps
1. Identify a candidate workload.
2. Establish your hybrid IT environment.
3. Build confidence and competence with AWS services.
4. Unshackle your organization from on-premises limits.