Deck sobre Migração.

1. AWS – CloudMigration
Otavio PecegoCoelho
IT Transformation
Consultant

2. Presenter
Otavio Pecego Coelho
opecego@hotmail.com
IT Transformation Consultant
PhD em Informática – PUC-RJ

3. Agenda
• Overview of MigrationProcess
• Application Discovery
• Migration Strategies
• Migration Planning for MassMigration
• Migration Execution
• Operation & Optimization
• AWS MigrationTools
• AWS Migration Partners

4. How AWS customersaremigrating
Cloud AdoptionFramework
1) Evaluate
opportunity
2)Discover,Analyze
and Plan
3)Application
Design
4)Migrate,
Integrate,and
Validate
5) Operateand
Optimize
Application1
Application2
Application3
Application1
Application2
Application3
ExistingITState
Evaluation
Planningand
Discovery
Operation

5. Migration
Design
(Planning)
Migration Integration Validation
Business
Strategy
& Objectives
CCoonnttiinnuuoouussMiiggrraattiioonnEEvvaalluuaattiioonnaannddFFeeeeddbbaacckk
App Migration IterativeSprint
Migration Factory
Prioritized
MigrationList
Migr
Candi
ation
dates
M igrated
Applications
Application
Migration
Initiation
 Cloud Fit Assessment
 App Selection&
Prioritization
 Execution Plan
 Process& tools
refinement
 Capture Infrastructure  Application Integration
 Move Apps/Infra/Data  InfrastructureIntegration
 RightSizingAWSResources  Operational Integration
 FunctionalValidation
 SecureACL
 BUAcceptance
 Monitoring
 Optimization
 Support
 BusinessEnablement
 Early Cloud Adoption
 Portfolio
Assessment
 Collectdata
90% Automation 30%Automation
Application
Analysis
50% Automation
Portfolio
Discovery
50% Automation
Operate/
Optimize
50%Automation
AWSMigrationFactory

6. Best Practices
1.Pre-Migration
1. Haveaclear vision of where ITand business should overlap inthe
future
2. Outline and share aclear cloud governancemodel
3. Train staff early in theprocess
4. Spend time and effort outlining how operations will take shape in AWS
5. Know which ITassetsyou currently own and which you’re includingin
each migration
6. Select the right partner(s) to help you along the Journey
https://medium.com/aws-enterprise-collection/21-best-practices-for-your-cloud-migration-e406546cb66b

7. 7
Focadaem
Capacidades
deNegócio
Negócio
Realização de Valor
Pessoas
Papéis e Readiness
Governança
Priorização e Controle
Focadaem
Capacidades
técnicas
Plataforma
Aplicativos e Infraestrutura
Segurança
Risco e Conformidade
Operações
Híbrida e Dinâmica
Estágios da Adoção
Estágios da Adoção

8. 8
Os 4 estágios da adoção da nuvem
• A Nuvem é usada projeto
a projeto
• Resolve necessidade(s)
específica(s) para o cliente
• Internamente, poucas
habilidades com a Nuvem
• O cliente está provando
para si mesmo que a
Nuvem é uma opçãoviável
• A Nuvem amplia os
datacenters existentes
• Novos projetos são iniciados
na Nuvem
• De 3 a 5 aplicativos
corporativos na Nuvem
(produção)
• Treinamento e formação de
um Centro de Excelência
na Nuvem (COE)
• Estabelecidos os modelos
de segurança e
conformidade com aNuvem
• Preparando para
operações com Nuvem no
longo prazo
• O COE é estabelecido
• Papéis das tecnologias são
redefinidos
• Grupos de aplicativos de
produção e (ou) data
centers migram
• A Nuvem torna-se a
escolha padrão
• Novos modelos de
negócios são explorados
• Mudar de "Por que
Nuvem?" Para "Por que
não a Nuvem?"
• Mais confortável com as
operações na Nuvem do
que no local
Projeto Fundação Migração Optimização

9. Organizações que não obtêm sucesso na integração operacional
(especialmente na gestão de mudanças) veem sua adoção da Nuvem
parada e seus programas não conseguem atingir os resultados
desejados.
Optimisation
Migration
Foundation
Project
EstágiosdaAdoção
THE STALL

