Commit e22c1cd
committed
fix: allow IPv6 EKS Pod Identity host regardless of IMDS endpoint mode
ContainerCredentialsProvider rejects the EKS Pod Identity IPv6 endpoint
(http://[fd00:ec2::23]/v1/credentials) unless AWS_EC2_METADATA_SERVICE_ENDPOINT_MODE
was explicitly set to IPV6. That variable configures the EC2 IMDS endpoint
(169.254.169.254 vs [fd00:ec2::254]) which is (I believe?) a separate subsystem from the container
credentials endpoint and EKS Pod Identity never sets it, so it defaults to the IPv4 allowlist. This behavior rejects valid IPv6 loopback hosts.
This change aligns the Java SDK with the C++, Python (botocore), Go v2, and JS v3 SDKs,
all of which allow the EKS IPv6 host unconditionally.
Related issue: aws/containers-roadmap#2683.1 parent 8a6a76c commit e22c1cd
2 files changed
Lines changed: 15 additions & 5 deletions
File tree
- core/auth/src
- main/java/software/amazon/awssdk/auth/credentials
- test/java/software/amazon/awssdk/auth/credentials
Lines changed: 1 addition & 5 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
307 | 307 | | |
308 | 308 | | |
309 | 309 | | |
310 | | - | |
311 | | - | |
312 | | - | |
313 | | - | |
314 | | - | |
| 310 | + | |
315 | 311 | | |
316 | 312 | | |
317 | 313 | | |
| |||
Lines changed: 14 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
164 | 164 | | |
165 | 165 | | |
166 | 166 | | |
| 167 | + | |
| 168 | + | |
| 169 | + | |
| 170 | + | |
| 171 | + | |
| 172 | + | |
| 173 | + | |
| 174 | + | |
| 175 | + | |
| 176 | + | |
| 177 | + | |
| 178 | + | |
| 179 | + | |
| 180 | + | |
167 | 181 | | |
168 | 182 | | |
169 | 183 | | |
| |||
0 commit comments