Dive into technical decisions from successful migrations
summary
Walks through concrete choices: pick discovery tools that map server‑to‑server, DB versions, licenses and container dependencies or incur manual work; one retail migration lost many weeks after skipping full dependency mapping and a healthcare move undercounted licenses so teams switch to open-source databases and re‑architect to cut TCO. Recommends multi‑account patterns using AWS Control Tower and AWS Organizations, network with Direct Connect + DX Gateway + Transit Gateway, and treat CIDR planning and IAM as one-way door and two-way door decisions.
AI-written summary · about
chapters (24)
- 0:00Introduction
- 0:50Migration Journey
- 2:20Agenda
- 3:06Oneway and twoway door decisions
- 4:11Discovery process
- 5:13How to pick a discovery tool
- 7:27Customer examples
- 9:09The mobilized phase
- 10:31Landing zone
- 13:38Governance
- 14:41Multiple accounts
- 15:43Account categories
- 16:56Workload accounts
- 19:42Combining accounts
- 20:24Account structure
- 21:37Networking
- 23:52Architecture
- 24:44Security
- 26:43Operations
- 28:14Data Analytics
- 29:21Data Lake
- 29:53Consistency
- 30:54Summary
- 31:26Resources
related talks
29mJourney through the center of migrations
26mEffective Data Migration: Challenges & Success
25mMass migrations to the cloud
29mLessons from migration and modernisation journey
15mStrategic Framework for Successful Oracle Migrations to AWS
29mMigrate and Modernize to Achieve Your Business Outcomes
25mNavigating Cloud Migration: Strategies for Success
47mMigrando hacia AWS: Cómo garantizar el cumplimiento y la seguridad