10. Need for a Foundation

11. Urbanism as an Example
Alternative to non-planning

12. App
AIAM
Internet
Perimeter
Load Balance
App
B
Segregation
Aplicação
A
(Homolog)
HighAvailability
App
A(DR)
Billing
Audit/Monitoring
BackUp
/ Arch
Integration
DC
Conection
Change /
Patch
Provisioning
Automation
Schedullers
Incident
Roles & Rights
Self
Service

13. App
AIAM
Internet
Perimeter
Load Balance
App
B
Segregação
DC
Connection
Aplicação
A(Homolog)
HighAvailability
App
A(DR)
Billing
Audit/Monitoring
BackUp /
Arch
Integration
Change /
Patch
Provisioning
Automation
Schedullers
Incident
Roles &
Rights
Self
Service

14. Urbanism in the AWS language

15. 15
Focadaem
Capacidades
deNegócio
Negócio
Realização de Valor
Pessoas
Papéis e Readiness
Governança
Priorização e Controle
Focadaem
Capacidades
técnicas
Plataforma
Aplicativos e Infraestrutura
Segurança
Risco e Conformidade
Operações
Híbrida e Dinâmica
Estágios da Adoção
Saiba mais sobre o CAF online:
https://d0.awsstatic.com/whitepapers/aws_cloud_adoption_framework.pdf
CAF – Cloud Adoption Framework

16. Best Practices
2. Migration
1. Start small andsimple
2. Automate
3. Approach the cloud astransformational
4. Leveragefully managed services wherever possible
3. Post-Migration
1. Monitor everything
2. Usecloud-native monitoring tools
3. LeverageAWS enterpriseSupport
https://medium.com/aws-enterprise-collection/21-best-practices-for-your-cloud-migration-e406546cb66b

17. Best Practices
4. For Mass Migrations
1. Build arobust migration factory made up of teams, tools, and
processes all centered around the migrationactivities
2. Provide leadership and set benchmarks for the migrationfactory
3. Havean onboarding process for new team members while theproject
is in full swing
4. Distribute talent judiciously acrossyour sprintteams
5. Consider many differentcriteria when deciding on the migration
strategy for aparticularapplication
6. Find patterns and create blueprints forthem
7. Test your applications
8. Ensure that aculture of over-communication is instilled in all teams
involved
https://medium.com/aws-enterprise-collection/21-best-practices-for-your-cloud-migration-e406546cb66b

18. Challenges
Toolscanhelp withthe belowchallenges
 Data center migrations can involve thousands of workloads and tens of thousandsof
servers.
 Large-scale server migration is a long and complex project with significant
manual labor.
 Complex application interdependencies thatare poorly understood.
 Identifying application inventory and dependenciesmanually slows down migration
process.
 Difficulty oftesting server migrations iteratively makes them less confident about
the migrationprocess.
 Long server downtime at cutover can incur additional business loss.

19. Application Discoveryand
Analysis Approach
• Semi-automated process with automation rate improving with tool
enablement
• Combination of AWSand partner discovery tooling with best practicesand
cloud assessment
• Requires light participation/ workshops withbusiness application owners –
minimal impact to businessunits
• App Portfolio Profiling is specific toeach customer/environment, but is
basedstandard AWSrationalization and prioritizationapproach

20. Application Discovery
& Analysis Process
Discov
er
ConductApp Discovery
Workshop
Implement tool based
discoveryenablement
Profiling app inventory &
assets
Interview AppOwners
Mapping ofApplication
Portfolio Identif
y
Identify app candidates
Capture inter-
dependencies
ConductApp Cloud Fit
Assessmentbasedon app
rationalization criteria
Evaluate Security & Data
Classification
Prioritiz
e
Sort and Rankapp
candidates list basedon
defined prioritization
criteria
Filter and Exclude app that
are anti patterns
Capture AppTCO
Develop AppPrioritization
Model
Cloud SuitableApplication MigrationRoadmap

