AWS global-accelerator documentation change
Summary
Updated Amazon S3 documentation links from Getting Started Guide (gsg) to User Guide (userguide) paths
Security assessment
Changes only correct documentation URLs without altering security content. While flow logs relate to security monitoring, the link updates themselves don't address vulnerabilities or add new security features. The security implications remain unchanged from previous documentation.
Diff
diff --git a/global-accelerator/latest/dg/monitoring-global-accelerator.flow-logs.md b/global-accelerator/latest/dg/monitoring-global-accelerator.flow-logs.md index 475a14a66..001451ceb 100644 --- a//global-accelerator/latest/dg/monitoring-global-accelerator.flow-logs.md +++ b//global-accelerator/latest/dg/monitoring-global-accelerator.flow-logs.md @@ -70 +70 @@ Flow logs for AWS Global Accelerator are published to Amazon S3 to an existing S -To create an Amazon S3 bucket for use with flow logs, see [Create your first S3 bucket](https://docs.aws.amazon.com/AmazonS3/latest/gsg/CreatingABucket.html) in the _Amazon Simple Storage Service User Guide_. +To create an Amazon S3 bucket for use with flow logs, see [Create your first S3 bucket](https://docs.aws.amazon.com/AmazonS3/latest/userguide/CreatingABucket.html) in the _Amazon Simple Storage Service User Guide_. @@ -171 +171 @@ If the user creating the flow log owns the bucket, the service automatically att -If the user creating the flow log does not own the bucket, or does not have the `GetBucketPolicy` and `PutBucketPolicy` permissions for the bucket, the flow log creation fails. In this case, the bucket owner must manually add the preceding policy to the bucket and specify the flow log creator's AWS account ID. For more information, see [Adding a bucket policy by using the Amazon S3 console ](https://docs.aws.amazon.com/AmazonS3/latest/gsg/add-bucket-policy.html) in the _Amazon Simple Storage Service User Guide_. If the bucket receives flow logs from multiple accounts, add a `Resource` element entry to the `AWSLogDeliveryWrite` policy statement for each account. +If the user creating the flow log does not own the bucket, or does not have the `GetBucketPolicy` and `PutBucketPolicy` permissions for the bucket, the flow log creation fails. In this case, the bucket owner must manually add the preceding policy to the bucket and specify the flow log creator's AWS account ID. For more information, see [Adding a bucket policy by using the Amazon S3 console ](https://docs.aws.amazon.com/AmazonS3/latest/userguide/add-bucket-policy.html) in the _Amazon Simple Storage Service User Guide_. If the bucket receives flow logs from multiple accounts, add a `Resource` element entry to the `AWSLogDeliveryWrite` policy statement for each account. @@ -223 +223 @@ If you enabled server-side encryption for your Amazon S3 bucket using AWS KMS-ma -In addition to the required bucket policies, Amazon S3 uses access control lists (ACLs) to manage access to the log files created by a flow log. By default, the bucket owner has `FULL_CONTROL` permissions on each log file. The log delivery owner, if different from the bucket owner, has no permissions. The log delivery account has `READ` and `WRITE` permissions. For more information, see [Access control list (ACL) overview](https://docs.aws.amazon.com/AmazonS3/latest/gsg/acl-overview.html) in the _Amazon Simple Storage Service User Guide_. +In addition to the required bucket policies, Amazon S3 uses access control lists (ACLs) to manage access to the log files created by a flow log. By default, the bucket owner has `FULL_CONTROL` permissions on each log file. The log delivery owner, if different from the bucket owner, has no permissions. The log delivery account has `READ` and `WRITE` permissions. For more information, see [Access control list (ACL) overview](https://docs.aws.amazon.com/AmazonS3/latest/userguide/acl-overview.html) in the _Amazon Simple Storage Service User Guide_.