You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The AWS metadata checks will only work on v1 endpoints, which are becoming harder to find. You will need to request a token with a PUT request, and then use that token in subsequent metadata requests.
Excuse the formatting, far too lazy today to deal with escaping backticks.
The AWS metadata checks will only work on v1 endpoints, which are becoming harder to find. You will need to request a token with a PUT request, and then use that token in subsequent metadata requests.
Excuse the formatting, far too lazy today to deal with escaping backticks.
Example:
get a valid token for use / refresh the token
TOKEN=
curl -X PUT http://169.254.169.254/latest/api/token -H "X-aws-ec2-metadata-token-ttl-seconds: 21600"
&& curl -H "X-aws-ec2-metadata-token: $TOKEN" -v http://169.254.169.254/latest/meta-data/get the key materials
curl -H "X-aws-ec2-metadata-token: $TOKEN" -v http://169.254.169.254/latest/meta-data/iam/security-credentials/
The text was updated successfully, but these errors were encountered: