[service] [request]: Idempotency on aws batch SubmitJob API
- Dominant language
- Shell
- Stars
- 5.4k
- Forks
- 334
- PR merge metrics
- No merged PRs in 30d
Description
### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment
No
**Tell us about your request**
What do you want us to build?
We are facing issue when same request is being sent to SubmitJob we need to send error so that another batch job is not triggered. If possible on the submitJobRequestId
**Which service(s) is this request for?**
Fargate, ECS
**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
We are facing issue where the same job with same request id is getting triggered twice, please refer to ticket: https://support.console.aws.amazon.com/support/home#/case/?displayId=176837491000036&language=en
**Are you currently working around this issue?**
How are you currently solving this problem?
No not working
**Additional context**
Anything else we should know?
Please refer ticket https://support.console.aws.amazon.com/support/home#/case/?displayId=176837491000036&language=en
**Attachments**
If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look. (Remember to remove any personally-identifiable information.)
Contributor guide
Research direction
Start by reading the AWS Batch SubmitJob API documentation and the support case linked in the issue. The repository files and tests to change are not identified, so confirm the intended idempotency behavior and service ownership before implementation. Done should mean that repeated submissions with the same request ID are handled predictably and do not trigger a duplicate batch job.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- api, cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100