AWS AmazonCloudFront documentation change
Summary
Removed Lambda function URL origin documentation section entirely
Security assessment
This appears to be a feature documentation removal without explicit security context. No evidence of security issues addressed in the change.
Diff
diff --git a/AmazonCloudFront/latest/DeveloperGuide/template-preconfigured-origin-settings.md b/AmazonCloudFront/latest/DeveloperGuide/template-preconfigured-origin-settings.md index 3d4e63cc4..3fb464492 100644 --- a//AmazonCloudFront/latest/DeveloperGuide/template-preconfigured-origin-settings.md +++ b//AmazonCloudFront/latest/DeveloperGuide/template-preconfigured-origin-settings.md @@ -5 +5 @@ -Amazon S3 originAPI Gateway originCustom origin and EC2 instanceElastic Load Balancing originLambda function URL originMediaPackage v1 originMediaPackage v2 originMediaTailor origin +Amazon S3 originAPI Gateway originCustom origin and EC2 instanceElastic Load Balancing originMediaPackage v1 originMediaPackage v2 originMediaTailor origin @@ -325,83 +324,0 @@ Following are the settings that you can customize for your Elastic Load Balancin -## Lambda function URL origin - -Following are the origin settings that CloudFront preconfigures for your Lambda function URL origin in a multi-tenant distribution. - -###### Origin settings (preconfigured) - - * Origin Access Control – CloudFront sets this up for you and adds the policy - - * Protocol – HTTPS only - - * HTTPS port – 443 - - * Minimum origin SSL protocol – TLSv1.2 - - * Origin path – None - - * Add custom header – None - - * Enable Origin Shield – No - - * Connection attempts – 3 - - * Response timeout – 30 - - * Keep-alive timeout – 5 - - - - -Following are the cache settings that CloudFront preconfigures for your Lambda function URL origin in a multi-tenant distribution. - -###### Cache settings (preconfigured) - - * Compress objects automatically – Yes - - * Viewer protocol policy – Redirect to HTTPS - - * Allowed HTTP method – `GET, HEAD, OPTIONS, PUT, POST, PATCH, DELETE` - - * Cache HTTP methods – No - - * Allow gRPC requests over HTTP/2 – No - - * Restrict viewer access – No - - * Cache policy – `CachingDisabled` (Possible values: `UseOriginCacheControlHeaders`, `UseOriginCacheControlHeaders-QueryStrings`) - - * Origin request policy – `AllViewerExceptHostHeader` - - * Response header policy – None - - * Smooth Streaming – No - - * Field level encryption – No - - * Enable real-time logs – No - - * Functions – No - - - - -Following are the settings that you can customize for your Lambda function URL origin in a multi-tenant distribution. - -###### Customizable settings - - * Enable Origin Shield – (Default: No) - - * Compress objects automatically – (Default: Yes) - - * Caching – (Default: `Cache by Default`) - - * If `Cache by Default` is selected, the `UseOriginCacheControlHeaders` cache policy is used. - - * If `Do Not Cache by Default` is selected, the `CachingDisabled` cache policy is used. - - * Include query string in cache – (Default: Yes, if `Cache by Default` is already selected) - - * If `Do Not Cache by Default` is already selected and you then choose to include the query string in the cache, the `UseOriginCacheControlHeaders-QueryStrings` cache policy is used. - - - -