> For the complete documentation index, see [llms.txt](https://docs.prismacloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prismacloud.io/content-collections/data-security-posture-management/how-to-articles/monitor-and-identify-aws-activities.md).

# Monitor and Identify AWS Activities

This article describes how to do the following:

* Monitor and track access to your AWS data assets in real-time.
* Identify actors who are reading, writing, or modifying your AWS data assets, along with timestamps for their last actions.
* Visualize actions performed by different actors up to 90 days in the past.

### Monitor and identify AWS activities

1. Navigate to the storage bucket whose active identities you wish to view.
   1. In Prisma Cloud DSPM, click Inventory.
   2. In Inventory, click the name of the specific storage bucket you want to view.

      ![](https://3990409212-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyqPwsbMSaogAot23rTIu%2Fuploads%2Fgit-blob-7a79d7ad050ea4004e7103d1e8dc489e6f16175e%2Fmedia_1d43d58a6c24421e8298858e42f3e6c38f47f0d4d.png?alt=media\&token=bc01a65d-5edc-424d-80f8-3e760564ea91)
   3. Click the Active Identities tab.

      ![](https://3990409212-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyqPwsbMSaogAot23rTIu%2Fuploads%2Fgit-blob-43023ea24334c6300d569a68aa678090f2b32907%2Fmedia_16c0166bf7fb7c32390287f734203786cc77ad339.png?alt=media\&token=f1e0b068-7c59-466d-8339-551ee381b059)
2. View how and when each actor interacted with the data assets. For example, identify when a specific actor last wrote an event.

   ![](https://3990409212-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyqPwsbMSaogAot23rTIu%2Fuploads%2Fgit-blob-e43559b452a5665e23649cabca4dddeed0ce2fde%2Fmedia_11c1754b8fb917bb1e6bbfeeccb445a6510d4ddff.png?alt=media\&token=b6c7dfae-04b5-420a-912e-50d808c62683)
3. Use the filters to narrow the search. For example, use the filters to search for all actors who wrote an event before a specific date.

   ![](https://3990409212-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyqPwsbMSaogAot23rTIu%2Fuploads%2Fgit-blob-cb74c0386517c2d779ae38497e815ef2ec901ca6%2Fmedia_1e8732e346d0723f3a5c25b734e31f34826d62948.png?alt=media\&token=36f11f09-1457-4310-8d21-710730a81391)


---

# 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://docs.prismacloud.io/content-collections/data-security-posture-management/how-to-articles/monitor-and-identify-aws-activities.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.
