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.

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. Scenario 1: Full Replication Failover. You take the on-premises Active Directory, and failover to another Region. Walkthrough. Log in to the CloudEndure Console 2.

Insiders

Sign Up for our Newsletter

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

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. Introduction. Considerations.

article thumbnail

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

AWS Disaster Recovery

Minimum business continuity for failover. Centralized cross-account management with Cross-Region copy using AWS Backup. Your application must be designed to handle any cascading failures to maintain a continuous user experience even when the backend systems are experiencing issues. Related information. Centralized Logging.