# AWS Global Accelerator

Cloud service · AWS. Updated 2026-11-12. Page: https://blowstack.com/tools/cloud-services-hub/aws-global-accelerator

> AWS Global Accelerator is a networking service that improves an application's availability and performance by directing traffic to optimal endpoints over the AWS global network.

Practice exams covering AWS Global Accelerator: [ANS-C01 AWS Certified Advanced Networking - Specialty](https://blowstack.com/practice-exams/aws-certified-advanced-networking-specialty), [CLF-C02 AWS Certified Cloud Practitioner](https://blowstack.com/practice-exams/aws-certified-cloud-practitioner), [SOA-C03 AWS Certified CloudOps Engineer - Associate](https://blowstack.com/practice-exams/aws-certified-cloudops-engineer-associate), [DOP-C02 AWS Certified DevOps Engineer - Professional](https://blowstack.com/practice-exams/aws-certified-devops-engineer-professional), [SAA-C03 AWS Certified Solutions Architect - Associate](https://blowstack.com/practice-exams/aws-certified-solutions-architect-associate), [SAP-C03 AWS Certified Solutions Architect - Professional](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional).

## 9 key features of AWS Global Accelerator

AWS Global Accelerator improves application performance by up to 60% through optimized paths, simplifies operational complexity by providing a single global entry point, enhances availability by routing to the nearest healthy end point, offers built-in DDoS protection, and aids in cost management by optimizing regional traffic serving.

1. **Improved Performance**: AWS Global Accelerator optimizes the path to your application to improve the performance of your internet applications by up to 60%. It directs traffic through Amazon Web Services' global network infrastructure, enhancing internet traffic routing.
2. **Simplified Operations**: By providing a global fixed entry point to your applications, AWS Global Accelerator simplifies how you manage global traffic, eliminating the need to manage IP addresses for different regions and reducing the operational complexity.
3. **Increased Availability**: AWS Global Accelerator improves the availability of your application by automatically routing traffic to the nearest healthy regional endpoint. This ensures a seamless experience for your users, even in the event of a regional failure.
4. **Built-in Protection**: It comes with built-in protection against Distributed Denial of Service (DDoS) attacks, ensuring that your applications remain available and perform well, even when they are targeted by malicious attempts to disrupt service.
5. **Cost Control**: AWS Global Accelerator allows you to optimize costs by controlling how traffic is served from different AWS regions, ensuring you can manage your expenses effectively without compromising on performance or availability.
6. **Bring Your Own IP Addresses**: For a standard IPv4 accelerator, you can use IPv4 addresses from your own address ranges through Bring Your Own IP (BYOIP) instead of Amazon-provided addresses.
7. **TCP Termination at the Edge**: Global Accelerator terminates client TCP connections at AWS edge locations and almost concurrently establishes new TCP connections to application endpoints, reducing latency and increasing throughput.
8. **Client IP Address Preservation**: Custom routing accelerators always preserve client IP addresses. Standard accelerators optionally preserve client IP addresses for supported endpoint types.
9. **Endpoint Weights and Regional Traffic Dials**: Standard accelerators support endpoint weights for fine-grained traffic control. Traffic dials increase or decrease the percentage of traffic sent to a specific endpoint group, supporting performance testing and stack upgrades.

## Where AWS Global Accelerator is used

AWS Global Accelerator use cases include improving global application performance, simplifying load balancing at scale, providing seamless IP address management, and enhancing application security and DDoS protection.

1. **Improve Global Application Performance**: AWS Global Accelerator improves the performance of your applications by routing user traffic through AWS's global network infrastructure. By deploying their application endpoints closer to users around the world, developers can reduce internet latency and improve data transfer speeds, offering a more seamless and responsive user experience.
2. **Simplify Load Balancing at Scale**: AWS Global Accelerator simplifies the management of load balancing across multiple regions. By automatically rerouting traffic to the nearest healthy endpoint, it enhances the availability and fault tolerance of your applications. This makes it easier for businesses to scale globally without the complexity of managing multiple load balancers or DNS configurations.
3. **Seamless IP Address Management**: By providing static IP addresses that act as a fixed entry point to your applications hosted in one or multiple AWS regions, AWS Global Accelerator simplifies IP address management. This allows organizations to avoid the complications associated with IP address changes in their applications, making it easier to whitelist IPs, manage firewall rules, and ensure consistent access for users and partners.
4. **Enhanced Security and DDoS Protection**: AWS Global Accelerator integrates with AWS Shield for DDoS protection.

## How AWS Global Accelerator is priced

AWS Global Accelerator pricing consists of a fixed monthly fee per accelerator plus additional charges based on the amount of data transferred.

- **Traffic-based Pricing**: AWS Global Accelerator charges a Data Transfer-Premium (DT-Premium) fee per gigabyte in the dominant traffic direction, determined each hour. The rate depends on the source AWS Region and destination AWS edge location. DT-Premium applies to all traffic through the accelerator and is additional to normal EC2 Data Transfer Out fees for application endpoints.
- **Fixed Hourly Fee**: Each accelerator costs $0.025 per full or partial hour until it is deleted, including when it is disabled.
- **Public IPv4 Address Charges**: Standard public IPv4 address charges apply to IPv4 addresses used with accelerators.

## Services AWS Global Accelerator works with

- **[Elastic Load Balancing (ELB)](https://blowstack.com/tools/cloud-services-hub/elastic-load-balancing-(elb))**: AWS Global Accelerator integrates with Elastic Load Balancing to distribute incoming application traffic across multiple targets, such as Amazon EC2 instances, in multiple AWS regions.
- **[AWS CloudFormation](https://blowstack.com/tools/cloud-services-hub/aws-cloudformation)**: AWS Global Accelerator integrates with AWS CloudFormation, allowing you to use CloudFormation templates to deploy and manage Global Accelerator resources such as accelerators, listeners, and endpoint groups.
- **[Amazon Route 53](https://blowstack.com/tools/cloud-services-hub/amazon-route-53)**: AWS Global Accelerator integrates with Amazon Route 53 through alias records that you create pointing to the accelerator, rather than by automatically updating DNS records once an accelerator is deployed, ensuring traffic is routed to the optimal endpoints.
- **[Amazon Athena](https://blowstack.com/tools/cloud-services-hub/amazon-athena)**: Global Accelerator flow logs stored in Amazon S3 can be queried with Amazon Athena. SQL queries can identify traffic patterns, client locations, and the endpoints receiving connections.
- **[Amazon CloudWatch](https://blowstack.com/tools/cloud-services-hub/amazon-cloudwatch)**: Global Accelerator publishes traffic and endpoint-health metrics to Amazon CloudWatch. You can create dashboards and alarms to track unhealthy endpoints, connection counts, and traffic volumes.
- **[Amazon EC2](https://blowstack.com/tools/cloud-services-hub/amazon-ec2)**: Global Accelerator standard accelerators support EC2 instances and Elastic IP addresses as endpoints. Custom routing accelerators map incoming connections to specific EC2 instance private IP addresses and ports within registered subnets.
- **[Amazon Elastic Kubernetes Service (Amazon EKS)](https://blowstack.com/tools/cloud-services-hub/amazon-elastic-kubernetes-service-(amazon-eks))**: Global Accelerator custom routing can direct connections to Kubernetes NodePorts on EC2 worker nodes in an EKS cluster. This lets applications assign clients to particular workloads, such as multiplayer game sessions, through fixed accelerator IP addresses.
- **[Amazon EventBridge](https://blowstack.com/tools/cloud-services-hub/amazon-eventbridge)**: Global Accelerator API activity recorded by CloudTrail can match Amazon EventBridge rules. For example, a rule can initiate a notification or remediation workflow when an accelerator is deleted or its configuration changes.
- **[Amazon QuickSight](https://blowstack.com/tools/cloud-services-hub/amazon-quicksight)**: Global Accelerator flow logs can be visualized in Amazon QuickSight using Athena queries over the logs in Amazon S3. Dashboards can show traffic distribution by client location, accelerator, or destination endpoint.
- **[Amazon S3](https://blowstack.com/tools/cloud-services-hub/amazon-s3)**: Global Accelerator delivers flow logs to an Amazon S3 bucket that you configure. These logs record connection information for traffic passing through an accelerator and can support troubleshooting and traffic analysis.
- **[Amazon VPC](https://blowstack.com/tools/cloud-services-hub/amazon-vpc)**: Global Accelerator routes traffic to supported endpoints within VPCs and creates network interfaces to deliver traffic to endpoints that preserve client IP addresses. Custom routing accelerators use VPC subnets as endpoints and map incoming traffic to specific private IP addresses and ports.
- **[Amazon WorkSpaces](https://blowstack.com/tools/cloud-services-hub/amazon-workspaces)**: Global Accelerator supports accelerated streaming connections for eligible WorkSpaces Personal desktops using the DCV protocol. It brings desktop streaming traffic onto the AWS global network near the user to improve connection performance.
- **[Amazon WorkSpaces Applications](https://blowstack.com/tools/cloud-services-hub/amazon-appstream-2)**: Global Accelerator carries UDP streaming traffic for WorkSpaces Applications sessions using the DCV protocol. This helps reduce latency for interactive applications, including graphics-intensive workloads.
- **[AWS CloudTrail](https://blowstack.com/tools/cloud-services-hub/aws-cloudtrail)**: Global Accelerator integrates with AWS CloudTrail to record API activity, including accelerator creation, endpoint changes, and deletions. These records identify who made a request, when it occurred, and the request parameters.
- **[AWS Config](https://blowstack.com/tools/cloud-services-hub/aws-config)**: AWS Config can record supported Global Accelerator resources, including accelerators, listeners, and endpoint groups. Configuration history lets you review changes to routing settings and endpoint membership.
- **[AWS Identity and Access Management (IAM)](https://blowstack.com/tools/cloud-services-hub/aws-identity-and-access-management-(iam))**: Global Accelerator uses IAM policies to control access to accelerators and related API operations, including tag-based access controls. It also uses service-linked roles to perform required actions such as managing network interfaces for VPC endpoints.
- **[AWS Shield](https://blowstack.com/tools/cloud-services-hub/aws-shield)**: Global Accelerator receives automatic DDoS protection from AWS Shield Standard. You can also register standard accelerators with Shield Advanced for enhanced detection, mitigation, and access to DDoS response assistance.
- **[AWS Site-to-Site VPN](https://blowstack.com/tools/cloud-services-hub/aws-site-to-site-vpn)**: Accelerated Site-to-Site VPN connections use Global Accelerator to bring VPN traffic onto the AWS global network at an edge location near the customer gateway. This option is available for supported VPN connections attached to a transit gateway.
- **[AWS Step Functions](https://blowstack.com/tools/cloud-services-hub/aws-step-functions)**: Step Functions can manage Global Accelerator through its AWS SDK service integrations. A workflow can update endpoint weights or regional traffic dials as part of an orchestrated deployment or failover procedure.

## AWS Global Accelerator exam questions

Real practice exam questions on AWS Global Accelerator, with the correct answer and its explanation.

### Question 1 (CLF-C02)

**Question:**

A financial services company provides a TCP-based transaction application to customers worldwide. Customers require fixed public IP addresses for their firewall allowlists, even when the company replaces its application endpoints. The company also wants customer connections to enter the AWS network at nearby edge locations instead of traveling over the public internet all the way to the application's Region. Which solution meets both requirements?

**Correct answer:** Use AWS Global Accelerator with the application's regional endpoints.

**Explanation:** AWS Global Accelerator provides static public IP addresses that remain unchanged when application endpoints change. It accepts traffic at edge locations and carries it over the AWS global network to regional endpoints.

### Question 2 (SOA-C03)

**Question:**

A company uses an AWS Global Accelerator standard accelerator to distribute TCP traffic on port 443 to two AWS Regions. Each Region has one endpoint group with a traffic dial of 100%. Client affinity is set to NONE.

In one Region, a CloudOps engineer adds a second Application Load Balancer (ALB) endpoint for a canary deployment. The original ALB serves the stable deployment. Both endpoints are healthy and have sufficient capacity.

The engineer must send approximately 10% of new connections assigned to this Region to the canary ALB and 90% to the stable ALB, measured over a large number of connections. The change must not reduce the traffic assigned to this Region or change the other Region's configuration.

Which configuration meets these requirements?

**Correct answer:** Keep the endpoint group's traffic dial at 100%. Set the stable ALB's endpoint weight to 90 and the canary ALB's endpoint weight to 10.

**Explanation:** Endpoint weights control the relative distribution of traffic among healthy endpoints within an endpoint group. Weights of 90 and 10 provide the required approximate split. Keeping the traffic dial at 100% avoids reducing the traffic directed to this Region.

### Question 3 (SAP-C03)

**Question:**

An industrial equipment company receives UDP telemetry through internet-facing Network Load Balancers (NLBs) in two AWS Regions. Each Region has sufficient capacity and independently replicated configuration data to process all telemetry. Devices can send to either of two destination IPv4 addresses that customers permanently allowlist. The devices cannot refresh DNS records during an outage and retry interrupted transmissions by creating new flows.

Both Regions should receive traffic during normal operation. If either Region becomes unable to process telemetry, new flows must automatically reach the healthy Region without changing the allowlisted addresses. A regional application can stop processing telemetry when its local configuration service fails even though its UDP listener and a separate TCP liveness port remain available. Each application instance exposes an HTTP /ready endpoint that returns success only when telemetry processing and the local configuration service are operational. Currently, the NLB target groups use the TCP liveness port for health checks.

Which solution meets these requirements?

**Correct answer:** Create a standard IPv4 AWS Global Accelerator with a UDP listener and an endpoint group containing the NLB in each Region. Enable traffic to both endpoint groups and give the devices the accelerator's two static IPv4 addresses. Change the NLB target group health checks to use HTTP /ready.

**Explanation:** A standard accelerator provides two static anycast IPv4 addresses and supports UDP listeners with NLB endpoints in multiple Regions. It routes new flows to healthy endpoints without requiring client DNS refreshes or address changes. For NLB endpoints, Global Accelerator uses the load balancer's health information. Configuring the NLB target groups to check /ready makes regional endpoint health reflect whether the application can actually process telemetry.

### Question 4 (SAA-C03)

**Question:**

A company operates a telemetry ingestion service on Amazon EC2 instances behind an internal Network Load Balancer (NLB) in one AWS Region. Devices worldwide connect over the public internet by using a proprietary TCP protocol, not HTTP or HTTPS. Network testing shows that long public-internet paths cause inconsistent connection performance.

The company wants device traffic to enter the AWS network near each device and use the AWS backbone to reach the service. Security policy prohibits internet-facing load balancers and public IP addresses on the EC2 instances. An internet gateway is attached to the VPC, but the application subnets have no routes to it.

Which solution meets these requirements?

**Correct answer:** Create an AWS Global Accelerator standard accelerator with a TCP listener. Add the internal NLB as an endpoint in an endpoint group for the application's Region, and direct devices to the accelerator.

**Explanation:** A standard accelerator supports TCP listeners and internal NLB endpoints. Device traffic enters the AWS global network at a nearby edge location and travels over the AWS backbone to the regional endpoint. The NLB can remain internal, and the instances do not need public IP addresses. The VPC must have an internet gateway attached, but the application subnets do not need routes to it for this connectivity.

### Question 5 (DOP-C02)

**Question:**

A company operates a latency-sensitive UDP application in three AWS Regions. Each Region has an independently scalable deployment behind a Network Load Balancer (NLB), and all three Regions must serve production traffic concurrently. Clients must use a fixed pair of public IPv4 addresses that corporate customers allowlist. Regional deployments must be replaceable without changing these addresses.

During planned maintenance, a DevOps engineer must stop sending new flows to a selected Region even while its NLB remains healthy. New flows must instead reach healthy deployments in other Regions. Outside maintenance windows, routing must favor optimal Regional endpoints over the AWS global network. Existing flows do not need to migrate between Regions, and each remaining Region has sufficient capacity.

Which solution meets these requirements?

**Correct answer:** Create a standard AWS Global Accelerator with a UDP listener and one endpoint group per Region. Register each Regional NLB in its endpoint group and normally set all traffic dials to 100%. For maintenance, set the selected Region's endpoint group traffic dial to 0%.

**Explanation:** A standard accelerator provides two static anycast IPv4 addresses and routes UDP traffic over the AWS global network to optimal healthy Regional endpoints. An endpoint group's traffic dial controls the traffic directed to that Region. Setting it to 0% stops new flows from being directed there and redirects them to other eligible endpoint groups without requiring an unhealthy NLB or a client address change.

### Question 6 (ANS-C01)

**Question:**

A company exposes an HTTPS application through an AWS Global Accelerator standard accelerator with internal Application Load Balancer (ALB) endpoints in two AWS Regions. Customers connect from known corporate public IPv4 CIDR ranges and have allowlisted the accelerator's static IPv4 addresses as destinations. The application must retain each client's original IP address in the ALB-generated X-Forwarded-For header.

Both endpoint VPCs have an internet gateway attached. The ALBs and application targets use private subnets that have no default route to an internet gateway or NAT gateway. Network ACLs permit the required traffic. Each ALB security group allows inbound TCP port 443 only from the accelerator's two static IPv4 addresses. Target security groups allow the application port from the corresponding ALB security group.

Global Accelerator reports both ALB endpoints as healthy, but customer HTTPS connections time out. The ALBs must remain internal, and the company must not add internet default routes to the private subnets.

Which change will restore customer connectivity while meeting these requirements?

**Correct answer:** Replace the ALB security groups' inbound source rules with the corporate public IPv4 CIDR ranges. Keep the existing target security group rules and subnet routes.

**Explanation:** Global Accelerator preserves client IP addresses for ALB endpoints, so the ALB security groups must permit the customers' source IP addresses, not the accelerator's destination addresses. The ALB then connects to its targets using its own security group identity, so the existing target rules are appropriate. An attached internet gateway is required for this configuration, but the private subnets do not need internet gateway routes.

## Practice AWS Global Accelerator in a full exam

Questions on AWS Global Accelerator in each practice exam, with every answer option and an explanation for each:

- [ANS-C01](https://blowstack.com/practice-exams/aws-certified-advanced-networking-specialty): 14 questions
- [SAA-C03](https://blowstack.com/practice-exams/aws-certified-solutions-architect-associate): 9 questions
- [CLF-C02](https://blowstack.com/practice-exams/aws-certified-cloud-practitioner): 4 questions
- [SOA-C03](https://blowstack.com/practice-exams/aws-certified-cloudops-engineer-associate): 3 questions
- [SAP-C03](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional): 2 questions
- [DOP-C02](https://blowstack.com/practice-exams/aws-certified-devops-engineer-professional): 1 question

## What is AWS Global Accelerator

AWS Global Accelerator is a networking service offered by Amazon Web Services (AWS) designed to improve the availability and performance of the applications that you offer to your global users. This service leverages the Amazon global network, allowing users to route their traffic through AWS's vast, highly available, and congestion-free backbone. By doing so, it helps in minimizing the path length between your users and your applications endpoint, regardless of where your users might be located globally. This results in a noticeable improvement in the user experience through reduced latency and packet loss.

The way AWS Global Accelerator works is fairly straightforward but profoundly impactful. When a user tries to access your application, Global Accelerator routes the user's request to the nearest edge location and then travels through AWS's network directly to the nearest application endpoint whether the application is deployed in one or more AWS Regions. This is significantly more efficient than routing over the public internet, where traffic is subject to various conditions that can lead to unpredictable performance and higher latency.

Another key aspect of AWS Global Accelerator is its support for static IP addresses that are globally unique and fixed, unlike the dynamic IP addresses typically assigned which can change and cause disruptions or require DNS updates. By providing static IP addresses, AWS makes it easier to manage applications without the need to update DNS settings frequently, adding an extra layer of reliability for applications that require a stable endpoint.

Global Accelerator supports IPv4 and dual-stack accelerators. IPv4 accelerators receive two static IPv4 addresses; dual-stack accelerators receive four static addresses: two IPv4 and two IPv6.

Static IP addresses remain assigned while the accelerator exists, even when it is disabled. Deleting the accelerator releases its assigned static IP addresses, so they can no longer be used to route traffic.

Global Accelerator also offers health checks and automatic failover. It continuously monitors the health of your application endpoints and can automatically reroute the traffic to healthy endpoints in case of failures. This feature ensures that your application remains available even if some of its endpoints become unhealthy, thus providing a robust solution to maintain high availability.

Custom routing accelerators instead map each accelerator port to a specific EC2 instance private IP address and port and do not provide external health checks. Your application monitors instance health and controls failover by directing traffic to a different accelerator IP address and port combination.

Security is another area where AWS Global Accelerator shines. It integrates with AWS Shield Standard, providing automatic protection against common network and transport layer DDoS attacks. This integrated protection helps in safeguarding applications from malicious attacks that could potentially disrupt service availability.

In essence, AWS Global Accelerator is a powerful tool for businesses looking to offer a seamless, high-performance experience to their customers around the globe. By leveraging AWSâs extensive and reliable infrastructure, it not only improves application performance but also enhances availability and security, making it an essential component of a global application delivery strategy.

## Learn AWS Global Accelerator in lessons

11 short lessons on AWS Global Accelerator in 5 certification courses.

- CLF-C02: AWS Global Accelerator: global traffic acceleration (Premium), https://app.blowstack.com/lessons/aws-global-accelerator-global-traffic-acceleration-clf-c02
- SOA-C03: Amazon CloudFront vs AWS Global Accelerator (Premium), https://app.blowstack.com/lessons/amazon-cloudfront-vs-aws-global-accelerator-soa-c03
- SAP-C03: AWS Global Accelerator vs Amazon Route 53: global routing and failover (Premium), https://app.blowstack.com/lessons/aws-global-accelerator-vs-amazon-route-53-global-routing-and-failover-sap-c03
- SAA-C03: AWS Global Accelerator: routing traffic over the AWS global network (Premium), https://app.blowstack.com/lessons/aws-global-accelerator-routing-traffic-over-the-aws-global-network-saa-c03
- DOP-C02: Amazon Route 53 vs AWS Global Accelerator: global traffic steering (Premium), https://app.blowstack.com/lessons/amazon-route-53-vs-aws-global-accelerator-global-traffic-steering-dop-c02
- CLF-C02: Amazon CloudFront and AWS Global Accelerator: choosing global delivery (Premium), https://app.blowstack.com/lessons/amazon-cloudfront-and-aws-global-accelerator-choosing-global-delivery-clf-c02

## Concepts related to AWS Global Accelerator

- [AWS global infrastructure](https://blowstack.com/tools/cloud-concepts-hub/aws-global-infrastructure): AWS global infrastructure is the worldwide arrangement of Regions, Availability Zones, and edge locations that provides the physical foundation for deploying and delivering cloud workloads.
- [Anycast](https://blowstack.com/tools/cloud-concepts-hub/anycast): Anycast is a network addressing and routing technique in which multiple locations advertise the same IP address and routing selects one location to receive a client's traffic.
- [Active-Active Architecture](https://blowstack.com/tools/cloud-concepts-hub/active-active-architecture): Active-active architecture runs multiple production environments simultaneously, distributing live traffic across them so healthy environments can continue serving users when another fails.
- [DDoS Mitigation](https://blowstack.com/tools/cloud-concepts-hub/ddos-mitigation): DDoS mitigation combines traffic filtering, distributed capacity, and resilient architecture to keep services available during distributed denial-of-service attacks.
- [Latency-Based Routing](https://blowstack.com/tools/cloud-concepts-hub/latency-based-routing): Latency-based routing directs clients to an eligible endpoint expected to provide the lowest network delay.
