1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
1
The possible cause of the issue due to 1.AWS Fargate Spot instances are generally available, there can be times when spot capacity is limited or unavailable in specific regions 2.you might want to try running a small job on Fargate On-Demand to see if it executes as expected. 3.Double-check the service limits, not just for vCPUs, but also for other resources and limits related to AWS Batch and ECS 4.Verify that the necessary permissions and IAM roles are correctly configured.
con risposta 4 mesi fa
Contenuto pertinente
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 7 mesi fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 3 anni fa
This was the issue. I ended up creating two compute environments. The first one uses spot provisioning, and the second uses on-demand. This way, when spot is not available, it falls back to the on-demand.