AWS athena documentation change
Summary
Grammar improvements and clarification about SSE-KMS requirements
Security assessment
Language clarifications without substantive changes to security content or encryption guidance.
Diff
diff --git a/athena/latest/ug/creating-tables-based-on-encrypted-datasets-in-s3.md index 7f5b7b2aa..d3bb77da7 100644 --- a/athena/latest/ug/creating-tables-based-on-encrypted-datasets-in-s3.md +++ b/athena/latest/ug/creating-tables-based-on-encrypted-datasets-in-s3.md @@ -7 +7 @@ -When you create a table, indicate to Athena that a dataset is encrypted in Amazon S3. This is not required when using SSE-KMS. For both SSE-S3 and AWS KMS encryption, Athena determines how to decrypt the dataset and create the table, so you don't need to provide key information. +When you create a table, indicate to Athena that a dataset is encrypted in Amazon S3. This isn't required when using SSE-KMS. For both SSE-S3 and AWS KMS encryption, Athena determines how to decrypt the dataset and create the table, so mustn't provide key information. @@ -15 +15 @@ If you use Amazon EMR along with EMRFS to upload encrypted Parquet files, you mu -To indicate that the dataset is encrypted in Amazon S3, perform one of the following steps. This step is not required if SSE-KMS is used. +To indicate that the dataset is encrypted in Amazon S3, perform one of the following steps. This step isn't required if SSE-KMS is used.