2 Answers
- Newest
- Most votes
- Most comments
0
The solution is to wait a little bit in order to let Batch launch more instances = )
answered 5 years ago
0
I accomplished this by defining a job environment with a specific instance type. Then the job definition used that job environment with the specific cpu/memory requirements of that instance. This always ensured each job would run on its own instance.
answered 5 years ago
Relevant content
- asked 4 months ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago