AWS solutions documentation change
Summary
Removed ECS template parameters and post-deployment configuration steps, updated section headers for architectural clarity
Security assessment
The changes primarily restructure documentation sections and remove administrative configuration details like admin email setup and Cognito credential guidance. While these relate to access control, there's no evidence of addressing a specific security vulnerability. The removal of credential-related documentation could impact security awareness but doesn't directly patch a vulnerability.
Diff
diff --git a/solutions/latest/dynamic-image-transformation-for-amazon-cloudfront/deploy-alb-ecs.md b/solutions/latest/dynamic-image-transformation-for-amazon-cloudfront/deploy-alb-ecs.md index 032702a71..f9a6ba83b 100644 --- a//solutions/latest/dynamic-image-transformation-for-amazon-cloudfront/deploy-alb-ecs.md +++ b//solutions/latest/dynamic-image-transformation-for-amazon-cloudfront/deploy-alb-ecs.md @@ -5,2 +4,0 @@ -ECS architecture template parametersPost-deployment configuration (ECS architecture) - @@ -28,40 +25,0 @@ Follow the step-by-step instructions in this section to configure and deploy the -## ECS architecture template parameters - -+ - -**Parameter** | **Default** | **Description** ----|---|--- -**Admin Email** | <Requires input> | The email address of the admin user for the Admin UI. Must be a valid email address (7-100 characters). This email will receive the initial login credentials for the administrative interface. -**Deployment Size** | small | T-shirt sizing for ECS Fargate deployment configuration. Options: small, medium, large, xlarge. This determines the number of ECS tasks, CPU, and memory allocation. Refer to [sizing guidance](./plan-your-deployment.html#choosing-deployment-architecture) for details. -**Origin Override Header** | _< Optional input>_ | HTTP header name used to override the origin destination for image requests. Must be a valid HTTP header name or empty. Useful for routing requests to different origins based on custom headers. - - 1. Choose **Next**. - - 2. On the **Configure stack options** page, choose **Next**. - - 3. On the **Review and create** page, review and confirm the settings. Select the box acknowledging that the template creates IAM resources. - - 4. Choose **Submit** to deploy the stack. - -You can view the status of the stack in the AWS CloudFormation console in the **Status** column. You should receive a CREATE_COMPLETE status in approximately 20 minutes. - - - - -## Post-deployment configuration (ECS architecture) - -After deploying the ECS template, additional configuration steps are required to fully utilize the advanced features: - -**Admin UI Access:** The Admin UI link is available in the CloudFormation stack outputs section. Access the Admin UI from there and sign in using the provided Cognito credentials. - -**Initial Configuration:** - - * **Configure Origins** : Use the Admin UI to add your S3 buckets and external origins - - * **Create Mappings** : Set up path-based or host-header mappings to route requests to origins - - * **Define Policies** : Create transformation policies for consistent image processing - - - - @@ -74 +32 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Deploy Lambda architecture +Lambda architecture template parameters @@ -76 +34 @@ Deploy Lambda architecture -Attaching an existing CloudFront distribution +ECS architecture template parameters