Home Arrow Icon Knowledge base Arrow Icon Global Arrow Icon Can custom routing accelerators be integrated with other AWS services


Can custom routing accelerators be integrated with other AWS services


Custom routing accelerators in AWS Global Accelerator can indeed be integrated with other AWS services, primarily through their interaction with Amazon EC2 instances within Amazon Virtual Private Cloud (VPC) subnets. Here is a detailed explanation:

Integration with Amazon EC2 and VPC

- Custom routing accelerators route traffic deterministically to specific Amazon EC2 instances and ports within VPC subnets. This means you can use your own application logic to direct users to particular EC2 instance destinations, which is useful for applications like multiplayer gaming, VoIP, or real-time media sessions where users must connect to specific servers[1][2][3][4].

- The endpoints for custom routing accelerators must be VPC subnets, and the traffic is routed only to private IP addresses of EC2 instances in those subnets. This integration ensures that traffic benefits from the AWS global network for improved performance and availability while maintaining security by not exposing EC2 instances directly to the internet[1][3][4][8].

Application Logic and API Integration

- Your application can use AWS Global Accelerator APIs, such as `ListCustomRoutingPortMappings`, to retrieve static mappings between the accelerator's IP addresses and ports and the private IP addresses and ports of EC2 instances. This allows your custom application logic (like matchmaking services in gaming or session controllers in communication apps) to dynamically route users to the correct destinations[2][4].

- This API-driven approach enables seamless integration with your backend services running on EC2, allowing you to implement complex routing logic based on user attributes such as geographic location, skill level, or session requirements[2][4].

Security and Traffic Control

- By default, VPC subnet endpoints are not allowed to receive traffic until explicitly permitted, giving you granular control over which EC2 instances can accept traffic through the accelerator. You can manage these permissions using Global Accelerator API calls like `AllowCustomRoutingTraffic` and `DenyCustomRoutingTraffic` to control access at the subnet or individual destination socket level[4].

Potential Integration with Other AWS Services

- While the primary integration is with EC2 instances in VPC subnets, custom routing accelerators can indirectly integrate with other AWS services that interact with EC2, such as AWS Lambda (triggered by EC2 events), Amazon CloudWatch (for monitoring), and AWS Identity and Access Management (IAM) for controlling permissions on accelerators[1][2][4].

- Additionally, you can bring your own IP addresses (BYOIP) to Global Accelerator, allowing further customization and integration with your existing network infrastructure[1].

In summary, custom routing accelerators are designed to integrate tightly with Amazon EC2 instances within VPC subnets, leveraging Global Accelerator's network to route traffic deterministically based on your application logic. They provide API hooks for dynamic routing decisions and granular traffic control, enabling integration with a variety of AWS services that support or complement EC2-based applications. This makes them suitable for complex, session-based applications requiring precise user-to-server mappings while benefiting from AWS's global network performance and security features[1][2][3][4].

Citations:
[1] https://docs.aws.amazon.com/global-accelerator/latest/dg/about-custom-routing-accelerators.html
[2] https://aws.amazon.com/blogs/networking-and-content-delivery/introducing-aws-global-accelerator-custom-routing-accelerators/
[3] https://docs.aws.amazon.com/global-accelerator/latest/dg/work-with-custom-routing-accelerators.html
[4] https://docs.aws.amazon.com/global-accelerator/latest/dg/about-custom-routing-how-it-works.html
[5] https://docs.aws.amazon.com/global-accelerator/latest/dg/getting-started-custom-routing.html
[6] https://docs.aws.amazon.com/global-accelerator/latest/dg/introduction-how-it-works.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/about-custom-routing-guidelines.html