article thumbnail

Using Route 53 Private Hosted Zones for Cross-account Multi-region Architectures

AWS Disaster Recovery

This post was co-written by Anandprasanna Gaitonde, AWS Solutions Architect and John Bickle, Senior Technical Account Manager, AWS Enterprise Support. Many AWS customers have internal business applications spread over multiple AWS accounts and on-premises to support different business units. Architecture Overview.

article thumbnail

Journey to Adopt Cloud-Native Architecture Series: #3 – Improved Resilience and Standardized Observability

AWS Disaster Recovery

In this blog, we talk about architecture patterns to improve system resiliency, why observability matters, and how to build a holistic observability solution. Minimum business continuity for failover. Current Architecture with improved resiliency and standardized observability. Predictive scaling for EC2. Conclusion.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Field Notes: Protecting Domain-Joined Workloads with CloudEndure Disaster Recovery

AWS Disaster Recovery

When designing a Disaster Recovery plan, one of the main questions we are asked is how Microsoft Active Directory will be handled during a test or failover scenario. Overview of architecture. In the following architecture, we show how you can protect domain-joined workloads in the case of a disaster. Walkthrough. Walkthrough.

article thumbnail

Disaster Recovery Solutions with AWS-Managed Services, Part 3: Multi-Site Active/Passive

AWS Disaster Recovery

Warm standby with managed services Let’s cover each of the components of this application, as well as how managed services behave in a multisite environment. You would just need to create the records and specify failover for the routing policy. In case of failover, the data plane scales up to meet the workload requirements.