Code relying on AWS IMDSv1 blocking cloud env hardening 😓 #1314
Labels
type: feature request
‘Nice-to-have’ improvement, new feature or different behavior or design.
type: question
Request for information or clarification. Not an issue.
Is your feature request related to a problem? Please describe.
AWS IMDSv2 (metadata url - 169.254.169.254) seems to be supported in
google/auth/aws.py
but some files likegoogle/auth/compute_engine/_metadata.py
still rely on IMDSv1, blocking aws cloud hardening.V1 Legacy code:
google-auth-library-python/google/auth/compute_engine/_metadata.py
Lines 49 to 54 in 9c87ad0
google-auth-library-python/google/auth/compute_engine/_metadata.py
Lines 153 to 241 in 9c87ad0
V2 Supported code:
google-auth-library-python/google/auth/aws.py
Lines 418 to 470 in 9c87ad0
Describe the solution you'd like
A full support of IMDSv2 as default metadata fetching service, follwing: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-metadata-v2-how-it-works.html
The text was updated successfully, but these errors were encountered: