> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/appsec-rules/iac-security/compute/appsec-aws-79.md).

# AWS EC2 instance not configured with Instance Metadata Service v2 (IMDSv2) misconfiguration detected

## Rule Details

|                        |                                                       |
| ---------------------- | ----------------------------------------------------- |
| Cortex AppSec Rule ID  | APPSEC\_AWS\_79                                       |
| Category - Subcategory | Compute - Unsanctioned Resource Or Type               |
| Provider               | AWS                                                   |
| Severity               | HIGH                                                  |
| Framework              | CloudFormation, Serverless, Terraform, Terraform Plan |
| Mapped CSPM/KSPM Rule  | 81c165ce-f66e-441a-8ea0-56a107175ccc                  |

## Impact

The Instance Metadata Service (IMDS) is an on-instance component used by code on the instance to securely access instance metadata.

You can access instance metadata from a running instance using one of the following methods:

* Instance Metadata Service Version 1 (IMDSv1) -- a request/response method
* Instance Metadata Service Version 2 (IMDSv2) -- a session-oriented method

As a request/response method IMDSv1 is prone to local misconfigurations:

* Open proxies, open NATs and routers, server-side reflection vulnerabilities.
* One way or another, local software might access local-only data.

## How to Fix

*Resource:* AWS::EC2::LaunchTemplate

* *Arguments:* Properties.MetadataOptions.HttpEndpoint / Properties.MetadataOptions.HttpTokens \[source,go]

***

Resources: IMDSv1Disabled: Type: AWS::EC2::LaunchTemplate Properties: ... LaunchTemplateData: ...

* MetadataOptions:
* HttpEndpoint: disabled

IMDSv2Enabled: Type: AWS::EC2::LaunchTemplate Properties: ... LaunchTemplateData: ...

* MetadataOptions:
* HttpTokens: required

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/appsec-rules/iac-security/compute/appsec-aws-79.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.