1 個回答
- 最新
- 最多得票
- 最多評論
0
Well, didn't find any recommended approach yet.
So, I resolve this issue as follows:
- When the container initiated from the code, maintaining the taskId reference in db.
- EventBridge to capture all the container events from the required ECS cluster and send to Lambda function.
- At lambda function, capturing the required stopReason and calling the API call for reprocess.
- Because the lambda function is firing multiple times with the same taskId (actually taskArn) so at the API level maintaining the reprocess counters.
Do let me know if is there any better way to do it.
已回答 1 年前
相關內容
- 已提問 6 個月前
- AWS 官方已更新 8 個月前
- AWS 官方已更新 1 年前
- AWS 官方已更新 2 年前