Amtrak's cloud adoption is riding the high-speed rail
summary
Cloud migration starts with a 2013 SAP nonprod pilot and grows into 150 applications moved off-premise, a data center sunset in 2019–2020, and mission‑critical financial and customer systems running in AWS. Architecture uses Route 53 with 50/50 active‑active routing, Elastic Beanstalk, global DynamoDB global tables, cross‑Region failover for a Positive Train Control covering 19,000 train miles, multi‑account governance, Service Catalog self‑service, Transit Gateway networking, IaC and DevSecOps with zero‑trust security and cost controls.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:50Agenda
- 2:54Amtraks cloud journey
- 6:55Cloud ecosystem
- 8:19Governance
- 10:55Use case
- 13:39Technical details
- 15:00Reference architecture
- 16:34Monitoring
- 18:30Observability
- 19:47Crossregion resiliency
- 20:55Disaster recovery scorecard
- 22:34Multiaccount structure
- 24:33Network services
- 26:13AWS Service Catalog
- 27:25Outro
related talks
01h 03mContinuous Security in the Cloud
40mBalancing agility and security: SBB’s journey to AWS(SEC204)
36maccelerates its modernization journey with
27mHBF’s AWS cloud transformation
19mPrescriptive approach to cloud: From on-premises to cloud in 9 months
37mShaping the Future of Travel with DevOps and Cloud
57mCreating value from confluence of technology forces (PRT250)
08mEnabling successful MRO operations with the AWS Cloud