AWS re:Invent 2023 - Best practices for creating multi-Region architectures on AWS (ARC308)

Architecting and building a multi-Region architectures can come with a new set of challenges. These challenges include how to manage dependencies, infrastructure deployments, data replication, consistency, observability, testing, and operations. Whether you’re needing to expand to multiple Regions to improve resilience, adhere to governmental data regulations, or improve end-user latency, this session highlights best practices, design principles, and sample architectures to help you meet your requirements.

Subscribe:

ABOUT AWS
Amazon Web Services (AWS) hosts events, both online and in-person, bringing the cloud computing community together to connect, collaborate, and learn from AWS experts.

AWS is the world's most comprehensive and broadly adopted cloud platform, offering over 200 fully featured services from data centers globally. Millions of customers—including the fastest-growing startups, largest enterprises, and leading government agencies—are using AWS to lower costs, become more agile, and innovate faster.

#AWSreInvent #AWSreInvent2023

[satish]

Good presentation

One thing was missed:

When workloads are migrated to the DR site, that location becomes the new primary, correct?

Since this is a warm standby strategy, we cannot operate at full capacity for an extended period, as fewer compute resources are allocated to the DR site. Our goal is to eventually return to the original primary location. To achieve this, we need to reverse the migration process back to the primary site.

In essence, for every disaster recovery scenario, there would be two instances of downtime: the first for migrating to the DR site, and the second for transitioning back to the original primary site.

Could you kindly confirm if my understanding is accurate?