AWS solutions documentation change
Summary
Added step for signing into AWS Management Console, updated step numbering, and fixed formatting for CORS Origin parameter
Security assessment
The changes are procedural updates and formatting improvements. While the CORS Origin parameter mentions security best practices, this is existing documentation and not a new security feature or vulnerability fix.
Diff
diff --git a/solutions/latest/serverless-image-handler/launch-stack.md index 7f9b1f6f2..c284d9380 100644 --- a/solutions/latest/serverless-image-handler/launch-stack.md +++ b/solutions/latest/serverless-image-handler/launch-stack.md @@ -13 +13 @@ Follow the step-by-step instructions in this section to configure and deploy the -[  ](https://console.aws.amazon.com/cloudformation/home?region=us-east-1#/stacks/new?stackName=DynamicImageTransformation&templateURL=https:%2F%2Fs3.amazonaws.com%2Fsolutions-reference%2Fdynamic-image-transformation-for-amazon-cloudfront%2Flatest%2Fdynamic-image-transformation-for-amazon-cloudfront.template&redirectId=ImplementationGuide) + 2. Sign into [AWS Management Console](https://aws.amazon.com/console) and select the button to launch `dynamic-image-transformation-for-amazon-cloudfront` CloudFormation template. [  ](https://console.aws.amazon.com/cloudformation/home?region=us-east-1#/stacks/new?stackName=DynamicImageTransformation&templateURL=https:%2F%2Fs3.amazonaws.com%2Fsolutions-reference%2Fdynamic-image-transformation-for-amazon-cloudfront%2Flatest%2Fdynamic-image-transformation-for-amazon-cloudfront.template&redirectId=ImplementationGuide) @@ -15 +15 @@ Follow the step-by-step instructions in this section to configure and deploy the - 2. The template launches in the US East (N. Virginia) Region by default. To launch the solution in a different AWS Region, use the Region selector in the console navigation bar. For a list of which AWS Regions support this solution, see [Supported AWS Regions](./plan-your-deployment.html#supported-aws-regions). + 3. The template launches in the US East (N. Virginia) Region by default. To launch the solution in a different AWS Region, use the Region selector in the console navigation bar. For a list of which AWS Regions support this solution, see [Supported AWS Regions](./plan-your-deployment.html#supported-aws-regions). @@ -17 +17 @@ Follow the step-by-step instructions in this section to configure and deploy the - 3. On the **Create stack** page, verify that the correct template URL is in the **Amazon S3 URL** text box and choose **Next**. + 4. On the **Create stack** page, verify that the correct template URL is in the **Amazon S3 URL** text box and choose **Next**. @@ -19 +19 @@ Follow the step-by-step instructions in this section to configure and deploy the - 4. On the **Specify stack details** page, assign a name to your solution stack. For information about naming character limitations, see [IAM and AWS STS quotas](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_iam-limits.html) in the _AWS Identity and Access Management User Guide_. + 5. On the **Specify stack details** page, assign a name to your solution stack. For information about naming character limitations, see [IAM and AWS STS quotas](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_iam-limits.html) in the _AWS Identity and Access Management User Guide_. @@ -21 +21 @@ Follow the step-by-step instructions in this section to configure and deploy the - 5. Under **Parameters** , review the parameters for this solution template and modify them as necessary. This solution uses the following default values. + 6. Under **Parameters** , review the parameters for this solution template and modify them as necessary. This solution uses the following default values. @@ -26 +26 @@ Follow the step-by-step instructions in this section to configure and deploy the -**CORS Origin** | * | This value is returned by the API in the **Access-Control-Allow-Origin** header. An asterisk value supports any origin. We recommend specifying a specific origin (Ex: [http://example.domain](http://example.domain)) to restrict cross-site access to your API. **Note:** This value is ignored if **CORS_ENABLED** is set to `No`. +**CORS Origin** | `*` | This value is returned by the API in the **Access-Control-Allow-Origin** header. An asterisk value supports any origin. We recommend specifying a specific origin (Ex: [http://example.domain](http://example.domain)) to restrict cross-site access to your API. **Note:** This value is ignored if **CORS_ENABLED** is set to `No`. @@ -43 +43 @@ Follow the step-by-step instructions in this section to configure and deploy the - 6. Choose **Next**. + 7. Choose **Next**. @@ -45 +45 @@ Follow the step-by-step instructions in this section to configure and deploy the - 7. On the **Configure stack options** page, choose **Next**. + 8. On the **Configure stack options** page, choose **Next**. @@ -47 +47 @@ Follow the step-by-step instructions in this section to configure and deploy the - 8. On the **Review and create** page, review and confirm the settings. Select the box acknowledging that the template creates IAM resources. + 9. On the **Review and create** page, review and confirm the settings. Select the box acknowledging that the template creates IAM resources. @@ -49 +49 @@ Follow the step-by-step instructions in this section to configure and deploy the - 9. Choose **Submit** to deploy the stack. + 10. Choose **Submit** to deploy the stack.