> 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/analytics-alerts/alerts-by-name/remote-usage-of-ec2-token.md).
# Remote usage of EC2 token
### Synopsis
| Field | Value |
| -------------------- | ----------------------------------------------------------------------------------------------------------------- |
| Activation Period | 14 Days |
| Training Period | 30 Days |
| Test Period | N/A (single event) |
| Deduplication Period | 1 Day |
| Required Data | AWS Audit Log |
| Detection Modules | Cloud |
| ATT\&CK Tactic | Credential Access (TA0006), Initial Access (TA0001) |
| ATT\&CK Technique | Steal Application Access Token (T1528), Unsecured Credentials (T1552), Valid Accounts: Cloud Accounts (T1078.004) |
| Severity | Low |
### Description
An AWS STS token associated with an EC2 instance was used externally, potentially indicating credential exfiltration.
### Attacker's Goals
Exfiltrate temporary credentials from the EC2 instance and use them remotely to access AWS resources.
### Investigative actions
* Identify the EC2 instance attached to the role and verify whether the API activity originated from that instance.
* Review the full session activity of the access key to determine the scope and intent of the operations performed.
* Check if the source IP and ASN are associated with known infrastructure such as VPNs, CI/CD pipelines, or third-party services.
* Investigate whether the EC2 instance shows signs of compromise.
### Variations
Suspicious usage of EC2 token
**Synopsis**
| Field | Value |
| ----------------- | ----------------------------------------------------------------------------------------------------------------- |
| ATT\&CK Tactic | Credential Access (TA0006), Initial Access (TA0001) |
| ATT\&CK Technique | Steal Application Access Token (T1528), Unsecured Credentials (T1552), Valid Accounts: Cloud Accounts (T1078.004) |
| Severity | Medium |
**Description**
An AWS STS token associated with an EC2 instance was used externally, potentially indicating credential exfiltration.
**Attacker's Goals**
Exfiltrate temporary credentials from the EC2 instance and use them remotely to access AWS resources.
**Investigative actions**
* Identify the EC2 instance attached to the role and verify whether the API activity originated from that instance.
* Review the full session activity of the access key to determine the scope and intent of the operations performed.
* Check if the source IP and ASN are associated with known infrastructure such as VPNs, CI/CD pipelines, or third-party services.
* Investigate whether the EC2 instance shows signs of compromise.
---
# 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/analytics-alerts/alerts-by-name/remote-usage-of-ec2-token.md?ask=&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.