21. Cloud Fit Assessment based on
Application Rationalization Criteria
• BusinessDrivers:
• Costreduction/EconomicsAnalysis – hardware, labor,
facility, support, maintenance, license costs, etc
• Data Classification (Criticality and Sensitivity)
• Security/RegulatoryCompliance
• Unsupported LegacyApp and LegacyOS
• LackEnterprise Support in Cloud
• Inconsistent DemandandWorkload
• Technology Drivers:
• Application TechnologyStack
• Application Performance, Utilization & Consumption
• Data/Storage/Network
• SecurityAssessment
• ServiceLevel/ Mission Critical/ Continuity–
HA/DR/Backup
Application Portfolio Data
Gathering
• Nameof the apps, technical owner, business
owner, cost rate/cost center
• App Characteristic (app framework, dev language,
data classification, data exchange, stateful vs
stateless session)
• App StackTier desc (inter-dependencies,
middleware, queues, database)
• Infrastructure desc(OS,network, ports/protocols,
security, virtualization, directory, NAS/CIF,
clusters)
• Number of systems: direct (exclusive), indirect
(dependent), non-prod (dev-test)

22. Defining Application Prioritization Criteria
• Businesscritically (supported business process andimpact,
frequency of use, sizeof user base,)
• Application complexity (technology stack,application
architecture, external interface,inter-dependencies)
• Environment Priority (Test-> Dev-> PreProd -> Prod)
• Environment Footprint (sizeof servers, file systems,database,
storage volumes)
• Transaction Workload (resource utilization for right
sizing/optimal AWSresources)

23. Application Prioritization Model
Example: this model leverages aweighted scaleand prioritization to deliver areport
identifying logical application groupings for a phased migration into AWS.
Exampleof Application PrioritizationReport
Criticality
Inter-Dependencies
Environment Footprint

24. AWS Application DiscoveryService
Automate datacenterapplicationdiscovery
IdentifyApplication MapApplication
Dependencies
Baseline Systemand
ProcessPerformance

25. AWS Application DiscoveryService
 Agents deployed on source hosts.Agentless
for VMWare.
 Windows & Linuxsupport
 Capture system inventory, performance,and
dependencies
 Capture and store secured data toAWS
Overview
 API access to discovered assets
 Output to CSV or XML
 Can be imported into athird-party
migration or visualization tool
DiscoveryAgents
AWSDiscovery
DB
AWS Application
DiscoveryServiceEncrypted
data
On-premises data centeror
VMware vCenter
Agentless
Discovery
Appliance
(StandaloneVM)

26. PartnerTools
Migration Technology for Discovery&Planning
https://aws.amazon.com/migration/partner-solutions/#discovery-planning

27. What’sNext?

28. Six Common Migration Strategies

29. ApplicationModernization/ChangeEffort
Migration
Pattern
Migration
PatternName
Pattern Description Example
R1
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
R2
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 HAhosts
R3
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 2008Above
R4
Re-Factor • Database to AWSRDS
• Middleware and application change to “cloudify” an application
• UAT required
• MS SQL same technology(RDS)
• Middleware, IBM products
R5
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 2008below;
RHEL 6 below, Oracle 8 to 11; All
databases
• AIX to Linux
• Oracle to SQL, SQL toAurora
• New application releases
• All clusters (MS clusters, DR)
R6
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
Migration Patterns

30. Typical Enterprise Portfolio Characteristics
Portfolio Tier Characteristics Typical Cases
Typical
Migration
Path
Best-fit
Operating
Model
Approx. %
Portfolio*
Differentiate
• High rate of change
• Possibly business-critical, not always
• Innovative and/or revenue generating.
• Customer-facing web apps
• Real-time Analytics
• Mobile, IoT, Big Data
Refactor DevOps ~20%
Table Stakes
• Low rate of change
• Business critical
• Highest availability/reliability required
• Systems of record
• ERP, CRM, Order/Logistics
• Legacy line-of-business
Replatform,
Repurchase
Steady-state
(high automation) ~30%
Commodity &
Craplications
• Low rate of change
• Non-business critical
• Standard availability/reliability required
• Productivity apps
• Non-business-critical
• Small customer-base
SaaS,
Rehost,
Retire
Steady-state
(low automation) ~50%

