AWS AmazonECS documentation change
Summary
Minor wording change from 'This is recommended' to 'We recommend this approach' regarding storing sensitive information in S3
Security assessment
Change is purely editorial with no security implications. It reinforces existing security advice about credential storage but doesn't introduce new security concepts or address vulnerabilities.
Diff
diff --git a/AmazonECS/latest/developerguide/ecs-agent-install.md b/AmazonECS/latest/developerguide/ecs-agent-install.md index db219d66a..e86bbf80d 100644 --- a//AmazonECS/latest/developerguide/ecs-agent-install.md +++ b//AmazonECS/latest/developerguide/ecs-agent-install.md @@ -84 +84 @@ For more information about these and other agent runtime options, see [Amazon EC -You can optionally store your agent environment variables in Amazon S3 (which can be downloaded to your container instances at launch time using Amazon EC2 user data). This is recommended for sensitive information such as authentication credentials for private repositories. For more information, see [Storing Amazon ECS container instance configuration in Amazon S3](./ecs-config-s3.html) and [Using non-AWS container images in Amazon ECS](./private-auth.html). +You can optionally store your agent environment variables in Amazon S3 (which can be downloaded to your container instances at launch time using Amazon EC2 user data). We recommend this approach for sensitive information such as authentication credentials for private repositories. For more information, see [Storing Amazon ECS container instance configuration in Amazon S3](./ecs-config-s3.html) and [Using non-AWS container images in Amazon ECS](./private-auth.html).