Access to Amazon S3 - Amazon Athena

Access to Amazon S3

You can grant access to Amazon S3 locations using identity-based policies, bucket resource policies, access point policies, or any combination of the above.

Whenever you use IAM policies, make sure that you follow IAM best practices. For more information, see Security best practices in IAM in the IAM User Guide.

Note

Athena does not support restricting or allowing access to Amazon S3 resources based on the aws:SourceIp, aws:SourceVpc, or aws:SourceVpce condition keys.

Amazon S3 access points and access point aliases

If you have a shared dataset in an Amazon S3 bucket, maintaining a single bucket policy that manages access for hundreds of use cases can be challenging.

Amazon S3 bucket access points help solve this issue. A bucket can have multiple access points, each with a policy that controls access to the bucket in a different way.

For each access point that you create, Amazon S3 generates an alias that represents the access point. Because the alias is in Amazon S3 bucket name format, you can use the alias in the LOCATION clause of your CREATE TABLE statements in Athena. Athena's access to the bucket is then controlled by the policy for the access point that the alias represents.

For more information, see Table location in Amazon S3 and Using access points in the Amazon S3 User Guide.

Using CalledVia context keys

For added security, you can use the aws:CalledVia global condition context key. The aws:CalledVia key contains an ordered list of each service in the chain that made requests on the principal's behalf. By specifying the Athena service principal name athena.amazonaws.com for the aws:CalledVia context key, you can limit requests to only those made from Athena. For more information, see Using Athena with CalledVia context keys.

Additional resources

For detailed information and examples about how to grant Amazon S3 access, see the following resources: