> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/release8.3/data-access/dam-supported-connectors/amazon-s3.md).

# Amazon S3

## Introduction

The Data Access Management (DAM) feature provides a structured, catalog-like view of users, roles, and policies permissions across different metadata objects in Amazon S3. This helps administrators and source system owners maintain visibility and control over access at every level.

This section describes how Data Access Management works for Amazon S3. It outlines how to sync and view buckets, folders, and files, review assigned permissions for different users, roles, policies, and capture audit logs of all crawled entries.

For more details, refer to the [Data Access Management - DDA](/release8.3/data-access/data-access-management.md).

{% hint style="info" %}
DAM functionality may vary depending on the capabilities of the source system.
{% endhint %}

### Amazon S3 Metadata **Cataloging**

| Source Object   | Attribute                |
| --------------- | ------------------------ |
| Roles           | S3\_Roles                |
| Roles           | Description              |
| Roles           | Policies                 |
| Roles           | Application Created Date |
| Roles           | Application Role         |
| Roles           | Audit                    |
| Users           | User ID                  |
| Users           | Roles                    |
| Users           | Application Created Date |
| Users           | Application User         |
| Users           | Audit                    |
| Policies        | Policy                   |
| Policies        | Policy Type              |
| Policies        | Policy JSON              |
| Policies        | Source                   |
| Policies        | Roles/Users              |
| Policies        | Remote Created Date      |
| Policies        | Audit                    |
| Buckets/Folders | Buckets/Folders          |
| Buckets/Folders | Type                     |
| Buckets/Folders | Roles/Users              |
| Buckets/Folders | Permissions              |
| Buckets/Folders | Audit                    |

### Amazon S3 Permissions

| Amazon S3 Cataloging | Availability |
| -------------------- | :----------: |
| Bucket-Level         |       ✅      |
| Folder-Level         |       ✅      |
| File-Level           |       ✅      |

***

Copyright © 2025, OvalEdge LLC, Peachtree Corners GA USA


---

# 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.ovaledge.com/release8.3/data-access/dam-supported-connectors/amazon-s3.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.