AWS AmazonECS documentation change
Summary
Added placeholder section for platform version 1.4.0 and removed detailed changelog for version 1.3.0
Security assessment
The change removes documentation about security-adjacent features like secrets injection and secure log configuration from the 1.3.0 changelog, but does not indicate any active security vulnerability. The addition of 1.4.0 contains no security-related content. This appears to be routine version history maintenance rather than addressing a specific security issue.
Diff
diff --git a/AmazonECS/latest/developerguide/platform-versions-changelog.md b/AmazonECS/latest/developerguide/platform-versions-changelog.md index fca04bcc2..28613c58f 100644 --- a//AmazonECS/latest/developerguide/platform-versions-changelog.md +++ b//AmazonECS/latest/developerguide/platform-versions-changelog.md @@ -4,0 +5,2 @@ +1.4.0 + @@ -8,0 +11,2 @@ The following are the available Linux platform versions. For information about p +## 1.4.0 + @@ -48,23 +51,0 @@ The following is the changelog for platform version `1.4.0`. -The following is the changelog for platform version `1.3.0`. - - * Beginning on Sept 30, 2019, any new Fargate task that is launched supports the `awsfirelens` log driver. Configure the FireLens for Amazon ECS to use task definition parameters to route logs to an AWS service or AWS Partner Network (APN) destination for log storage and analytics. For more information, see [Send Amazon ECS logs to an AWS service or AWS Partner](./using_firelens.html). - - * Added task recycling for Fargate tasks, which is the process of refreshing tasks that are a part of an Amazon ECS service. For more information, [Task retirement and maintenance for AWS Fargate on Amazon ECS](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-maintenance.html). - - * Beginning on March 27, 2019, any new Fargate task that is launched can use additional task definition parameters that you use to define a proxy configuration, dependencies for container startup and shutdown as well as a per-container start and stop timeout value. For more information, see [Proxy configuration](./task_definition_parameters.html#proxyConfiguration), [Container dependency](./task_definition_parameters.html#container_definition_dependson), and [Container timeouts](./task_definition_parameters.html#container_definition_timeout). - - * Beginning on April 2, 2019, any new Fargate task that is launched supports injecting sensitive data into your containers by storing your sensitive data in either AWS Secrets Manager secrets or AWS Systems Manager Parameter Store parameters and then referencing them in your container definition. For more information, see [Pass sensitive data to an Amazon ECS container](./specifying-sensitive-data.html). - - * Beginning on May 1, 2019, any new Fargate task that is launched supports referencing sensitive data in the log configuration of a container using the `secretOptions` container definition parameter. For more information, see [Pass sensitive data to an Amazon ECS container](./specifying-sensitive-data.html). - - * Beginning on May 1, 2019, any new Fargate task that is launched supports the `splunk` log driver in addition to the `awslogs` log driver. For more information, see [Storage and logging](./task_definition_parameters.html#container_definition_storage). - - * Beginning on July 9, 2019, any new Fargate tasks that is launched supports CloudWatch Container Insights. For more information, see [Monitor Amazon ECS containers using Container Insights with enhanced observability](./cloudwatch-container-insights.html). - - * Beginning on December 3, 2019, the Fargate Spot capacity provider is supported. For more information, see [Amazon ECS clusters for Fargate](./fargate-capacity-providers.html). - - * Based on Amazon Linux 2. - - - -