- Newest
- Most votes
- Most comments
When you create a schedule in EventBridge, you have the opportunity to choose a flexible time window. This allows the scheduler to randomly distribute your schedule invocations within the time window you specify, reducing the likelihood of all schedules being fired at the same second and thus, hitting ECS runTask limit.
Besides, consider configuring a retry policy and dead letter queue for those scenarios when the invocation fails. EventBridge Scheduler will attempts to retry them according to your settings, increasing the likelihood of all them being processed.
If none of the above works, you may need to re-architect the solution. You could have an SQS queue as a the target of your schedules and trigger your ECS tasks based off the queue at the supported rate.
answered a year ago
You can service quota in your AWS console. This will shows the applied quotas for each service. Filter/search by ECS and you can find the relevant quota. If the quota is adjustable, then you can update it or you might need to log a support ticket. If it's not adjustable - that is a hard limit, then you cannot update it. You will need to rearchitect your design to overcome the hard limit.
Relevant content
asked 4 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 9 months ago