31. Planning Your Cloud Migration
• Now thatyou’ve gatheredallof theapplication andperformancemetricsfor each
server/applicationandhavedoneacomplete analysisandhaveconsultedwiththe
business/technologyteams:
 Decideonamigrationstrategy
 Retain;Retire;Re-purchase;Re-host;Re-platform;Re-factor
 Decideonapriorityandbuildthemigrationbacklog
 Identifytoolstohelpfacilitatethemigration
 Starttoarchitectanddesignwhattheoperationallandingzonewill looklike

32. Migration
Design
(Planning)
itized
ionList
M
Ca
 Execution Plan
 Process& tools
refinement
Business
Strategy
& Objectives
Prior
M igrat
Migration
Application
Application
Initiation
Portfolio
Analysis
Discovery
50% Automation 50% Automation
 Business Enablement
 Portfolio  Cloud Fit Assessment
 EarlyCloud Adoption Assessment  App Selection &
 Collect data Prioritization
Migration Factory
CCoonnttiinnuuoouussMMiiggrraattiioonnEEvvaalluuaattiioonnaannddFFeeeeddbbaacckk
App Migration IterativeSprint
igration Migrated
ndidates Applications
Operate/
Migration Integration Validation
Optimize
90% Automation 30% Automation 50%Automation
 Capture Infrastructure  Application Integration  Functional Validation  Monitoring
 Move Apps/Infra/Data  Infrastructure Integration  SecureACL  Optimization
 RightSizingAWS Resources Operational Integration  BUAcceptance  Support
AWSMigrationFactory
- Migration Design & Planning

33. Application Migration
Design & PlanningApproach
• Runaseries of workshops with BusinessUnits, AppOwners,
IT,InfoSec
• Architect well-defined future state targetenvironment
• Conduct Well-Architected Review
• Refine the selection of automated tools and theprocess
• Estimate migration schedule, efforts, and BUsimpact
• Create migration checklist and validation plan
• Build Migration ExecutionPlan
• Conduct amigration pilot - “test-run” to validate assumptions

34. Application Migration
Design & Planning Process
Solutio
n
Desig
n
ConductWorkshop
ArchitectWell-Defined
TargetInfra Env
AWSWellArchitected
Review
Select automated
migration tooling to
support apppatterns
Pla
n
Define migration sprint
planning andmilestones
Estimatemigration
efforts
Establish validation and
acceptancecriteria
Build migrationchecklist
and executionplan
ProcessRefinement
Conduct Migration Pilot
– Initial Trialrun
Refine automatedtools,
processes,and sprint
runs
ValidateAssumptionand
Migration Checklist
Migration ExecutionPlan
• Awell-defined target environment with well-constructed fundamentalservices are
key successto migration factory and acceleratevelocity.
• LeverageScrumFramework and conduct sprint planning meeting

35. Application Migration – Sprint Tasks Sample

36. Application Migration – Sprint Tasks Sample

37. Application Migration
Execution Approach
• Implement migration automation tools tocapture on premise
workload and move intoAWS
• Leveragehigh-speed data transfer solution orvirtual/physical
network appliance for large data transfer and database
migration
• Perform Integration for infrastructure, application,and
operation
• Conduct application functional validation

38. Application Migration Execution ProcessCreateInfra
Prepare Future
StateTargetEnv
Deploy core
infrastructure
services
Setup central
control source of
truth - accounts,
policy, credentials,
& permissions
CaptureApp/Infra
Prepon-premise
Infrastructure
readiness
Capture all relevant
apps/ imagesin
sequence per
prioritization report
DeployApp/Infra
Deploy captured
apps in target
environment
Right Sizingof AWS
Resources
MoveData
Determine data
migration approach
to use
Execute parallel run
if needed
Testdata
consistency
Deployed to AWSInfrastructure with configuration and migrateddata
• Thisstep should be highly automated withmigration tooling refinement and awell-

39. 1SERVER 10SERVERS 50SERVERS 100SERVERS
Total Man HoursSpent
Manual Migration
Semi-Automated Migration
FullyAutomated Migration
Need to continuous fine-tune the tool for theenvironment
Migration Costs VariesNumberofManHours/Efforts

40. Application Migration ToolApproach
• Racemi
• CloudScraper
OSCloning
• CloudVelox
• CloudEndure
DRReplication
• AWS VM Import / AWS SMS
• Rivermeadow
• Hotlink
• Ravello
VM Conversion
• AppZero
• C3DNA
• Cliqr
AppContainer
AWS

