> ## Documentation Index
> Fetch the complete documentation index at: https://docs.e6data.com/llms.txt
> Use this file to discover all available pages before exploring further.

# 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 theme={"theme":{"light":"github-light","dark":"github-dark"}}
# Delete the role's inline policies first - delete-role fails while they're attached
for p in $(aws iam list-role-policies --role-name e6data-cross-account-role --query 'PolicyNames' --output text); do
  aws iam delete-role-policy --role-name e6data-cross-account-role --policy-name "$p"
done

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

## See also

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


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.