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年前
関連するコンテンツ
- AWS公式更新しました 9ヶ月前