AWS AmazonECS high security documentation change
Summary
Added deprecation timeline for Fargate platform version 1.3.0 with force-update dates and termination schedule, updated migration instructions, and added detailed changelog for version 1.3.0
Security assessment
The change explicitly states that deprecated platform versions will stop receiving security updates after deprecation date. The forced migration timeline helps prevent security risks from running outdated software. The mention of discontinued security updates for deprecated versions constitutes a security-related maintenance requirement.
Diff
diff --git a/AmazonECS/latest/developerguide/platform-versions-retired.md b/AmazonECS/latest/developerguide/platform-versions-retired.md index 982f5df90..b510d0ca0 100644 --- a//AmazonECS/latest/developerguide/platform-versions-retired.md +++ b//AmazonECS/latest/developerguide/platform-versions-retired.md @@ -9 +9,7 @@ Deprecated Fargate Linux versions change log -This page lists Linux platform versions that AWS Fargate has deprecated or have been scheduled for deprecation. These platform versions remain available until the published deprecation date. +###### Important + +On March 2, 2026, AWS will start force-updating all the Amazon ECS services running Fargate platform version 1.3.0 that are not migrated to the platform version 1.4.0. That may potentially impact your workloads. Starting March 16, 2026, we will make the platform version 1.3.0 as Retired. At that time, you will not be able to launch new tasks or create new services configured with platform version 1.3.0, but your existing tasks will continue running. On March 31, 2026, we will terminate all the remaining running tasks configured with platform version 1.3.0. + +For information about how to migrate to platform version 1.4, see [Migrating to Linux platform version 1.4.0 on Amazon ECS](./platform-version-migration.html). + +The following table lists Linux platform versions that AWS Fargate has deprecated or have been scheduled for deprecation. These platform versions remain available until the published deprecation date. @@ -13 +19 @@ A _force update date_ is provided for each platform version scheduled for deprec -We recommend updating your services standalone tasks to use the most recent platform version. For more information on migrating to the most recent platform version, see [Migrating to Linux platform version 1.4.0 on Amazon ECS](./platform-version-migration.html). +For information about how to migrate to latest platform version, see [Migrating to Linux platform version 1.4.0 on Amazon ECS](./platform-version-migration.html). @@ -15 +21 @@ We recommend updating your services standalone tasks to use the most recent plat -Once a platform version reaches the _deprecation date_ , the platform version will no longer be available for new tasks or services. Any standalone tasks or services which explicitly use a deprecated platform version will continue using that platform version until the tasks are stopped. After the deprecation date, a deprecated platform version will no longer receive any security updates or bug fixes. +After a platform version reaches the _deprecation date_ , the platform version will no longer be available for new tasks or services. Any standalone tasks or services which explicitly use a deprecated platform version will continue using that platform version until the tasks are stopped. After the deprecation date, a deprecated platform version will no longer receive any security updates or bug fixes. @@ -21,0 +28 @@ Platform version | Force update date | Deprecation date +1.3.0 | March 2, 2026 | March 16, 2026 @@ -26,0 +34,25 @@ For information about current platform versions, see [Fargate platform versions +### 1.3.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. + + + +