This Guidance demonstrates cross region resilient platforms with data consistency (both for data and catalogue) across regions.
Architecture Diagram
![](https://d1.awsstatic.com/apac/events/2021/aws-innovate-aiml/2022/eng/innovate-aiml-22-UI_Gradient-Divider.082bb46e8d9654e48f62bf018e131dd8ec563c4e.jpg)
Step 1
Use Amazon Simple Storage Service (Amazon S3) as storage for the data lake.
Step 2
AWS Glue Data Catalog stores data lake metadata.
Step 3
Deploy other configurations, such as Amazon Athena workgroup settings or AWS Glue catalog schemas by using infrastructure as code (IaC) pipelines.
Step 4
Use Multi-AZ configuration for AWS services that store data outside of Amazon S3.
Step 5
Use Amazon Route 53 or AWS Global Accelerator to provide an endpoint for data ingestion that can switch to another Region during failover.
Step 6
Use Amazon S3 cross-Region replication to replicate data to the backup Region.
Step 7
Keep AWS Glue Data Catalog in sync by using IaC pipelines and create new partitions using Amazon S3 events.
Step 8
Use IaC pipelines to keep configuration in sync.
Step 9
Use AWS service cross-Region replication to back up other analytics services.
Step 10
During failover, the workloads in the backup region are deployed.
Well-Architected Pillars
![](https://d1.awsstatic.com/apac/events/2021/aws-innovate-aiml/2022/eng/innovate-aiml-22-UI_Gradient-Divider.082bb46e8d9654e48f62bf018e131dd8ec563c4e.jpg)
The AWS Well-Architected Framework helps you understand the pros and cons of the decisions you make when building systems in the cloud. The six pillars of the Framework allow you to learn architectural best practices for designing and operating reliable, secure, efficient, cost-effective, and sustainable systems. Using the AWS Well-Architected Tool, available at no charge in the AWS Management Console, you can review your workloads against these best practices by answering a set of questions for each pillar.
The architecture diagram above is an example of a Solution created with Well-Architected best practices in mind. To be fully Well-Architected, you should follow as many Well-Architected best practices as possible.
-
Operational Excellence
This guidance supports operational excellence by making sure that businesses can continue to run important data lake workloads in the event of a regional problem. It emphasizes automated pipelines for deploying and maintaining the data lake, and uses a business-level monitoring technique to provide operators better visibility into the workloads.
-
Security
This guidance uses encryption for data at rest in both Regions. It emphasizes the need to roll out access control settings by using automated infrastructure as code (IaC) pipelines.
-
Reliability
This guidance covers how to safeguard Amazon S3 data, data lake metadata, and non-Amazon S3 storage using native AWS cross-region backup services and replication.
-
Performance Efficiency
This pillar is not a key focus of a disaster recovery (DR) strategy. However, the solution does provide for continued operation of the workloads in the event of a regional problem, and uses AWS Global Accelerator to provide more efficient ingestion of streaming data.
-
Cost Optimization
Using the backup and restore pattern reduces the need to run duplicate workloads in the backup Region, which saves the cost required to run those workloads.
-
Sustainability
Using the backup and restore pattern reduces the need to run duplicate workloads in the backup Region, which saves the resources required to run those workloads.
Related Content
![](https://d1.awsstatic.com/apac/events/2021/aws-innovate-aiml/2022/eng/innovate-aiml-22-UI_Gradient-Divider.082bb46e8d9654e48f62bf018e131dd8ec563c4e.jpg)
Disclaimer
The sample code; software libraries; command line tools; proofs of concept; templates; or other related technology (including any of the foregoing that are provided by our personnel) is provided to you as AWS Content under the AWS Customer Agreement, or the relevant written agreement between you and AWS (whichever applies). You should not use this AWS Content in your production accounts, or on production or other critical data. You are responsible for testing, securing, and optimizing the AWS Content, such as sample code, as appropriate for production grade use based on your specific quality control practices and standards. Deploying AWS Content may incur AWS charges for creating or using AWS chargeable resources, such as running Amazon EC2 instances or using Amazon S3 storage.
References to third-party services or organizations in this Guidance do not imply an endorsement, sponsorship, or affiliation between Amazon or AWS and the third party. Guidance from AWS is a technical starting point, and you can customize your integration with third-party services when you deploy the architecture.