- Newest
- Most votes
- Most comments
The ElasticContainerService task patching retirement notification you've received is not related to the task revision you're running, but rather to the underlying Fargate platform version. AWS Fargate regularly deploys platform version revisions to provide new features and perform routine maintenance, which includes updates to the Linux kernel and runtime components.
Even if your tasks are running the latest task revision, they may still be using an older Fargate platform version. The notification indicates that AWS has deployed a new platform version revision, and tasks running on previous platform version revisions will be retired.
The fact that two entities are affected suggests you have two tasks or services that are running on an older Fargate platform version, despite potentially using the latest task revision. To address this:
-
You don't necessarily need to take any action. AWS will automatically replace these tasks with new ones running on the updated platform version during the specified time window.
-
If you want to control when the update occurs, you can manually update your services before the specified date. For rolling deployment type services, you can use the AWS CLI command:
aws ecs update-service --service service_name --cluster cluster_name --force-new-deployment
-
For Blue/Green deployment type services, you'll need to create a new deployment using the same task definition version.
It's important to note that the "Affected resources" status in these notifications is static and won't change even if you take action. To verify that your tasks have been updated, you can check their start time - if they were launched after the date specified in the notification, they are running on the new platform version revision.
Sources
Received email about "Upcoming routine retirement of your AWS Elastic Container Service tasks running on AWS Fargate" but they are already running the latest Fargate version | AWS re:Post
AWS Fargate new platform notifications | AWS re:Post
Relevant content
published 3 years ago
