[GH-ISSUE #1764] IPv6 endpoints for AWS IMDS #907

New issue

Open

opened 2026-03-04 01:49:49 +03:00 by kerem · 0 comments

kerem commented

2026-03-04 01:49:49 +03:00

Owner

Originally created by @nmeyerhans on GitHub (Sep 7, 2021).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1764

Additional Information

AWS has recently added an IPv6 endpoint for IMDS, in addition to the existing 169.254.169.254 IPv4 endpoint. On EC2 instances with IPv6 addresses assigned, the metadata service is available at fd00:ec2::254

More details in the announcement and the documentation

In order to support customers who choose to avoid assigning an IPv4 address to their instances (or potentially disable v4 support in their operating system entirely), s3fs should be able to retrieve EC2 instance role credentials from the v6 endpoint in addition to, or instead of, the v4 endpoint.

Originally created by @nmeyerhans on GitHub (Sep 7, 2021). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1764 ### Additional Information AWS has recently added an IPv6 endpoint for IMDS, in addition to the existing 169.254.169.254 IPv4 endpoint. On EC2 instances with IPv6 addresses assigned, the metadata service is available at fd00:ec2::254 More details in [the announcement](https://aws.amazon.com/about-aws/whats-new/2021/08/Ipv6-amazon-ec2-metadata-time-sync-vpc-dns/) and the [documentation](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/configuring-instance-metadata-service.html) In order to support customers who choose to avoid assigning an IPv4 address to their instances (or potentially disable v4 support in their operating system entirely), s3fs should be able to retrieve EC2 instance role credentials from the v6 endpoint in addition to, or instead of, the v4 endpoint.