AWS AmazonCloudWatch documentation change
Summary
Minor editorial changes: replaced 'a bucket' with 'an S3 bucket' for grammatical accuracy and expanded prefix explanation with organizational examples.
Security assessment
No security vulnerabilities or weaknesses are addressed. Changes are purely editorial/clarification-focused without introducing new security features or addressing security incidents. The added examples demonstrate organizational use cases, not security controls.
Diff
diff --git a/AmazonCloudWatch/latest/logs/S3Export.md b/AmazonCloudWatch/latest/logs/S3Export.md index e6228d29f..828e390ee 100644 --- a//AmazonCloudWatch/latest/logs/S3Export.md +++ b//AmazonCloudWatch/latest/logs/S3Export.md @@ -9 +9 @@ Concepts -This chapter provides you with information, so you can export log data from your log groups to an Amazon S3 bucket for custom processing and analysis, or to load onto other systems. You can export to a bucket in the same account or a different account. +This chapter provides you with information, so you can export log data from your log groups to an Amazon S3 bucket for custom processing and analysis, or to load onto other systems. You can export to an S3 bucket in the same account or a different account. @@ -26 +26 @@ You can export to S3 buckets that are encrypted with AES-256 or with SSE-KMS. Ex -You can export logs from multiple log groups or multiple time ranges to the same S3 bucket. To separate log data for each export task, you can specify a prefix that will be used as the Amazon S3 key prefix for all exported objects. +You can export logs from multiple log groups or multiple time ranges to the same S3 bucket. To organize exported data, specify a prefix for each export task which will be used as the Amazon S3 key prefix for all exported objects. For example `prod/app-logs/2026-01-03/` or `log-group-name/backup/`