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:

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

See also