In this workshop, we explore the AWS methodology for migrating Microsoft applications to AWS. We walk through the concerns and considerations to take into account while planning a migration. Learn how to develop and implement a migration plan to move applications from on-premises (or traditional hosting) to AWS. This session uses a case study format to dive deep into the details of how to successfully plan a Microsoft application migration.

1. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
AWS re:INVENT
Migrating a Microsoft ASP.NET
Application to AWS
J e s s e B u r g e s s , S o l u t i o n s A r c h i t e c t
N o v e m b e r 2 8 , 2 0 1 7
G P S W K S 4 0 6

2. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Workshop Format
11:30 – 12:00 Presentation
12:00 – 1:30 Case Study / Group
Exercise
1:30 – 2:00 Group Findings

3. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Migration
Fundamentals
Tools and Tips
for Partners
ASP.NET
Migration
Patterns
What to Expect from Today’s Workshop

4. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Innovation: Windows on AWS

5. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
The fundamental process around
migration — understand the benefits of
the new system, assess gaps in the
existing system, plan, and migrate —
hasn’t changed much over time.
Stephan Orban – Head of Enterprise Strategy AWS, https://medium.com

6. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
The Migration Process
A Process for Mass Migrations to the Cloud
Opportunity
Evaluation
Portfolio
Discovery and
Planning
Operate
Application
Design
Migration &
Validation

7. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
d e s c r i b e s a c o m m o n
j o u r n e y c u s t o m e r s t a k e
t o d r i v e i n n o v a t i o n a n d
v a l u e t h r o u g h
m i g r a t i n g t o t h e c l o u d
T h e A W S M i g r a t i o n
P a t h
LANDING ZONE /
FOUNDATION
EXISTING
APPS
1
4
2
1
3

8. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Landing Zone for Windows on AWS
A landing zone is a baseline AWS
environment that encompasses an
account strategy, network design,
foundational security, and identity and
directory services

9. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Landing Zone for Windows on AWS
• Network Design
• VPCs, Connectivity, Subnets
• NACLs, Security Groups, etc.
• IAM (AWS AuthN & AuthZ)
• Active Directory
• Key Management, SSL
Certificates
• Multiple Account Strategy
• Start simple
• AWS Organizations
• Security is the #1 priority
• Edge Security, Encryption, etc.
• Logging, Auditing, Config Mgmt,
etc.

10. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
What’s a typical migration
look like?

11. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Example Migration Sequence
• Account Structure
• Network / VPC
• Security
• Identity /
Active Directory
Step 1. Landing Zone
Private Subnet, 10.0.0.64/18
10.0.0.0/16
Public Subnet, 10.0.0.0/18
On-Premises Data Center
Domain
Controller
Amazon
Route 53
Domain
Controller
SQL
Server
SQL
Server
App
Server
App
Server
Web
Server
Web
Server
VPN /
DirectConnect
Security Prod
Root
Dev
Private Subnet, 10.0.0.64/18
10.0.0.0/16
Public Subnet, 10.0.0.0/18
On-Premises Data Center
Domain
Controller
Amazon
Route 53
Domain
Controller
SQL
Server
SQL
Server
App
Server
App
Server
Web
Server
Web
Server
VPN /
DirectConnect
Security Prod
Root
Dev
AWS Shield AWS WAF
CloudTrail
CloudWatch
VPC Flow Logs
Systems Mgr
Inspector
Config
Security Group
Security Group
Security Group
On-Premises Data Center
Domain
Controller
Amazon
Route 53
Domain
Controller
SQL
Server
SQL
Server
App
Server
App
Server
Web
Server
Web
Server
or
Active Directory
on EC2
VPN /
DirectConnect
Security Prod
Root
Dev
AWS Shield AWS WAF
AWS Managed
Active Directory
CloudTrail
CloudWatch
VPC Flow Logs
Systems Mgr
Inspector
Config

12. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Example Migration Sequence
Step 2. Database Tier
• Build out your DBMS
infrastructure
• Choose a database
replication and
synchronization strategy
• Backup/Restore migration
(manual/scripted approach
suitable for smaller
databases)
On-Premises Data Center
Domain
Controller
Amazon
Route 53
Domain
Controller
SQL
Server
SQL
Server
App
Server
App
Server
Web
Server
Web
Server
or
Active Directory
on EC2
or
SQL Server
on EC2
SQL Server
on AWS RDS
VPN /
DirectConnect
Security Prod
Root
Dev
AWS Shield AWS WAF
AWS Managed
Active Directory
CloudTrail
CloudWatch
VPC Flow Logs
Systems Mgr
Inspector
Config
• Zero-downtime migration
(software tool based
solution)
• Full-Diff migration
(manual/scripted approach
suitable for larger
databases)

13. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Example Migration Sequence
Step 3. Server / App
Migration
• Perform extensive testing at
this stage
• Production still being served
from on-premises
• Choose a server/app
migration strategy
• Manual migration (build new
servers – migrate data)
• Tool based migration (block-
level server migration and
synchronization)
On-Premises Data Center
Domain
Controller
Amazon
Route 53
Domain
Controller
SQL
Server
SQL
Server
App
Server
App
Server
Web
Server
Web
Server
or
Active Directory
on EC2
or
SQL Server
on EC2
SQL Server
on AWS RDS
VPN /
DirectConnect
App Server App Server
Web Server Web Server
Security Prod
Root
Dev
AWS Shield AWS WAF
AWS Managed
Active Directory
CloudTrail
CloudWatch
VPC Flow Logs
Systems Mgr
Inspector
Config
On-Premises Data Center
Domain
Controller
Amazon
Route 53
Domain
Controller
SQL
Server
SQL
Server
App
Server
App
Server
Web
Server
Web
Server
or
Active Directory
on EC2
or
SQL Server
on EC2
SQL Server
on AWS RDS
VPN /
DirectConnect
App Server App Server
Web Server Web Server
Security Prod
Root
Dev
AWS Shield AWS WAF
AWS Managed
Active Directory
CloudTrail
CloudWatch
VPC Flow Logs
Systems Mgr
Inspector
Config
Test Team

14. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Example Migration Sequence
Step 4. Production Cutover
• Plan your final cutover
carefully• Ensure any final replication
and/or synchronization
occurs
• Test your cutover
mechanism (DNS TTL, etc.)
• Maintain rollback (continue
after cutover if possible)
On-Premises Data Center
Domain
Controller
Amazon
Route 53
Domain
Controller
SQL
Server
SQL
Server
App
Server
App
Server
Web
Server
Web
Server
or
Active Directory
on EC2
or
SQL Server
on EC2
SQL Server
on AWS RDS
VPN /
DirectConnect
App Server App Server
Web Server Web Server
Security Prod
Root
Dev
AWS Shield AWS WAF
AWS Managed
Active Directory
CloudTrail
CloudWatch
VPC Flow Logs
Systems Mgr
Inspector
Config

15. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
ASP.NET migration
patterns

16. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
6R’s of Migration Patterns
6 Strategies for Migrating Applications to the Cloud
Rollback

17. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Rehost
a.k.a Lift & Shift - like for
like migration to the
cloud
Pros:
• Usually the fastest
migration strategy
• No architectural
modifications
Cons:
• Miss some “cloudy”
benefits of target platform
– both technical and
financial

18. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Rehost: EC2 Reference Architecture for Windows on AWS
Availability Zone 1 (AZ1)
Public Subnet
CloudFront
(Content Dist.
Network)
Internet
Internet
Gateway
WAF (Web
Application
Firewall)
NAT
GW
WAP/Proxy
/RDGW
Route53 (DNS)
Availability Zone 2 (AZ2)
Private Subnet
Domain
Controller
Web
Server
AWS Config
Systems Manager
Configuration &
Systems Management
Storage &
Archiving
S3
Amazon Glacier
Monitoring,
Auditing & Logging
AWS CloudTrail
Amazon
CloudWatch
DevOps
AWS
CodeDeploy
AWS
CodeBuild
AWS
CodePipeline
AWS
CodeCommit
AWS
VPN/
DirectConnect
Inspector
Certificate
Manager
IAM
Security, Certificate &
Key Management
CloudHSM
Security GroupSecurity Group
Web
Server
AutoScaling
AutoScaling
App
Server
Security Group
AutoScaling
AutoScaling
Security Group Security Group
Domain
ControllerSQL
Server
NAT
GW
WAP/Proxy
/RDGW
Web
Server
Security GroupSecurity Group
Web
Server
AutoScaling
AutoScaling
Security Group
App
Server
AutoScaling
AutoScaling
Security Group Security Group
Domain
ControllerSQL
Server
Public Subnet Private Subnet
Replica
Replica
Replica
Replica
Replica
Replica
AWS Shield
(DDoS)
Domain
Controller
Denver
MPLS
Domain
Controller
Domain
Controller
Always On
AG (Synchronous)
New York
VPC
Endpoint
WAP / ADFS Endpoint
ADFS
ADFS

19. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Replatfor
ma.k.a Lift-Tinker & Shift - like
for like migration to the
cloud with some
modificationsPros:
• Realize some benefits of
cloud platform
• Minimal architectural
modifications
Cons:
• Can be some rework
required

20. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Replatform: AWS Managed Services for Windows
Availability Zone 1 (AZ1)
Public Subnet
CloudFront
(Content Dist.
Network)
Internet
Internet
Gateway
WAF (Web
Application
Firewall)
NAT
GW
WAP/Proxy
/RDGW
Route53 (DNS)
Availability Zone 2 (AZ2)
Private Subnet
Domain
Controller
Web
Server
AWS Config
Systems Manager
Configuration &
Systems Management
Storage &
Archiving
S3
Amazon Glacier
Monitoring,
Auditing & Logging
AWS CloudTrail
Amazon
CloudWatch
DevOps
AWS
CodeDeploy
AWS
CodeBuild
AWS
CodePipeline
AWS
CodeCommit
AWS
VPN/
DirectConnect
Inspector
Certificate
Manager
IAM
Security, Certificate &
Key Management
CloudHSM
Security GroupSecurity Group
Web
Server
AutoScaling
AutoScaling
App
Server
Security Group
AutoScaling
AutoScaling
Security Group Security Group
AWS
Managed
Active
Directory
NAT
GW
WAP/Proxy
/RDGW
Web
Server
Security GroupSecurity Group
Web
Server
AutoScaling
AutoScaling
Security Group
App
Server
AutoScaling
AutoScaling
Security Group Security Group
AWS
Managed
Active
Directory
Public Subnet Private Subnet
RDS SQL Server
(Primary)
RDS SQL Server
(Secondary)
AWS Shield
(DDoS)
Domain
Controller
Denver
MPLS
Domain
Controller
Domain
Controller
New York
VPC
Endpoint
WAP / ADFS Endpoint
ADFS
ADFS

21. Customer VPC VMware Cloud VPCCustomer Data Center
AWS Direct
Connect
VMware Cloud
Endpoints
VPC subnet VPC subnet
VPC subnet
Private Managed
AWS ServicesCustomer Instances
vSphere Environment
VMware
Endpoints
Non-vSphere Environment
ESXi ESXi
Amazon EC2
Replatform: VMware Cloud for AWS
vCenter

22. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Repurchase
a.k.a Replace-Drop & Shop:
replace application with
Software-as-a-Service
platformPros:
• Minimize O&M going
forward
Cons:
• Lose Command &
Control

23. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Repurchase: Amazon WorkSpaces & Amazon
AppStream

24. AWS Elastic
Beanstalk
AWS
CodeDeploy
Amazon EC2 &
Auto Scaling
Replatform: Blue/Green Deployments on
AWS
Amazon
Route 53
ELB / ALB
Auto Scaling Group
Managed AD
Multi-AZ
SQL Server RDS
Multi-AZ
ElastiCache
Auto Scaling Group
50% 50%

25. Auto Scaling
Scale your infrastructure automatically
 Adds or removes
EC2 instances based
on metrics and
health checks
 No additional charge
 Minimize cost and
maximize
performance Availability Zone 2 (AZ2)Availability Zone 1 (AZ1)
Auto Scaling Group
Minimum Size: 2
Desired Size: 4
Maximum Size: 6
Auto
Scaling
Group
Launch
Configurati
on
Scaling
Plan

26. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Replatform: Blue/Green Deployments
Deployment process:
• Load balancer may or may not be
outside the Blue/Green boundary
• Deploy application with Blue Auto
Scaling Group
• DNS (Route53) points to load
balancer
• Load balancer directs all user traffic
to Blue environment
• Blue environment leveraging
backend services outside the
Blue/Green boundary
Amazon
Route 53
ELB / ALB
Managed AD
Multi-AZ
SQL Server RDS
Multi-AZ
ElastiCache
Auto Scaling Group
100%

27. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Replatform: Blue/Green Deployments
Deployment process:
• Initiate the Green environment via
new Auto Scaling Group
• the Green environment leverages
the same backend services
• Perform acceptance testing on
Green environment
• Scale up the Green environment to
prepare for Blue/Green switch
Amazon
Route 53
ELB / ALB
Auto Scaling Group
Managed AD
Multi-AZ
SQL Server RDS
Multi-AZ
ElastiCache
Auto Scaling Group
100%

28. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Replatform: Blue/Green Deployments
Deployment process:
• Shift traffic to the Green
environment via the load balancer
(AWS Elastic Beanstalk will
provision a new load balancer so a
DNS update is required to direct
traffic to the new load balancer)
• Continue to scale up the Green
environment
Amazon
Route 53
ELB / ALB
Auto Scaling Group
Managed AD
Multi-AZ
SQL Server RDS
Multi-AZ
ElastiCache
Auto Scaling Group
50% 50%

29. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Replatform: Blue/Green Deployments
Deployment process:
• All traffic is now being served by
the Green environment
• For rollback purposes the Blue
environment can be retained for a
period of time, be placed in standby
mode, shutdown, or terminated
• Rinse and repeat
Amazon
Route 53
ELB / ALB
Auto Scaling Group
Managed AD
Multi-AZ
SQL Server RDS
Multi-AZ
ElastiCache
Auto Scaling Group
100%
Amazon
Route 53
ELB / ALB
Auto Scaling Group
Managed AD
Multi-AZ
SQL Server RDS
Multi-AZ
ElastiCache
Auto Scaling Group
100%
Amazon
Route 53
ELB / ALB
Auto Scaling Group
Managed AD
Multi-AZ
SQL Server RDS
Multi-AZ
ElastiCache
Auto Scaling Group
100%

30. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Refactor
a.k.a Rewrite Application:
rearchitect application
leveraging cloud-native
features and services
Pros:
• Realize full
potential of
target cloud
platform
Cons:
• Requires the largest
investment and level of
effort to realize

31. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Refactor: Windows Containers on Amazon
ECS
• Increased Hardware
Utilization
• New Models for High
Availability
• Simplified IT Operations
• Simplified Application
Development
Guest OS Guest OS Guest OS
Guest OS Guest OS
Guest OS Guest OS
Status:on
Connections Connections Connections
Network Up/NetworkDown
Host OS / Hypervisor
Status:on
Connections Connections Connections
Network Up/NetworkDown
Host OS / Hypervisor
Guest OS Guest OS Guest OS
Guest OS Guest OS
Guest OS Guest OS
Status:on
Connections Connections Connections
Network Up/NetworkDown
Host OS / Hypervisor
Status:on
Connections Connections Connections
Network Up/NetworkDown
Host OS / Hypervisor
Guest OS
Operating System Virtualization:

32. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Refactor: Windows Containers on Amazon
ECS
Containerization:
• Increased
Application Density
• Increased OS
Utilization
• Environment
Standardization
• Promotes DevOps
Practices
Guest OS
Status:on
Connections Connections Connections
Network Up/NetworkDown
Host OS / Hypervisor
Guest OS Guest OS
Docker Container Engine
Cont ainer
App 1
Cont ainer
App 2
Cont ainer
App 3
Bins/Libs Bins/Libs Bins/Libs
Cont ainer
App 2
Bins/Libs
Container
App 3
Bins/Libs
Cont ainer
App 1
Cont ainer
App 2
Cont ainer
App 3
Bins/Libs Bins/Libs Bins/Libs
Cont ainer
App 2
Bins/Libs
Container
App 3
Bins/Libs
Cont ainer
App 1
Cont ainer
App 2
Cont ainer
App 3
Bins/Libs Bins/Libs Bins/Libs
Container
App 2
Bins/Libs
Container
App 3
Bins/Libs
Guest OS
Status:on
Connections Connections Connections
Network Up/NetworkDown
Host OS / Hypervisor
Guest OS Guest OS
Docker Container Engine
Cont ainer
App 2
Cont ainer
App 3
Bins/Libs Bins/Libs
Cont ainer
App 1
Cont ainer
App 2
Cont ainer
App 3
Bins/Libs Bins/Libs Bins/Libs
Container
App 2
Bins/Libs
Container
App 3
Bins/Libs
Cont ainer
App 1
Cont ainer
App 2
Cont ainer
App 3
Bins/Libs Bins/Libs Bins/Libs
Container
App 2
Bins/Libs
Container
App 3
Bins/Libs
Container
App 1
Container
App 2
Container
App 3
Bins/Libs Bins/Libs Bins/Libs
Container
App 1
Container
App 2
Cont ainer
App 3
Bins/Libs Bins/Libs Bins/Libs
Container
App 1
Container
App 2
Cont ainer
App 3
Bins/Libs Bins/Libs Bins/Libs
Container
App 1
Container
App 2
Container
App 3
Bins/Libs Bins/Libs Bins/Libs
Container
App 1
Container
App 2
Container
App 3
Bins/Libs Bins/Libs Bins/Libs
Guest OS
Docker Container Engine
Status:on
Conn ections Conn ections Conn ections
Network Up/NetworkDown
Host OS / Hypervisor
Guest OS
Docker Container Engine
Status:on
Connections Connections Connections
Network Up/NetworkDown
Host OS / Hypervisor
Container
App 1
Bins/Libs
Container
App 2
Bins/Libs
Container
App 3
Bins/Libs

33. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Refactor: Serverless .NET Core on Lambda
AWS
Lambda
Supports C#
December 1, 2016

34. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Refactor: Serverless .NET Core on Lambda
No Servers to Manage Continuous Scaling Subsecond Metering
Compute:
EC2
Three EC2 Instances:
= $10.44 / day
vs.
1042MB, HA, Bursts:
Scenario: 1,000,000 requests/day @ 200ms avg =
200,000,000ms / day
Compute:
Lambda
= $3.33 / day
c
4large
c
4large
c
4large

35. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Refactor: Serverless .NET Core on Lambda
Invoking Lambda from AWS Event Sources

36. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Refactor: Serverless .NET Core on Lambda
• Frontend of the AWS Serverless architecture
• Expose Lambda functions as HTTP API
• Manages authentication, versioning, monitoringAPI Gateway
API Gateway
CloudFront S3 Bucket
S3://www.yourspa.com
GetSchedule()
UpdateSchedule()
AddEvent()
AWS Lambda
DynamoDB
Route 53
AWS

37. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
How AWS can help

38. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Migration Tools From AWS & Partners
Data Transfer
AWS Storage and
File Gateway
S3 Transfer
Acceleration
AWS Direct
Connect
Amazon Kinesis
Firehose
AWS Snowball &
Snowmobile
AWS Database
Migration Service
Server and Database
migrations
AWS Server
Migration Service
Application Monitoring
/ Profiling
Amazon
CloudWatch
AWS Config
Discovery and planning
AWS Application
Discovery Service

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

40. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Make the APN Work for You
Go-to-
market
with AWS
6
Join APN Partner Programs
that Meet Specific Business
Needs
5
Move Up Partner
Tiers and Unlock
Benefits
4Get AWS Trained
and Certified
3
Build a
Business Plan 2
Join the AWS Partner Network (APN)1

41. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
APN Benefits*
• Sales Enablement
• GTM Benefits
• Credits & Funding
• Technical Training
• Technical Certifications
• Syndicated Web
Content
*APN Partner qualification requirements must be met to be eligible for some programs.

42. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
microsoft@amazon.com

43. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Re:Invent Sessions for Windows
GPSWKS407 - GPS: Strategies for Migrating Microsoft SQL Server Databases to
AWS
WIN204 - Simplifying Microsoft Architectures with AWS Services
WIN306 - Design, Deploy, and Optimize Microsoft SQL Server on AWS
WIN312 - Deploying .NET Application CI/CD Pipelines on AWS
WIN403 - AWS Directory Service for Microsoft Active Directory Deep Dive
WIN404 - How to Extend your Office 365 Investment to AWS
SID343 - User Management and App Authentication with Amazon Cognito
WIN402 - Extending VSTS Build/Release Pipelines to AWS

44. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Case Study: Example Corp Migration
• Grab a number & break into groups
• Limited amount of time:
• 1:00 – 1:15 - Read the case study
• 1:15 – 1:30 - Brainstorm, outline requirements &
define outputs
• 1:30 – 2:00 - Solutioning
• 2:00 – 2:15 - Start writing your out-brief
• Tips:
• Don’t sweat the details, just make assumptions (tech
or otherwise) and keep solutioning
• Give everyone (who wants to) 2 mins to share an idea
during the brainstorming step
• Nominate roles: note-taker, white-boarder, moderator,
etc.
1:00 – 2:15 Group Work
2:15 – 2:45 Group Findings
http://bit.ly/2jIxMgH
Example
Corp
http://bit.ly/2jIxMgH

45. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
THANK YOU!