The cost implications of using custom routing accelerators in AWS Global Accelerator primarily involve two components: the fixed hourly fee for each accelerator and the data transfer charges.
1. Fixed Hourly Fee per Accelerator
Each custom routing accelerator you deploy incurs a fixed hourly charge. This fee covers the use of AWS-provided static IPv4 addresses assigned to the accelerator. The IP addresses remain allocated to the accelerator as long as it exists, even if the accelerator is disabled and not routing traffic. However, if you delete the accelerator, you lose those static IP addresses[1][9].
2. Data Transfer Costs
Beyond the hourly fee, you pay for the volume of data transferred through the accelerator. Data transfer pricing varies by geographic region and is based on the amount of data processed by the accelerator. This means the more traffic routed through your custom routing accelerator, the higher your data transfer costs will be[3][9].
3. Additional Considerations
- Custom routing accelerators route traffic only to EC2 instances within VPC subnets, and do not support other endpoint types like load balancers. This may influence architecture decisions that could impact overall costs, such as the number and size of EC2 instances required[1][7].
- You must allocate sufficient listener port ranges to cover all destination ports and instances, which could affect the complexity and management overhead but not directly the cost[7][10].
- Using your own IP address range (BYOIP) is supported, which might have cost implications related to IP address management but can provide more control over IP usage[1].
In summary, the main cost drivers for custom routing accelerators are the hourly accelerator fees and the data transfer volume charges. These costs are in addition to the underlying costs of running EC2 instances in your VPC subnets. The custom routing capability itself does not inherently add extra charges beyond the standard Global Accelerator pricing model, but the architecture it enables might influence your overall AWS resource usage and costs[3][9][10].
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://cloudchipr.com/blog/aws-global-accelerator
[4] https://repost.aws/questions/QUqyevPh1vSO2CEpqQIXrHTQ/cloudfront-vs-global-accelerator
[5] https://boto3.amazonaws.com/v1/documentation/api/1.36.2/reference/services/globalaccelerator.html
[6] https://www.youtube.com/watch?v=DuXx0UpUKSg
[7] https://docs.aws.amazon.com/global-accelerator/latest/dg/about-custom-routing-guidelines.html
[8] https://www.reddit.com/r/aws/comments/wr4d0r/cloudfront_global_accelerator/
[9] https://www.nops.io/glossary/what-is-aws-global-accelerator/
[10] https://docs.aws.amazon.com/global-accelerator/latest/dg/work-with-custom-routing-accelerators.html