AWS AmazonCloudFront documentation change
Summary
Removed all references and configuration guidance for S3 Multi-Region Access Points as CloudFront origins.
Security assessment
Removal of feature documentation without security justification. While related to origin security, no vulnerabilities or security issues are mentioned in the change.
Diff
diff --git a/AmazonCloudFront/latest/DeveloperGuide/DownloadDistS3AndCustomOrigins.md b/AmazonCloudFront/latest/DeveloperGuide/DownloadDistS3AndCustomOrigins.md index 05991b49c..13d7d8303 100644 --- a//AmazonCloudFront/latest/DeveloperGuide/DownloadDistS3AndCustomOrigins.md +++ b//AmazonCloudFront/latest/DeveloperGuide/DownloadDistS3AndCustomOrigins.md @@ -58,2 +57,0 @@ The following topics describe the different ways that you can use an Amazon S3 b - * Use an Amazon S3 Multi-Region Access Point - @@ -509,8 +506,0 @@ To force a faster update to CloudFront's records, you can update your CloudFront -### Use an Amazon S3 Multi-Region Access Point - -You can also use an Amazon S3 Multi-Region Access Point as a CloudFront origin. Amazon S3 Multi-Region Access Points provide a global endpoint that automatically routes requests to the closest Amazon S3 bucket based on network latency. When you use an Amazon S3 Multi-Region Access Point as an origin, specify the Multi-Region Access Point hostname as the origin domain name: - -``multi-region-access-point-alias`.accesspoint.s3-global.amazonaws.com` - -To restrict access to the S3 Multi-Region Access Point so that it's only accessible through your CloudFront distribution, see [Restrict access to an Amazon S3 Multi-Region Access Point origin](./private-content-restricting-access-to-s3-mrap.html). -