41. AWSDirect
Connect
Solution
Providers
(Aspera,
Riverbed,
Tsunami,Ctera)
Transferto S3
overInternet
AWSImport
Export / Snow
Family
GBs TBs
VelocityofData
Days
Sizeof Data
LargeData Migration Approach
Hours

42. Milestone
Activities
Deliverables
Table
Migration
Stored Proc & otherDB
objects Migration
Schemaverification
& DataValidation
 Migrated table schema
 Migrated user accounts.
 Unit Test results
 Migrated SP, Functions,
Triggers code
 Unit Test results
 Perform Schema
Comparison of
tables, indexes,
 Perform data
verification
between source
and target
database.
 Custom data
migration scripts
 Migrated data to
target database
 Unit Test results
Data
Migration
Migrate Table Schema
from Source to target
Database
Migrate user accounts
and permissions from
source to target DB
 Migrate SP,Functions and
other DB objects from
source to target DB
 Perform unit testing of the
migrated schema asper
test plan.
 Set up data
migration scripts
 Perform data
migration
 Unit testing of data
migrated from
source to target DB
 Complete
migration to SQL
Server database
with schema
objects and data
Database Migration Approach
Awide selection of partner and vendor tools (AWS included)

43. Migration Execution – Integration
• Strongly depends on the application and customerenv:
• Infrastructure Integration
• AWSnetwork pipe and connectivity, security group, VIP,DNS,firewall rulesetc
• Application Integration
• re-establish external data sources, app inter-dependencies (accessmanagement,
middleware, queues, enterprise bus)
• Operational Integration
• SSO/AD,Monitoring, Backup, Patching, Update CMDB,Onboarding Procedure to
Cloud Management Platform
• Best practices – useof FQDNsvshard coded IPaddresses

44. Migration Execution – Validation
• Focuseson functional validation and businessacceptance
criteria
• Level of automation dependson
• Functional validation, smoke tests, performance baseline test andetc
• Leverage existing testing tools, invest in building automated test scripts and test
scenarios
• Review roll back procedure(optional)
• Schedule Cut over
• Best practices – implement continuous integration,automate
your build, automate yourdeploy

45. nitori
ed
ons
Operate/
Optimize
50%Automation
Migration Factory
Business CCoonnttiinnuuoouussMMiiggrraattiioonnEEvvaalluuaattiioonnaannddFFeeeeddbbaacckk
Strategy
& Objectives App Migration IterativeSprint
Prioritized Migration Migrat
M igration List Candidates Applicati
Migration
Application
Application
Migration
Initiation Portfolio Analysis Design Migration Integration Validation
Discovery (Planning)
50% Automation 50% Automation 90% Automation 30% Automation
sEnab p Portf Fit As nfrastr tion In ctiona
s
u
AWSMigrationFactory
- Operation andOptimization
(Part 4 of AWSApp MigrationMethodology)

46. Post Migration – Operate & Optimize
Configuration
Management
Deployment
Management
Source
Control
Service
Management
Monitoring
Management
Data/Log
Management
Performance
Management
Security
Management
Cost
Management
Cloud
Management
Services
AWS IaaS Platform
Customer IT Operation/Optimization

47. AWS MigrationTools

48. AWS Server MigrationService
Automate the end-to-end server migrationprocess
Automates an incrementalreplication
of live servervolumes to AWS
Orchestrateslarge-scale
server migrations
Migrate serverstoAWS in a
cost effectivemanner
Support most widely usedoperating
systems
Manage migration and track
the process easilywith a GUI
Reduceserver downtime atcutover

49. AWS Server MigrationService
Overview
 Support VMware VMs migrationwith the
initial release
 Windows & Linuxsupport
 Agentless VM migration
 Capture incremental changes made toon-
premises VMs and transfer toAWS
 Create migration waves
 AWS Management Console and
API/CLI access
 Launch EC2 instances fromAmazon
Machine Images (AMI)
AWS ServerMigration
Service
On-premises VMware VMs
VMs
AMIs

50. AWS SMS Steps

51. AWS SMS Steps

