What are some of the most frequently asked questions about determinism

AWS Global Accelerator FAQs

Q: What is AWS Global Accelerator?

A: AWS Global Accelerator is a network service that improves the availability and performance of the applications you offer to global customers. AWS Global Accelerator is easy to set up, configure, and manage. It provides a fixed entry point for the applications via static IP addresses and eliminates the complexity of managing specific IP addresses for different AWS Regions and Availability Zones. AWS Global Accelerator always routes user traffic to the optimal endpoint based on performance and reacts instantly to changes in application state, the user's location, and the policies you have configured. You can test the performance benefits of your location with a speed comparison tool. Like all other AWS services, AWS Global Accelerator is a standalone offering that only pays for what is actually used - with no long-term commitments or minimum fees.

Q: What can I do with AWS Global Accelerator?

A: With AWS Global Accelerator, you can:

  • the static IP addresses provided by AWS Global Accelerator with regional AWS resources or endpoints, such as B. Network Load Balancers, Application Load Balancers, EC2 Instances and elastic IP addresses. The IP addresses are anycast from AWS Edge locations, so they provide onboarding to the global AWS network near users.
  • Easily move endpoints between Availability Zones or AWS Regions without having to update DNS configuration or change client-facing applications.
  • Increase or decrease the traffic for a specific AWS Region by configuring a traffic percentage for your endpoint groups. This is particularly useful when testing performance and when releasing updates.
  • Control the amount of traffic directed to each endpoint within an endpoint group by assigning weights to the endpoints.
Q: What performance improvements does AWS Global Accelerator offer?
A: AWS Global Accelerator leverages Amazon's global network, which allows you to improve the performance of your applications by reducing the first byte latency (the round trip time of a packet from a client to your endpoint and back) and jitter (the Latency variation) and increase throughput (the time it takes to transfer data) compared to the public Internet. For TCP traffic as measured by third-party measurement tools for real users at the 90th percentile (p90), Global Accelerator reduces the first byte latency by up to 49% and the jitter by up to 58% and improves the Throughput by up to 60%. Lever, a recruiting platform, found that ... "Just by enabling AWS Global Accelerator, a multinational customer saw a 51.2 percent reduction in average end-to-end app load times". By building a multi-regional architecture with a Global Accelerator as the front end, Skyscanner was able to "... reduce the response time from more than 200 milliseconds to less than 4 milliseconds, which corresponds to an improvement of 98 percent".

Q: Where is AWS Global Accelerator currently deployed?

A: AWS Global Accelerator uses a global network of 96 points of presence in 84 cities in 46 countries. The AWS Global Accelerator edge locations are in:

  • North America: Ashburn, VA (2); Atlanta, GA; Boston, MA; Chicago, IL; Columbus, OH; Dallas / Fort Worth, TX; Denver, CO; Hillsboro, OR; Houston, TX; Los Angeles, CA (2); Miami, FL; Minneapolis, MN; Montreal, QC; New York, NY; Newark, NJ; Philadelphia, PA; Phoenix, AZ; Queretaro, Mexico (2); Salt Lake City, UT; San Jose, CA; Seattle, WA (2); Toronto, ON; Vancouver, BC
  • Europe: Amsterdam, Netherlands; Athens, Greece; Berlin, Germany; Brussels Belgium; Bucharest, Romania; Budapest, Hungary; Copenhagen, Denmark; Dublin, Ireland; Dusseldorf, Germany; Frankfurt, Germany (2); Hamburg, Germany; Helsinki, Finland; Lisbon, Portugal; London, England (2); Madrid, Spain; Manchester, England; Marseille, France; Milan, Italy; Munich, Germany; Oslo, Norway; Palermo, Italy; Paris, France; Prague, Czech Republic; Rome, Italy; Sofia, Bulgaria; Stockholm, Sweden; Vienna, Austria; Warsaw, Poland; Zagreb, Croatia; Zurich, Switzerland
  • Asia: Bangalore, India; Bangkok, Thailand; Chennai, India; Hong Kong, China (2); Hyderabad, India; Jakarta, Indonesia; Calcutta, India; Kuala Lumpur, Malaysia; Manila, Philippines; Mumbai, India; New Delhi, India; Osaka, Japan; Seoul, South Korea (2); Singapore (2); Taipei, Taiwan (2); Tokyo, Japan
  • Australia and New Zealand: Auckland, New Zealand; Melbourne, Australia; Perth, Australia; Sydney, Australia
  • South America: Bogota, Colombia; Buenos Aires, Argentina; Rio de Janeiro, Brazil; Santiago, Chile; São Paulo, Brazil (2)
  • Middle East: Dubai, United Arab Emirates; Fujairah, United Arab Emirates; Manama, Bahrain; Tel Aviv, Israel
  • Africa: Cape Town, South Africa; Johannesburg, South Africa; Nairobi, Kenya

