# HG changeset patch # User Franz Glasner # Date 1708354198 -3600 # Node ID a90273abc8a4d34bf43e68e554063e4ca9dff849 # Parent 0180b7deebf109f9765d796cf177e377ec366135 Make any notes regarding IMDSv2 and IPv4/IPv6 diff -r 0180b7deebf1 -r a90273abc8a4 configmix/extras/aws.py --- a/configmix/extras/aws.py Thu Dec 07 08:44:05 2023 +0100 +++ b/configmix/extras/aws.py Mon Feb 19 15:49:58 2024 +0100 @@ -8,6 +8,7 @@ .. see:: - https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-metadata.html - https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instancedata-data-retrieval.html - https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-identity-documents.html + . IMDSv2: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-metadata-v2-how-it-works.html """ @@ -26,6 +27,12 @@ _MARKER = object() +# +# These are for IMDSv1 (Instance Metadata Service) +# +# There is a new session-oriented IMDSv2 implementation using +# IPv4 (169.254.169.254) and IPv6 ([fd00:ec2::254]). +# URL_META_INSTANCEID = "http://169.254.169.254/latest/meta-data/instance-id" URL_META_REGION = "http://169.254.169.254/latest/meta-data/placement/region" URL_META_AVAILABILITY_ZONE = "http://169.254.169.254/latest/meta-data/availability-zone"