52. PartnerTools
Migration Technology for WorkloadMobility
https://aws.amazon.com/migration/partner-solutions/#workload-mobility

53. AWS Database Migration Service(AWSDMS)
DMS migrates databases to AWS easily and
securely with minimal downtime. It can
migrate your data to and from most widely
used commercial and open-source
databases.
AmazonAurora

54. How does it work

55. Characteristics
• The source database remains fully operational during the migration, minimizing downtime
to applications that rely on the database.
• The AWS Database Migration Service can migrate your data to and from most widely
used commercial and open-source databases.
• The service supports homogenous migrations such as Oracle to Oracle, as well as
heterogeneous migrations between different database platforms. It also allows you to
stream data to Amazon Redshift, Amazon DynamoDB, and Amazon S3 from any of the
supported sources,
• which areAmazonAurora, PostgreSQL,MySQL,MariaDB, Oracle Database, SAPASE,SQLServer, IBM DB2
LUW,and MongoDB.
• AWS Database Migration Service can also be used for continuous data replication with
high-availability.
• When migrating databases to Aurora, Redshift or DynamoDB, you can use DMS free for
six months.

56. Heterogenous
Migration
Consolidation
& Migration

57. Continuous Data
Replication

58. AWS SchemaConversion Tool(AWSSCT)
SCT helps automate many database schemas
and code conversion tasks when migrating
between database engines or data warehouse
engines
AmazonAurora

59. AWS Database MigrationService
Overview
 Keep your applications running duringthe
migration
 Start areplication instance
 Configure both databaseendpoints
 Select tables, schemas, ordatabases
On-premises Database
 Switch applications over to the target at
your convenience as AWS DMS keeps
the target database in sync.
 Wide support of databases
 Homogeneous migrations (ex: Oracle to
Oracle)
 Heterogeneous migrations (ex: Oracle to
AmazonAurora)
AWS
Database
Migration
Service

60. AWS SCT Console
1. SourceDatabase Schema
2. Actions items
3. TargetDatabase Schema
4. Schemaelement properties
5. SQLcommand to create targetelement

62. PartnerTools
Migration Technology for Database IntegrationandManagement
https://aws.amazon.com/rds/partners/#Database_Migration

63. AWS MigrationHub
• Provides a single location to trackthe progress of applicationmigrations across
multiple AWS andpartnersolutions.
• Also provides keymetrics and progress for individualapplications,regardless of
which tools are being used to migratethem
• View the migrationprogress of allthe resources in the application.
• Allows you to quickly getprogress updates across allof your migrations,easily
identify and troubleshootanyissues
• Thereis no additionalcostfor using Migration Hub

64. Liftand Shift:AWS Snow Family
Snowball Snowball Edge Snowmobile
Petabyte-scale data
migration
Compute & Storage for
Hybrid/Edge workloads
Exabyte-scale data
migration

65. AWS Import/ExportSnowball
Overview
 ExtremelyScalable
 Singleapplianceup to 50 TB or 80 TB
 Multiple appliancescanbe used in parallelto
transfer Petabytes ofdata.
• Highspeed
 10GBaseT networkconnection.
 Programmable
 Snowball job managementAPI
 Snowball S3Adapter
 Tamper resistant and secure
 256-bit encryption keys managed by
AWS Key Management Service
On-premises Data
Fast
Elastic
Costeffective
10G network
50TB or 80TBcapacity

66. AWS SnowballEdge
Petabyte-scalehybrid devicewith onboard compute and storage
• 100 TB local storage
• Local compute equivalent to anAmazon
EC2 m4.4xlarge instance
• 10GBase-T, 10/25Gb SFP28, and 40Gb
QSFP+ copper, and optical networking
• Ruggedized and rack-mountable

67. Snowball Edge keyfeatures
S3-compatible endpoint
File interface (NFS)
Clustering
Run AWS Lambda functions
Faster data transfer
Encryption

68. Amazon Snowmobile
• Exabyte-scale data transferservice
• Each Snowmobile can transfer up to
100PB
• Connects to your networkvia
removable high-speed networkswitch
• Appears as network-attacheddata
store
• Data encrypted with256-bit
encryption keys, managed
through KMS
• Snowmobile driven back to AWS
and data is loaded into S3,
Redshift, Glacier