Q: How do I get started with AWS Global Accelerator?

A: You can start setting up AWS Global Accelerator by using the API, or through the AWS Management Console or an AWS CloudFormation template. Because the AWS Global Accelerator is a global service, it is not tied to a specific AWS Region. Here are three easy steps to set up AWS Global Accelerator for the application:

  1. Create an accelerator: When you create the accelerator, AWS Global Accelerator provides two static IP addresses for it. You then configure one or more listeners to handle incoming connections from end customers to your accelerator based on the protocol and port you specified.
  2. Configure the endpoint groups: You choose one or more regional endpoint groups to associate with your accelerator's listener by specifying the AWS Regions across which you want to distribute traffic. The listener directs requests to the registered endpoints in this endpoint group. AWS Global Accelerator monitors the health of endpoints within the group based on the health check settings defined for each endpoint. You can configure the traffic percentage for each endpoint group, which controls the amount of traffic that an endpoint group accepts. By default, traffic is set to 100% for all regional endpoint groups.
  3. Register endpoints for endpoint groups: In each endpoint group, you register one or more regional resources, such as B. Application Load Balancers, Network Load Balancers, EC2 Instances, or elastic IP addresses. You then use weights to choose how much traffic is routed to each endpoint.

Q: How does AWS Global Accelerator work with Elastic Load Balancing (ELB)?

A: Both services solve the challenge of routing user requests to healthy application endpoints. AWS Global Accelerator relies on ELB to provide traditional load balancing functions such as: B. to provide support for internal and non-AWS endpoints, preheating and layer 7 routing. However, while ELB enables load balancing within a region, AWS Global Accelerator offers interregional traffic management.

A regional ELB load balancer is an ideal target for the AWS Global Accelerator. Using a regional ELB load balancer, you can precisely route the incoming application traffic within an AWS region to backends, such as Distribute e.g. Amazon EC2 instances or Amazon ECS tasks. The AWS Global Accelerator complements ELB by extending these capabilities beyond a single AWS Region so that you can provide a global interface for your applications in any number of regions. If you have workloads that target a global customer base, we recommend using the AWS Global Accelerator. If you have the workloads that are hosted in a single AWS Region and used by clients in and around the same region, you can use an Application Load Balancer or Network Load Balancer to manage the resources.

Q: How is AWS Global Accelerator different from Amazon CloudFront?

A: AWS Global Accelerator and Amazon CloudFront are separate services that use the AWS global network and its edge locations around the world. CloudFront optimizes the performance of both cacheable content (such as images and videos) and dynamic content (such as API acceleration and dynamic website serving). Global Accelerator improves performance for a wide variety of applications over TCP or UDP by forwarding packets at the edge to the applications running in one or more AWS Regions. Global Accelerator fits well for non-HTTP use cases such as gaming (UDP), IoT (MQTT) or Voice over IP, but also for HTTP use cases that specifically require static IP addresses or deterministic fast regional failover. Both services integrate with AWS Shield for DDoS protection.

Q: Can I use AWS Global Accelerator for my on-premise services?

A: You cannot configure on-premise resources directly as endpoints for the static IP addresses, but you can configure a Network Load Balancer (NLB) in each AWS Region to address the on-premise endpoints. Then you can register the NLBs as endpoints in the AWS Global Accelerator configuration.

Q: Can I deterministically forward multiple users to a specific endpoint IP and port behind my accelerator?

A: Yes. By using a custom routing accelerator, you can use your own application logic to route user traffic to a specific Amazon EC2 IP and port in one or more AWS Regions. An example of a use case is a multiplayer game where you want to assign multiple players to a single session on a game server based on factors such as geographic location, player skills, and game configuration. Other examples are VoIP, EdTech and social media applications where multiple users are assigned to a particular media server to initiate voice, video and messaging sessions.