summaryrefslogtreecommitdiff
path: root/packages
diff options
context:
space:
mode:
authorRyan Harper <ryan.harper@canonical.com>2019-11-22 21:05:44 -0600
committerChad Smith <chad.smith@canonical.com>2019-11-22 20:05:44 -0700
commit4bc399e0cd0b7e9177f948aecd49f6b8323ff30b (patch)
treeceb03a0fcad1a205907554cb87707e12bbf4049d /packages
parent310f8605a5fe62dacf8edc63a809a061085bb907 (diff)
downloadvyos-cloud-init-4bc399e0cd0b7e9177f948aecd49f6b8323ff30b.tar.gz
vyos-cloud-init-4bc399e0cd0b7e9177f948aecd49f6b8323ff30b.zip
ec2: Add support for AWS IMDS v2 (session-oriented) (#55)
* ec2: Add support for AWS IMDS v2 (session-oriented) AWS now supports a new version of fetching Instance Metadata[1]. Update cloud-init's ec2 utility functions and update ec2 derived datasources accordingly. For DataSourceEc2 (versus ec2-look-alikes) cloud-init will issue the PUT request to obtain an API token for the maximum lifetime and then all subsequent interactions with the IMDS will include the token in the header. If the API token endpoint is unreachable on Ec2 platform, log a warning and fallback to using IMDS v1 and which does not use session tokens when communicating with the Instance metadata service. We handle read errors, typically seen if the IMDS is beyond one etwork hop (IMDSv2 responses have a ttl=1), by setting the api token to a disabled value and then using IMDSv1 paths. To support token-based headers, ec2_utils functions were updated to support custom headers_cb and exception_cb callback functions so Ec2 could store, or refresh API tokens in the event of token becoming stale. [1] https://docs.aws.amazon.com/AWSEC2/latest/ \ UserGuide/ec2-instance-metadata.html \ #instance-metadata-v2-how-it-works
Diffstat (limited to 'packages')
0 files changed, 0 insertions, 0 deletions