mirror of
https://github.com/HackTricks-wiki/hacktricks-cloud.git
synced 2026-03-12 21:22:57 -07:00
Fix typo in S3 encryption method
This PR fixes a typo in the "Amazon Athena" section regarding supported S3 encryption methods. The text currently states: > "SSE-C and CSE-E are not supported." "CSE-E" is not a valid AWS encryption acronym. The document previously defines **Client-side encryption with customer provided keys** as **CSE-C**. Since Athena does not support client-side encryption where the key is managed entirely by the customer (without KMS), **CSE-C** is the correct term to pair with SSE-C as unsupported methods.
This commit is contained in:
@@ -286,7 +286,7 @@ Amazon Athena supports the **ability to query S3 data that is already encrypted*
|
||||
|
||||
**This encryption of results is independent of the underlying queried S3 data**, meaning that even if the S3 data is not encrypted, the queried results can be encrypted. A couple of points to be aware of is that Amazon Athena only supports data that has been **encrypted** with the **following S3 encryption methods**, **SSE-S3, SSE-KMS, and CSE-KMS**.
|
||||
|
||||
SSE-C and CSE-E are not supported. In addition to this, it's important to understand that Amazon Athena will only run queries against **encrypted objects that are in the same region as the query itself**. If you need to query S3 data that's been encrypted using KMS, then specific permissions are required by the Athena user to enable them to perform the query.
|
||||
SSE-C and CSE-C are not supported. In addition to this, it's important to understand that Amazon Athena will only run queries against **encrypted objects that are in the same region as the query itself**. If you need to query S3 data that's been encrypted using KMS, then specific permissions are required by the Athena user to enable them to perform the query.
|
||||
|
||||
### Enumeration
|
||||
|
||||
|
||||
Reference in New Issue
Block a user