A company provides a Voice over Internet Protocol (VoIP) service that uses UDP connections. The service consists of Amazon EC2 instances that run in an Auto Scaling group. The company has deployments across multiple AWS Regions.
The company needs to route users to the Region with the lowest latency. The company also needs automated failover between Regions.
Which solution will meet these requirements?
To route users to the Region with the lowest latency and ensure automated failover, you can use AWS Global Accelerator with a Network Load Balancer (NLB). Global Accelerator allows routing both HTTP and non-HTTP protocols, such as UDP, which is essential for VoIP. AWS Global Accelerator improves availability and resiliency by distributing traffic among multiple regions and providing automatic failover to optimal endpoints. Thus, deploying an NLB in each Region, associating it with the Auto Scaling group, and using it as an endpoint in AWS Global Accelerator best meets the requirements of low latency and automated failover.
agree with A, Global Accelerator has automatic failover and is perfect for this scenario with VoIP https://aws.amazon.com/global-accelerator/faqs/
Thank you for your link, it make me consolidate A.
This option does not meet the requirements because AWS Global Accelerator is only used to route traffic to the optimal AWS Region, it does not provide automatic failover between regions.
Instant regional failover: AWS Global Accelerator automatically checks the health of your applications and routes user traffic only to healthy application endpoints. If the health status changes or you make configuration updates, AWS Global Accelerator reacts instantaneously to route your users to the next available endpoint.
Thank you, the link also helps me to know the differences between Global Acc and CloudFront.
I also agree A after reading this link.
A - Global Accelerator is a good fit for non-HTTP use cases, such as gaming (UDP), IoT (MQTT), or Voice over IP, as well as for HTTP use cases that specifically require static IP addresses or deterministic, fast regional failover. Both services integrate with AWS Shield for DDoS protection.
This is the best case for A to be an answer. Cloudfront is great but for HTTP use cases.
CloudFront uses Edge Locations to cache content while Global Accelerator uses Edge Locations to find an optimal pathway to the nearest regional endpoint. CloudFront is designed to handle HTTP protocol meanwhile Global Accelerator is best used for both HTTP and non-HTTP protocols such as TCP and UDP. so i think A is a better answer
Option A suggests using an NLB and associating it with an Auto Scaling group, then using the NLB as an AWS Global Accelerator endpoint in each Region. While this can provide low-latency access, AWS Global Accelerator primarily focuses on improving the availability and fault tolerance of applications. It directs traffic over the AWS global network to optimize the path to the application, but it may not necessarily route traffic based on the lowest latency. In contrast, Option C involves using Amazon Route 53 for latency-based routing, which allows you to direct users to the Region with the lowest latency. This aligns more closely with the requirement of routing users to the Region with the lowest latency. Therefore, Option C is a better fit for the specified use case.
I agree with you, as a networking engineer, I would go with the R53 latency-based entries. I don't know why people are still choosing A, this is not an application based question, rather a networking based question. I work with VoIP within my DataCenters as well, everyone of my network architect colleagues agreed with Option C.
Option C used CloudFront which is caching and why do you need caching for a VoIP traffic? CF for Option C is the reason we should choose A. Option A is correct
Its UDP so ALB is not applicable here which means BD are wrong C using CF that uses latency record as origin? Makes no sense B NLB autoscaling and AWS GA is best used for lower latency and scaling. Recommended read: https://aws.amazon.com/blogs/networking-and-content-delivery/well-architecting-online-applications-with-cloudfront-and-aws-global-accelerator/
"The company needs to route users to the Region with the lowest latency. The company also needs automated failover between Regions." IMO both A and C would meet both requirements. The main difference is that with A, the IP address stays the same - in case of failover, it would be routed to a different entry point. With C, the different endpoint have different IP addresses, and in case of failover, DNS would return the IP address of a different entry point. Thus failover might take longer with C, but again, the stem does not mention that failover must be fast ...
Why ALB, not NLB?
It IS NLB. You cannot trust the "official" answers. I am not even sure why they bother giving them Application Load Balancer: -Web applications with layer 7 routing (HTTP/HTTPS) -Microservices architectures (e.g. Docker containers) -Lambda targets Network Load Balancer: -TCP and UDP based applications -Ultra low latency -Static IP addresses -VPC endpoint services
Agree with C. As i understand NLB cannot be used as AWS Global accelerator endpoint. It has to be ALB or ELB.
A is right answer, key words VoIP, UDP connection, automatic failover between region.
A is correct because Accelerator endpoint usefull more than route53
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-policy-latency.html
Answer-A
One of the major benefits of AWS Global Accelerator is Instant regional failover: AWS Global Accelerator automatically checks the health of your applications and routes user traffic only to healthy application endpoints. If the health status changes or you make configuration updates, AWS Global Accelerator reacts instantaneously to route your users to the next available endpoint. https://aws.amazon.com/global-accelerator/faqs/
A ia correct
Correct as Global accelerator is most preferred for TCP and UDP
UDP Connection :- So NLB Routing to region having lowest latency and also with Automated failover, Also non-HTTP use cases, such as gaming (UDP), or Voice over IP - Global Accelerator
you can configure a Network Load Balancer (NLB) in each AWS Region to address your on-premises endpoints. Then you can register the NLBs as endpoints in your AWS Global Accelerator configuration. https://aws.amazon.com/global-accelerator/faqs/
A : UDP so NLB and Global Accelerator reduces the number of hops by providing packets to travel over congestion free AWS global network. Global Accelerator supported end point : ALB,NLB,EC2 & Elastic IP address