69. Snowball Edge: Remote DataCollection
Customer Example: Oregon StateUniversity
• Collect and analyze oceanic and coastal images (60TB/week)
• Environmental and ocean ecosystemresearch
• Prior to Snowball, used many small HDDs – took weeks to months to upload
• $4MM+ in infrastructure investment --Expensive and inefficient
• Customer Quote: “Snowballletsus migrate TBsof datain daysata
fraction ofthecost”

70. Storage Gatewayhybrid storagesolutions
Use standardstorage protocolstoaccess AWS storage services
AWSStorage
Gateway
AmazonEBS
snapshots
AmazonS3
AmazonGlacier
AWS IdentityandAccess
Management(IAM)
AWSKeyManagement
Service(KMS)
AWSCloudTrail
Amazon
CloudWatch
Files
Volumes
Tapes
On-premises
AWSCloud

71. Where does Storage Gateway store data?
us-east-1
Storage Gateway Service
Data Center
iSCSI
HTTPS

72. FileGateway
On-premises filestorage maintainedas objectsinAmazonS3
CustomerPremises
Data stored and retrieved from your Amazon S3 buckets
One-to-one mapping from files-to-objects
File metadata stored in object metadata
Bucket access managed by IAM role you own and manage
Use S3 Lifecycle Policies, versioning, or CRR to manage data
GlacierS3Standard S3 Standard-
Infrequent
Access
HTTPS
NFS
v3 /v4.1
Application
Server
Storage
Gateway
Storage
GatewayVM

73. FileGatewayusecases
Storage
GatewayVM
NFSclient
RefreshCache
Amazon
EMR
In-cloudworkload
S3 Bucket
Amazon
Athena
Amazon
QuickSight
S3 Bucket
Snowball +Gateway
NFS
client
Storage
GatewayVM
RefreshCache
S3 BucketRead-onlyNFS
client
Crossregion
replication
FileSharing
SiteB
SiteA
NFS
client
Storage
GatewayVM

74. Application
Server
VolumeGateway
• Block storagein S3 accessedviathevolume gateway
• Compression of data in-transitand at-rest
• Backupon-premises volumes to EBS snapshots
• Create on-premises volumes from EBSsnapshots
• Up to 1PB of totalvolume storagepergateway
AmazonEBS
snapshots
Storage
Gateway
Service
On-premises volumestorage backedbyAmazonS3 withEBS snapshots
CustomerPremises
iSCSI HTTPS
Volume
GatewayVM
Volume Storedin
Amazon S3

75. TapeGateway
Virtualtapestorage inAmazonS3 andAmazonGlacierwithVTLmanagement
Virtual tapestorage in S3 and Glacier accessedvia tapegateway
Data compressed in-transitandat-rest
Up to 1 PB totaltapestorage per gateway,unlimited archivecapacity
Supports leading backupapplications
**3-5 hour taperetrievalfromAmazon Glacier
ArchivedTapes
stored in
AmazonGlacier
MEDIA
CHANGE
R
TAPE
DRIVE
CustomerPremises
VirtualTapes
stored in
AmazonS3
Backup
Server
HTTPSiSCSI
Tape
Gateway
Tape
GatewayVM

76. Backup,archive,and disasterrecovery
Cost-effectivestorage inAWS withlocalor cloud restore
“Tapesare a headache, prone with hardware
failures, offsite storage costs, and constant
maintenance needs. Storage Gateway provided the
most cost-effective and simple alternative. We
even got disaster recoveryby using a bi-coastaldata
center.”

77. GlacierS3Standard S3-Infrequent
Access
FileGateway
PetroBank
Application
ServersLTO
NAS
Activearchivemigration fromLTO
Cost-effectivestorageinAWS withlocaldataaccess
AWSDirect
Connect
Selfserviceloading ofdata
Reduced time-to-data by daysorweeks
Storage archive costs reducedby90%
HalliburtonDataCenter
AWSLambda

78. Operate andOptimize
Now the funbegins
 Ensure application performance
 Look to proactively monitoryourapplication
end-to-end
 Trackmetrics,collectand monitor logfiles
 The goal is to resolve issues before they
