AWS AmazonCloudFront documentation change
Summary
Added example parameters section with S3/custom origin templates, updated WAF documentation link, clarified domain name requirements, and expanded use case with parameter implementation details
Security assessment
The WAF web ACL section describes existing security controls but only changes a documentation link. Domain name requirement clarification and parameter examples improve configuration accuracy but don't address vulnerabilities. No evidence of patching security flaws or disclosing incidents.
Diff
diff --git a/AmazonCloudFront/latest/DeveloperGuide/tenant-customization.md b/AmazonCloudFront/latest/DeveloperGuide/tenant-customization.md index 2b7e11002..fccb10906 100644 --- a//AmazonCloudFront/latest/DeveloperGuide/tenant-customization.md +++ b//AmazonCloudFront/latest/DeveloperGuide/tenant-customization.md @@ -5 +5 @@ -How parameters work with distribution tenants +How parameters work with distribution tenantsExample parameters @@ -15 +15 @@ You can customize the following: - * **AWS WAF web ACL (V2)** – You can specify a separate web ACL for the distribution tenant, which will _override_ the web ACL used for the multi-tenant distribution. You can also disable this setting for a specific distribution tenant, which means the distribution tenant won't inherit the web ACL protections from the multi-tenant distribution. For more information, see [AWS WAF web ACL](./distribution-web-values-specify.html#DownloadDistValuesWAFWebACL). + * **AWS WAF web ACL (V2)** – You can specify a separate web ACL for the distribution tenant, which will _override_ the web ACL used for the multi-tenant distribution. You can also disable this setting for a specific distribution tenant, which means the distribution tenant won't inherit the web ACL protections from the multi-tenant distribution. For more information, see [AWS WAF web ACL](./DownloadDistValuesGeneral.html#DownloadDistValuesWAFWebACL). @@ -23 +23 @@ You can customize the following: - * **Domain names** – Unlike standard distributions, you can specify domain names for your distribution tenants (at the tenant-level). You must specify at least one domain name per distribution tenant. + * **Domain names** – You must specify at least one domain name per distribution tenant. @@ -51,0 +52,89 @@ In the multi-tenant distribution, you can define up to two parameters for each o +## Example parameters + +See the following examples for using parameters for the domain name and origin path. + +**Domain name parameters** + +In the multi-tenant distribution configuration, you can define a parameter for the origin domain name like the following examples: + +###### Amazon S3 + + * `{{`parameter1`}}.amzn-s3-demo-logging-bucket.s3.us-east-1.amazonaws.com` + + * `{{`parameter1`}}–amzn-s3-demo-logging-bucket.s3.us-east-1.amazonaws.com` + + + + +###### Custom origins + + * `{{`parameter1`}}.lambda-url.us-east-1.on.aws` + + * `{{`parameter1`}}.mediapackagev2.ap-south-1.amazonaws.com` + + + + +When you create a distribution tenant, specify the value to use for ``parameter1``. + + + "Parameters": [ + { + "Name": "parameter1", + "Value": "mycompany-website" + } + ] + + +Using the previous examples specified in the multi-tenant distribution, the origin domain name for the distribution tenant resolves to the following: + + * ``mycompany-website`.amzn-s3-demo-bucket3.s3.us-east-1.amazonaws.com` + + * ``mycompany-website`–amzn-s3-demo-bucket3.s3.us-east-1.amazonaws.com` + + * ``mycompany-website`.lambda-url.us-east-1.on.aws` + + * ``mycompany-website`.mediapackagev2.ap-south-1.amazonaws.com` + + + + +**Origin path parameters** + +Similarly, you can define parameters for the origin path in the multi-tenant distribution like the following examples: + + * `/{{``parameter2``}}` + + * `/{{``parameter2``}}/test` + + * `/public/{{``parameter2``}}/test` + + * `/search?name={{``parameter2``}}` + + + + +When you create a distribution tenant, specify the value to use for ``parameter2``. + + + "Parameters": [ + { + "Name": "parameter2", + "Value": "myBrand" + } + ] + + +Using the previous examples specified in the multi-tenant distribution, the origin path for the distribution tenant resolves to the following: + + * `/`myBrand`` + + * `/`myBrand`/test` + + * `/public/`myBrand`/test` + + * `/search?name=`myBrand`` + + + + @@ -58 +147,7 @@ You want to create multiple websites (tenants) for your customers, and you need - 2. For the origin domain name, you create a parameter named `customer-name` and specify that it's required. You enter the parameter after the S3 bucket, so that it appears as `https://amzn-s3-demo-bucket1.s3.region-code.amazonaws.com/`{{customer-name}}``. + 2. For the origin domain name, you create a parameter named `customer-name` and specify that it's required. You enter the parameter before the S3 bucket, so that it appears as: + +`{{`customer-name`}}.amzn-s3-demo-bucket3.s3.us-east-1.amazonaws.com`. + + 3. For origin path, you create a second parameter named `my-theme`, and specify that it's optional, with a default value of `basic`. Your origin path appears as: `/{{`my-theme`}}` + + 4. When you create a distribution tenant: @@ -60 +155 @@ You want to create multiple websites (tenants) for your customers, and you need - 3. For origin path, you create a second parameter named `my-theme`, and specify that it's optional, with a default value of `basic`. Your origin path appears as ``/{{my-theme}}`` + * For domain name, you must specify a value for `customer-name`, because it's marked as required in the multi-tenant distribution. @@ -62 +157 @@ You want to create multiple websites (tenants) for your customers, and you need - 4. When you create a distribution tenant, you must specify a value for `{{customer-name}}` for the origin domain name because it's required. For the origin path, you can specify your own value for the `{{my-theme}} ` parameter. If you don't, the distribution tenant will use the default value that you specified earlier. + * For origin path, you can optionally specify a value for `my-theme` or use the default value. @@ -73 +168 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -CloudFront multi-tenant distribution reference +Understand how multi-tenant distributions work