Home Arrow Icon Knowledge base Arrow Icon Global Arrow Icon Can I monitor IPv6 traffic separately using AWS Global Accelerator


Can I monitor IPv6 traffic separately using AWS Global Accelerator


Yes, you can monitor IPv6 traffic separately using AWS Global Accelerator. AWS Global Accelerator supports dual-stack accelerators that provide both IPv4 and IPv6 static anycast IP addresses, allowing you to route and serve both IPv4 and IPv6 traffic to your application endpoints, including Application Load Balancers (ALB), Network Load Balancers (NLB), and EC2 instances configured for dual-stack operation[1][2][3][5][8].

For monitoring, AWS Global Accelerator integrates with Amazon CloudWatch metrics that now include a global IP dimension distinguishing IPv4 and IPv6 traffic. This means you can view metrics such as request volume (e.g., NewFlowCount) separately for IPv4 and IPv6 addresses. The CloudWatch metrics for IPv6 traffic are available alongside those for IPv4, enabling you to track and analyze IPv6 traffic independently without additional charges or separate setups[1][2][5].

Additionally, AWS Global Accelerator supports flow logs, which capture detailed information about IP traffic going to and from your accelerator’s network interfaces. These flow logs include data for both IPv4 and IPv6 traffic and can be published to Amazon S3 or CloudWatch Logs for further analysis and troubleshooting[7].

In summary:

- AWS Global Accelerator supports dual-stack accelerators with IPv6 and IPv4 static IPs.
- You can route IPv6 traffic through Global Accelerator to dual-stack ALB, NLB, and EC2 endpoints.
- Amazon CloudWatch metrics for Global Accelerator include separate IPv6 traffic metrics, allowing distinct monitoring of IPv6 flows.
- Flow logs capture detailed IPv6 traffic data for deeper inspection and security monitoring.
- There are no additional costs for using dual-stack accelerators or monitoring IPv6 traffic.

This setup enables comprehensive and separate monitoring of IPv6 traffic through AWS Global Accelerator alongside IPv4 traffic, facilitating performance tracking, troubleshooting, and compliance with IPv6 requirements[1][2][3][5][7].

Citations:
[1] https://aws.amazon.com/blogs/networking-and-content-delivery/introducing-aws-global-accelerator-ipv6/
[2] https://aws.amazon.com/about-aws/whats-new/2023/11/aws-global-accelerator-ipv6-dual-stack-nlb-endpoints/
[3] https://aws.amazon.com/blogs/networking-and-content-delivery/global-accelerator-ipv6-nlb/
[4] https://docs.aws.amazon.com/global-accelerator/latest/dg/cloudwatch-monitoring.html
[5] https://aws.amazon.com/about-aws/whats-new/2023/08/aws-global-accelerator-extends-ipv6-support-ec2-endpoints/
[6] https://aws.amazon.com/blogs/aws/new-for-aws-global-accelerator-internet-protocol-version-6-ipv6-support/
[7] https://docs.aws.amazon.com/global-accelerator/latest/dg/monitoring-global-accelerator.flow-logs.html
[8] https://aws.amazon.com/blogs/networking-and-content-delivery/global-accelerator-ipv6-ec2/
[9] https://repost.aws/questions/QUUu02BPd-Rye6rRIRUcNpLA/ipv6-availability