To configure regional endpoint groups in AWS Global Accelerator, follow these detailed steps and concepts:
**1. Understand Endpoint Groups and Their Role
An endpoint group in AWS Global Accelerator is associated with a specific AWS Region and contains one or more endpoints within that region. Each endpoint group is linked to a listener, which processes inbound client connections based on specified protocols and ports. For standard accelerators, endpoint groups route traffic to resources such as Network Load Balancers (NLB), Application Load Balancers (ALB), EC2 instances, or Elastic IP addresses in a single AWS Region[1][2][10].
**2. Create or Select an Accelerator and Listener
First, create an accelerator (standard or custom routing) in the Global Accelerator console or via API. Then, create one or more listeners specifying the protocol (TCP, UDP, or both) and port or port range that the accelerator will use to receive client traffic[8][10].
**3. Add Endpoint Groups to Listeners
For each listener, add one or more endpoint groups by selecting the AWS Region where your endpoints reside. Each listener can have only one endpoint group per AWS Region[6][7].
- In the AWS Global Accelerator console, go to the Accelerators page and select your accelerator.
- Under the Listeners section, choose the listener ID to which you want to add an endpoint group.
- Click "Add endpoint group" and select the desired AWS Region from the dropdown[6].
**4. Configure Traffic Dial
You can set a traffic dial percentage (0 to 100) for each endpoint group. This dial controls the proportion of traffic that Global Accelerator sends to the endpoint group relative to the total traffic directed to that group. It allows fine-grained traffic control for scenarios like blue/green deployments or performance testing across regions. By default, the traffic dial is set to 100%[1][5][8].
**5. Configure Health Checks
For standard accelerators, you can configure custom health check settings for EC2 instances and Elastic IP endpoints within the endpoint group. These settings define how Global Accelerator monitors endpoint health and routes traffic only to healthy endpoints. For load balancer endpoints, health checks are configured on the Elastic Load Balancing console[1][6].
**6. Add Endpoints to Endpoint Groups
Add the specific endpoints (NLB, ALB, EC2 instances, or Elastic IPs) to the endpoint group. Each endpoint must be valid and active. You can also assign weights to endpoints to control the percentage of traffic routed to each endpoint within the group, which is useful for load balancing or testing purposes[2][9][10].
**7. Optional: Configure Port Overrides
If you need to reroute traffic to different ports on your endpoints than those specified on the listener, you can configure port overrides for the endpoint group. This is useful for avoiding port conflicts or connection collisions[6].
**8. Save and Monitor
After configuring endpoint groups and adding endpoints, save your settings. AWS Global Accelerator will monitor endpoint health continuously and route traffic based on client location, endpoint health, traffic dial settings, and endpoint weights[1][2][8].
Summary of Key Configuration Points
- Each endpoint group is tied to a single AWS Region and linked to a listener.
- You can add multiple endpoint groups for different regions to a listener.
- Traffic dial controls the traffic percentage sent to each endpoint group.
- Health checks ensure traffic is routed only to healthy endpoints.
- Endpoints can be NLB, ALB, EC2 instances, or Elastic IPs for standard accelerators.
- Endpoint weights allow traffic distribution within an endpoint group.
- Port overrides can be configured if needed.
This approach provides granular control over how traffic is routed globally, enabling performance optimization and deployment flexibility across multiple AWS Regions[1][6][8][10].
Citations:
[1] https://docs.aws.amazon.com/global-accelerator/latest/dg/about-endpoint-groups.html
[2] https://docs.aws.amazon.com/global-accelerator/latest/dg/about-endpoints.html
[3] https://docs.aws.amazon.com/global-accelerator/latest/dg/about-custom-routing-endpoint-groups.html
[4] https://docs.aws.amazon.com/global-accelerator/latest/dg/introduction-how-it-works.html
[5] https://tutorialsdojo.com/aws-global-accelerator/
[6] https://docs.aws.amazon.com/global-accelerator/latest/dg/about-endpoint-groups.create-endpoint-group.html
[7] https://boto3.amazonaws.com/v1/documentation/api/1.21.9/reference/services/globalaccelerator.html
[8] https://docs.aws.amazon.com/global-accelerator/latest/dg/introduction-get-started.html
[9] https://boto3.amazonaws.com/v1/documentation/api/1.16.27/reference/services/globalaccelerator.html
[10] https://cloudchipr.com/blog/aws-global-accelerator