> For the complete documentation index, see [llms.txt](https://docs.e6data.com/query-engine/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.e6data.com/query-engine/guides/deployment/aws-serverless/faqs.md).

# FAQs

Common questions about data access, permissions, and revocation for a Serverless e6data deployment on AWS.

**Why does e6data need access to my AWS account?** To securely read and analyze the data stored in your S3 buckets. e6data requires only read-only permissions and cannot modify your data.

**Can e6data modify or delete my data?** No. The cross-account role grants read-only access. e6data cannot create, update, or delete any object or bucket configuration.

**Can I limit access to specific buckets or prefixes?** Yes. Access can be scoped at the bucket, prefix, or object level using IAM policies. For advanced folder-level restrictions, contact e6data support.

**How do I revoke access?** Remove the IAM role or update its trust policy to remove e6data's principal.

* In the **AWS Console**: open the IAM role → **Trust relationships**, and remove the e6data principal, or delete the role entirely.
* With the **AWS CLI**:

```bash
aws iam delete-role --role-name e6data-cross-account-role
```

## See also

* [Configure AWS access](/query-engine/guides/deployment/aws-serverless/configure-aws-access.md) - how the cross-account role is set up.
* [Troubleshooting](/query-engine/guides/deployment/aws-serverless/troubleshooting.md) - resolving access and connection errors.


---

# 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.e6data.com/query-engine/guides/deployment/aws-serverless/faqs.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.