impact yourcustomers
 Fine tune your application –Always
evolve
 It is an iterative process
 Think about scalability
https://aws.amazon.com/migration/partner-solutions/#application-profiling
AWSConfig AWSCloudWatch
AWS
CloudTrail

79. Internal only – do not distribute
AWS CompetencyProgram
Migration PartnerSolutions
The AWS Competency Program is designed to highlight APN Partners
who have demonstrated technical proficiency and proven customer
success in specialized solution areas. Attaining an AWS Competency
allows partners to differentiatethemselves to customers by showcasing
expertise in a specificsolutionarea.
Enterprises migrating to AWS require expertise, tools, and
alignment of business and ITstrategy.Many organizationscan
acceleratetheir migration, and their time to results, through
partnership.
TheAWS Partner CompetencyProgram has validatedthat the
following partners have demonstrated that they can help
enterprise customers migrate applications and legacy
infrastructuretoAWS.

80. Migration DeliveryPartners
Migration Delivery Partners help customers through every stageof migration,accelerating
results by providing personnel, tools, and education in the form of professional services.
These partners either are,or have a relationship with anAWS audited Managed Service
Provider to help customers with ongoing support ofAWS workloads.
https://aws.amazon.com/migration/partner-solutions/#migration-delivery

81. Migration ConsultingPartners
Migration Consulting partners provide expertiseand training to help enterprises quickly
develop specific capabilities and achieve specific outcomes for the move toAWS. They
provide consulting services to enable adoption of DevOps practices, to modernize
applications,and implementsolutions.
https://aws.amazon.com/migration/partner-solutions/#migration-consulting

82. Migration Technologyfor Discovery &Planning
Discover IT assets across your application portfolio, identify dependencies and
requirements, and build your comprehensive migration plan with this technology suite.
https://aws.amazon.com/migration/partner-solutions/#discovery-planning

83. Migration Technologyfor WorkloadMobility
Execute migrations to AWS by capturing your host server, configuration,
storage, and network states,then provision and configure yourAWS target
resources.
https://aws.amazon.com/migration/partner-solutions/#workload-mobility

84. Migration Technologyfor ApplicationProfiling
Gain valuable insights into your applications by capturing and analyzing
performancedata,usage, and monitoring dependencies before and after
migration.
https://aws.amazon.com/migration/partner-solutions/#application-profiling

85. What isMRP?
•ShortAnswer:
Migration Readiness &Planning
Accelerated& PrescriptiveJourney
to MigrationReadiness…
Includes eight distinct work streams

86. Migration Readiness &PlanningOutcomes
LandingZone
• Account structure
• Network design includingVPC,VPN,
DX, &multi-region
• Controlled Identity andAccess
Mgmt.
• Foundational capability tosecurely
operate atscale.
Skills/Center ofExcellence
• Structure across IT,Security andBusiness
• Identifying KeyRoles
• TechnicalTrainingProgram(s)
• Establishing WorkExperience
• Developing CloudExpertise
• 3rd party tooling, staffaugmentationor
outsourcing.
Discovery & Planning
• Dissecting theDatacenter
• DefiningApplication Patternsand
Grouping
• Application DesignProcess
• Initial backlog of applicationsready
to migrate
Migration BusinessCase
• Migration CostEstimate
• TCOModelling
• Business ValueAssessment
• Options toOptimize
Security &Compliance
• Security Directives: governance,risk,
and compliancemodels
• Preventive measures toprotect&
mitigatethreats
• Inspect & DetectInfractions
• Security Responsesplaybook
• Remediate tostandards
• Fullsecurity and compliancevisibility
& transparency
MigrationExperience
• Start Migrations Day1
• Establish theProcess
• Migrate a seriesofApplication
Patterns
• Functionality needs and enduser
experience matched with service
catalogue definitions
MigrationPlan
• CostEstimate
• Application Scoring
• TeamModel
• Project Plans
• Communication Plans
• Change ManagementPlans
Operating Model
• Implementation of Operational Run
Books for: Monitoring, Logging,
Provisioning, Asset Management,and
Configuration Management.
• BCR/DR
• WellOperated andContinuous
ImprovementProcesses.

87. Questions?

88. ThankYou