Skip to content

Questions for Global Accelerator (ACC) and Route53 Health Checks (HC) and Application Recovery Controller (ARC)

0

Hi re:Post!

  1. Does ACC assume there is a standby environment already created and ready to point to when the primary region goes down?

  2. Does HC ARC assume there is a 2nd hosted zone with matching DNS records ready to go?

  3. What are the main differences between a HC Application Recovery Controller (ARC) and a DR Global Accelerator?

  4. How is the Global Accelerator tied into a hosted zone and dnz records ?

We've been reading these helpful documents:

https://docs.aws.amazon.com/prescriptive-guidance/latest/strategy-database-disaster-recovery/defining.html

https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/dns-failover.html

https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/health-checks-types.html

Thank you for your time and help!

Best Regards,

Donald

asked a year ago271 views
1 Answer
2
Accepted Answer
  1. Global Accelerator does not assume there is a standby environment already created. It works with the endpoints you configure, which can be in multiple regions. Global Accelerator continuously monitors the health of all endpoints and directs traffic to healthy endpoints. You have the flexibility to set up your architecture as active-active or active-standby, but Global Accelerator itself doesn't create or manage standby environments.

  2. Route 53 Application Recovery Controller (ARC) does not assume there is a second hosted zone with matching DNS records. ARC works with routing controls that are integrated with Route 53 health checks. These routing controls act as on-off switches to redirect traffic between regional replicas. You would typically set up DNS failover records associated with domain names that front your application replicas in each region, but ARC itself doesn't create or require a separate hosted zone.

  3. The main differences between Route 53 Application Recovery Controller (ARC) and Global Accelerator for disaster recovery are:

    • ARC is designed for complex, multi-region applications and provides more granular control over failover processes.
    • ARC uses routing controls integrated with Route 53 health checks to manage traffic routing.
    • ARC provides readiness checks and insights into recovery readiness.
    • Global Accelerator uses anycast IP addresses and the AWS global network to route traffic to the optimal endpoint.
    • Global Accelerator provides automatic failover based on endpoint health and supports traffic distribution using weights and traffic dials.
  4. Global Accelerator is not directly tied into a hosted zone or DNS records. It provides static IP addresses that serve as entry points for your application. You would typically create a DNS record in your hosted zone that points to these Global Accelerator IP addresses. Global Accelerator then handles routing to your endpoints based on health, location, and other factors, without further interaction with DNS.

Both solutions can be effective for disaster recovery, but they operate at different levels and offer different capabilities. The choice between them would depend on your specific application architecture and requirements.
Sources
Routing Control - Route 53 Application Recovery Controller - AWS
How AWS Global Accelerator works - AWS Global Accelerator
Routing control in ARC - Amazon Application Recovery Controller (ARC)

answered a year ago
EXPERT
reviewed a year ago
  • Thank you for your reply, the links, and help!

    Regarding 1), so in order for the Global Accelerator to work there needs to be an available standby environment, correct?

    Also for 2), there needs to be an existing second hosted zone with matching DNS records in order for ARC to have some where to fail over to, correct?

    Best Regards, Donald

    1. A standby environment is optional.
    2. Uses same Zone
  • Thank you Gary for your help and input regarding my questions!

    For "1. A standby environment is optional." - so then what would one fail-over to if there's no standby environment? Don't the endpoints have to exist in order for the accelerator to fail-over to them?

    Best Regards, Donald

  • AWS Global Accelerator is a networking service that improves the availability and performance of applications with a global user base. It leverages AWS's global network infrastructure to provide static IP addresses that act as fixed entry points to your application endpoints in one or more AWS Regions.

    Key benefits for disaster recovery include:

    Improved availability: Global Accelerator continuously monitors the health of your application endpoints and routes traffic to the nearest healthy endpoints.

    Fast regional failover: It can detect an unhealthy endpoint within sub-second intervals and redirect traffic to healthy endpoints in other regions, typically within 30 seconds.

    Increased fault tolerance: By using anycast IP addresses, Global Accelerator can reroute traffic to healthy endpoints even if entire AWS Regions become unreachable.

    Example: Consider a multi-region e-commerce platform. If the primary region in US-East-1 experiences an outage, Global Accelerator can quickly redirect traffic to healthy endpoints in US-West-2 or EU-Central-1, maintaining service continuity and minimizing downtime.

    The service integrates with AWS Shield for DDoS protection and works seamlessly with other AWS services like Elastic Load Balancing and EC2, providing a comprehensive solution for global traffic management and disaster recovery.

    Source: "https://docs.aws.amazon.com/global-accelerator/latest/dg/introduction-benefits-of-migrating.html"

  • Thank you Dave and Gary for your explanations and help! Best Regards, Donald

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.