AWS mwaa documentation change
Summary
Updated documentation to replace 'AWS CloudFormation' with 'CloudFormation' throughout the file for terminology consistency
Security assessment
The changes are purely terminological, replacing 'AWS CloudFormation' with 'CloudFormation' without altering any security-related content or permissions guidance. No evidence of addressing security vulnerabilities or adding security features.
Diff
diff --git a/mwaa/latest/userguide/samples-ecs-operator.md b/mwaa/latest/userguide/samples-ecs-operator.md index 3a37299dd..5c964a72d 100644 --- a//mwaa/latest/userguide/samples-ecs-operator.md +++ b//mwaa/latest/userguide/samples-ecs-operator.md @@ -9 +9 @@ VersionPrerequisitesPermissionsCreate an Amazon ECS clusterCode sample -This topic describes how you can use the `ECSOperator` to connect to an Amazon Elastic Container Service (Amazon ECS) container from Amazon MWAA. In the following steps, you'll add the required permissions to your environment's execution role, use a AWS CloudFormation template to create an Amazon ECS Fargate cluster, and finally create and upload a DAG that connects to your new cluster. +This topic describes how you can use the `ECSOperator` to connect to an Amazon Elastic Container Service (Amazon ECS) container from Amazon MWAA. In the following steps, you'll add the required permissions to your environment's execution role, use a CloudFormation template to create an Amazon ECS Fargate cluster, and finally create and upload a DAG that connects to your new cluster. @@ -77 +77 @@ JSON - * In addition to adding the required premissions to run tasks in Amazon ECS, you must also modify the CloudWatch Logs policy statement in your Amazon MWAA execution role to allow access to the Amazon ECS task log group as listed in the following. The Amazon ECS log group is created by the AWS CloudFormation template in Create an Amazon ECS cluster. + * In addition to adding the required premissions to run tasks in Amazon ECS, you must also modify the CloudWatch Logs policy statement in your Amazon MWAA execution role to allow access to the Amazon ECS task log group as listed in the following. The Amazon ECS log group is created by the CloudFormation template in Create an Amazon ECS cluster. @@ -103 +103 @@ For more information about the Amazon MWAA execution role, and how to attach a p -Using the following AWS CloudFormation template, you will build an Amazon ECS Fargate cluster to use with your Amazon MWAA workflow. For more information, refer to [Creating a task definition](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/create-task-definition) in the _Amazon Elastic Container Service Developer Guide_. +Using the following CloudFormation template, you will build an Amazon ECS Fargate cluster to use with your Amazon MWAA workflow. For more information, refer to [Creating a task definition](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/create-task-definition) in the _Amazon Elastic Container Service Developer Guide_. @@ -246 +246 @@ Alternatively, you can use the following shell script. The script retrieves the - 1. Copy, and save the script as `ecs-stack-helper.sh` in the same directory as your AWS CloudFormation template. + 1. Copy, and save the script as `ecs-stack-helper.sh` in the same directory as your CloudFormation template. @@ -273 +273 @@ Alternatively, you can use the following shell script. The script retrieves the -If successful, you'll refer to the following output showing your new AWS CloudFormation stack ID. +If successful, you'll refer to the following output showing your new CloudFormation stack ID. @@ -282 +282 @@ If successful, you'll refer to the following output showing your new AWS CloudFo -After your AWS CloudFormation stack is completed and AWS has provisioned your Amazon ECS resources, you're ready to create and upload your DAG. +After your CloudFormation stack is completed and AWS has provisioned your Amazon ECS resources, you're ready to create and upload your DAG.