> 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/an-aws-ec2-instance-containing-sensitive-data-was-exported.md).

# An AWS EC2 instance containing sensitive data was exported

### Synopsis

| Field                | Value                                                       |
| -------------------- | ----------------------------------------------------------- |
| Activation Period    | 14 Days                                                     |
| Training Period      | 30 Days                                                     |
| Test Period          | N/A (single event)                                          |
| Deduplication Period | 3 Days                                                      |
| Required Data        | AWS Audit Log                                               |
| Detection Modules    | Cloud                                                       |
| Detector Tags        | Cloud Data Asset Stealth Tactics, Data Detection & Response |
| ATT\&CK Tactic       | Exfiltration (TA0010)                                       |
| ATT\&CK Technique    | Transfer Data to Cloud Account (T1537)                      |
| Severity             | Informational                                               |

### Description

A EC2 instance was exported to an S3 bucket. The instance was found to contain sensitive data.

### Attacker's Goals

An attack may exfiltrate data from an EC2 instance to an S3 bucket outside the account.

### Investigative actions

* Check the identity that exported the instance.
* Check to which S3 bucket the EC2 was exported into.
* Check the S3 bucket permission and policy.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/an-aws-ec2-instance-containing-sensitive-data-was-exported.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.