1 Answer
- Newest
- Most votes
- Most comments
0
The Fargate task retirement is about the patch applied on it for bug fix or security patch purpose.
Here is the part of documentation which talks about it:
If a security issue is found that affects an existing platform version, AWS creates a new patched revision of the platform version and retires tasks running on the vulnerable revision. In some cases, you may be notified that your tasks on Fargate have been scheduled for retirement. For more information, see AWS Fargate task maintenance FAQs.
The FAQ has a comprehensive list of common questions and answers related to this topic.
I hope this helps you to clarify this question.
Relevant content
AWS OFFICIALUpdated a year ago- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 17 days ago
I do understand the why behind the task retirement. The question is, why the resources are still marked as affected in the health dashboard, even though I performed the update of the service to make sure it happened in our maintenance window (as suggested in the email informing me about the routine retirement). Also the "last update time" of these resources is wrong in the health dashboard.
The Health Dashboard doesn't have directly relation with the task status. For instance, the "affected" information showing there was about the time that the notification was sent. If you have done the Task replacement already, you don't need to worry about it. The same for the other fields on it. All the columns showing on the Health Dashboard are about the message itself, not about the resource referred on it. Let me know if you have further queries about it.
OK, great to know. Thanks!