Rise with SAP on AWS: Swarovski's technical journey(BIZ202)
summary
Swarovski migrates its SAP estate to Rise with SAP on AWS using a lift‑and‑shift: 16 SAP landscapes in 18 months (effectively 12 months of migration time around business freeze periods). Architecture uses short‑distance HA with zero RPO across two AZs and Direct Connect for predictable throughput, and teams replatform Windows SAP workloads to Linux with a three‑month prep to fix file paths. Major cutover for a 9 TB ERP takes >48 hours downtime; post‑move the warehouses and latency‑sensitive processes run successfully.
AI-written summary · about
chapters (17)
- 0:00Introduction and speakers
- 1:07Modernizing SAP workloads
- 3:15What is Rise with SAP
- 4:40AWS global infrastructure for SAP
- 7:14Business transformation with SAP
- 9:02Innovation with AI and AWS SDK
- 11:08Stefan’s introduction and Swarovski background
- 13:27Swarovski’s cloud strategy
- 15:38Choosing Rise with SAP on AWS
- 18:13Migration approach and timeline
- 19:36Disaster recovery and high availability
- 23:10Challenges of Windows to Linux migration
- 25:40Key challenges in the migration
- 29:31Key learnings from the migration
- 32:40People and mindset transformation
- 33:42Future roadmap and next steps
- 34:43How to get started with Rise on AWS
related talks
46mReimagining Manufacturing: Clariant’s SAP RISE Journey with AWS
18mHow a retailer modernised their SAP landscape
12mModernize Manufacturing with SAP on
25mChoosing your SAP migration path
58mChoice and innovation for SAP customers
01h 01mRunning SAP on and with Microsoft Azure
37mDecide and begin an SAP migration journey to AWS
56mAccelerate your SAP S/4HANA transformation on