1、 2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.I N D 3 1 5 RDos and donts for mission-critical workloads in financial servicesSamuel BaruffiHe/HimPrincipal Solutions ArchitectGlobal Financial ServicesAmazon Web S
2、ervices(AWS)Vasu ChariHe/HimPrincipal Solutions ArchitectGlobal Financial ServicesAmazon Web Services(AWS)Shivani SharmaShe/HerSenior Solutions ArchitectGlobal Financial ServicesAmazon Web Services(AWS)2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.Werner VogelsCTO,A“Everything f
3、ails,all the time.”2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.Ability of a workload to recover from infrastructure or service disruptionsResilienceThe mental modelContinuous improvement CI/CD,observability,moving beyond pre-deployment testing towards chaos engineering pattern
4、sHigh availabilityResistance to common failures through design and operational mechanisms at a primary site Core services,design goals to meet availability goalsDisaster recoveryReturning to normal operation within specific targets at a recovery site for failures that cannot be handled by HABackup a
5、nd recovery,data bunkering,managed recovery objectives 2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.Recovery point objective and recovery time objective(RPO/RTO)How much data can you afford to recreate or lose?How quickly must you recover?What is the cost of downtime?DisasterRe
6、covery point(RPO)Recovery time(RTO)Data lossDowntime 2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.Backup&restoreData backed upNo services deployedCost:$Pilot lightData liveServices idleCost:$Warm standby Data liveServices run reduced capacityCost:$Active/activeData liveLive ser