# IMDSv2: session tokens added against request-forgery access to instance credentials: the technique as Amazon Web Services published it

Facts read 16 Nov 2026. Page reviewed 16 Nov 2026.

Amazon Web Services published "IMDSv2: session tokens added against request-forgery access to instance credentials" on 19 Nov 2019. AWS introduced version 2 of its EC2 Instance Metadata Service, which requires a session token obtained with an HTTP PUT request. AWS says the change adds protection against open firewalls, reverse proxies and server-side request forgery reaching instance credentials.

- **Published:** 19 Nov 2019
- **Publisher:** Amazon Web Services
- **Access path:** [Exposed network services and request paths](/access-paths/exposed-network-service/)
- **Source:** [the publisher's write-up](https://aws.amazon.com/blogs/security/defense-in-depth-open-firewalls-reverse-proxies-ssrf-vulnerabilities-ec2-instance-metadata-service/)

AWS introduced version 2 of its EC2 Instance Metadata Service, which requires a session token obtained with an HTTP PUT request. AWS says the change adds protection against open firewalls, reverse proxies and server-side request forgery reaching instance credentials.

## Related pages

- [Leaked IAM user keys used for storage theft and container ](/techniques/ecs-crypto-mining-leaked-keys/)
- [Malicious OAuth applications used to keep access after an ](/techniques/midnight-blizzard-oauth-apps/)
- [Lateral movement through cloud APIs and compute instances](/techniques/cloud-lateral-movement/)

## Sources

- IMDSv2: session tokens added against request-forgery access to instance credentials: https://aws.amazon.com/blogs/security/defense-in-depth-open-firewalls-reverse-proxies-ssrf-vulnerabilities-ec2-instance-metadata-service/ (read 16 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://cloudsecuritybreaches.com/techniques/imdsv2-ssrf/
