Upcoming retirement of your standalone AWS Elastic Container Service tasks running on AWS Fargate

Hello.

It seems that you need to start a new task and replace the one you are currently using as described in the document [1].
https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-maintenance.html

For standalone task retirement, AWS stops the task on or after the task retirement date. we don’t launch a replacement task when a task is stopped. If you need these tasks to continue to run, you need to stop the running tasks and launch a replacement task before the time indicated in the notification. Therefore, we recommend that customers monitor the state of standalone tasks and if required, implement logic to replace the stopped tasks.

I'm not sure how you use ECS Fargate, but I thought starting a new task and stopping the affected Fargate task would solve it.
https://repost.aws/knowledge-center/ecs-run-task-cluster

Just to be sure, when starting a new task, make sure that the platform version of the task is new.
https://docs.aws.amazon.com/AmazonECS/latest/developerguide/platform-versions-retired.html

Hello,

To handle the retirement of tasks due to a new AWS Fargate platform version revision, follow these steps:

For Standalone Tasks:

1. Identify the affected standalone tasks from the "Affected Resources" tab in the AWS Health Dashboard.
2. Stop the affected standalone tasks in the Amazon ECS console.
3. Launch new replacement tasks using the same configuration as before.
4. Verify that the new tasks are running correctly.
5. Monitor for future notifications and repeat the process when new platform versions are released (optional).

For Service Tasks (Optional):

1. Identify the affected services from the "Affected Resources" tab in the AWS Health Dashboard.
2. Update the affected service using the Force Update option, which will trigger a deployment of new tasks using the latest platform version.
3. Monitor the service update to ensure the new tasks are running correctly and the old tasks are being drained and stopped.
4. Monitor for future notifications and repeat steps 2-3 when new platform versions are released.

Obs: This step is optional since the Service will take care automatically to the task replacement following the deployment configuration (min/max).

Throughout the process, feel free to reach out to AWS Support if you encounter any issues or have specific questions. Additionally, familiarize yourself with the AWS Fargate documentation on task maintenance and platform version revisions for a better understanding of the rationale and processes involved.