AWS Disaster Recovery
JUNE 23, 2021
The architecture in Figure 2 shows you how to use AWS Regions as your active sites, creating a multi-Region active/active architecture. Each Region hosts a highly available, multi- Availability Zone (AZ) workload stack. I use Amazon DynamoDB for the example architecture in Figure 2. DR strategies.
AWS Disaster Recovery
JANUARY 20, 2021
Route 53 Private Hosted Zones (PHZs) and Resolver endpoints on AWS create an architecture best practice for centralized DNS in hybrid cloud environment. This blog presents an architecture that provides a unified view of the DNS while allowing different AWS accounts to manage subdomains. Architecture Overview.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
AWS Disaster Recovery
APRIL 26, 2021
By using the best practices provided in the AWS Well-Architected Reliability Pillar whitepaper to design your DR strategy, your workloads can remain available despite disaster events such as natural disasters, technical failures, or human actions. Every AWS Region consists of multiple Availability Zones (AZs).
AWS Disaster Recovery
APRIL 27, 2021
In this blog, we talk about architecture patterns to improve system resiliency, why observability matters, and how to build a holistic observability solution. Due to its monolithic architecture, the application didn’t scale quickly with sudden increases in traffic because of its high bootstrap time. Predictive scaling for EC2.
AWS Disaster Recovery
JANUARY 25, 2022
The Availability and Beyond whitepaper discusses the concept of static stability for improving resilience. The AWS Identity and Access Management (IAM) data plane is highly available in each Region, so you can authorize the creation of new resources as long as you’ve already defined the roles.
Expert insights. Personalized for you.
63 
Let's personalize your content