Background
My organization received the email below, informing about an upcoming update that would - if I understood correctly - restart the affected tasks sometime after 17 Jun 2024. Under the "Affected resources" tab for this event in AWS Health all our services - which are all running on Fargate platform version 1.4.0 - in all clusters are listed. Since some of our services can not be restarted without some impact on their state, we want to restart them manually at a time that is convenient to us. I tried to restart a couple of services using AWS CLI according to the instructions for rolling deployment type services in the email. I also tried a force redeployment using AWS Console for a couple of other services. I did this after Mon, 10 Jun. Despite this, they are still listed in the Affected resources tab as still pending under "Resource status" after 2 days. The referenced link https://docs.aws.amazon.com/AmazonECS/latest/userguide/AWS_Fargate-versions.html does not mention any newer version than Fargate 1.4.0.
According to an answer to this re:Post question from someone with a similar question as me https://repost.aws/questions/QUHYlXWwgYQGaZzRPLqBS_eg/account-health-marks-fargate-clusters-needing-upgrade-even-though-they-are-on-the-latest-version, this is about a patch release of Fargate that does not have a new version number, and the Affected resources tab is not updated even if the proposed instructions for manual update are followed.
My question: is there no way of me to verify that the manual restarts has taken effect, and that the restarted services will not be restarted again as a part of the upcoming update event?
The received email (with identical info found under the event in AWS Health):
Subject: [Notification] Upcoming routine retirement of your AWS Elastic Container Service tasks running on AWS Fargate beginning Mon, 17 Jun 2024 05:00 GMT. [AWS Account: 123123123123]
To: aws@exampledomain.com
Hello,
You are receiving this notification because AWS Fargate has deployed a new platform version revision [1] and will retire any tasks running on previous platform version revision(s) starting at Mon, 17 Jun 2024 05:00 GMT as part of routine task maintenance [2]. Please check the "Affected Resources" tab of your AWS Health Dashboard for a list of affected tasks. There is no action required on your part unless you want to replace these tasks before Fargate does. When using the default value of 100% for minimum healthy percent configuration of an ECS service [3], a replacement task will be launched on the most recent platform version revision before the affected task is retired. Any tasks launched after Mon, 10 Jun 2024 05:00 GMT were launched on the new platform version revision.
AWS Fargate is a serverless, pay-as-you-go compute engine that lets you focus on building applications without managing servers. As described in the Fargate documentation [2] and [4], Fargate regularly deploys platform version revisions to make new features available and for routine maintenance. The Fargate update includes the most current Linux kernel and runtime components. Fargate will gradually replace the tasks in your service using your configured deployment settings, ensuring all tasks run on the new Fargate platform version revision.
We do not expect this update to impact your ECS services. However, if you want to control when your tasks are replaced, you can initiate an ECS service update before Mon, 17 Jun 2024 05:00 GMT by following the instructions below.
If you are using the rolling deployment type for your service, you can run the update-service command from the AWS command-line interface specifying force-new-deployment:
$ aws ecs update-service --service service_name
--cluster cluster_name --force-new-deployment
If you are using the Blue/Green deployment type, please refer to the documentation for create-deployment [5] and create a new deployment using the same task definition version.
Please contact AWS Support [6] if you have any questions or concerns.
[1] https://docs.aws.amazon.com/AmazonECS/latest/userguide/AWS_Fargate-versions.html
[2] https://docs.aws.amazon.com/AmazonECS/latest/userguide/task-maintenance.html
[3] https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service_definition_parameters.html#sd-deploymentconfiguration
[4] https://aws.amazon.com/blogs/containers/improving-operational-visibility-with-aws-fargate-task-retirement-notifications/
[5] https://docs.aws.amazon.com/cli/latest/reference/deploy/create-deployment.html
[6] https://aws.amazon.com/support
Thanks a lot for your answer (both author and reviewer), not I feel a bit more confident about what to expect next week!
For anyone from AWS reading this, I'm a bit frustrated that the information about the event referred to "Affected resources" but did not mention that the list was static, and that the info did not mention that the updated platform version revision would not show up as a change in the platform version number (ie 1.4.0). It would have saved us a couple of hours. I have sent this as a feedback on the event.
@LilyB - Your feedback is taken, we will work towards improving messaging and overall process.
@containerised I appreciate it.