- Newest
- Most votes
- Most comments
Hi Eric, thanks for reaching out!
Looking in to this, I was able to confirm internally that the ResourceRequirement parameters under ContainerOverrides are not processed when configuring a Batch Job as an EventBridge rule target. The parameters under Command will be accepted, but ResourceRequirements do not get passed from the EventBridge Target to the Batch Job. I can also confirm that there is a Feature Request in place to allow for this, but I'm unable to provide an ETA on when this may be available.
However, I can recommend that instead of using an EventBridge rule with a cron expression, you can accomplish your use case using the newer EventBridge Scheduler feature. This feature has TerraForm support and will allow you to schedule direct Batch SubmitJob calls with all the parameters you wish to pass, including Container Override parameters with ResourceRequirement fields.
I tested this feature with VCPU and MEMORY ResourceRequirements with a Scheduler schedule in the console and passed the following JSON for the API call:
{
"JobDefinition": "arn:aws:batch:us-west-1:123456789012:<definition>",
"JobName": "MyData",
"JobQueue": "arn:aws:batch:us-west-1:123456789012:<queue>",
"ContainerOverrides": {
"ResourceRequirements": [{
"Type": "VCPU",
"Value": "4"
},
{
"Type": "MEMORY",
"Value": "8192"
}
]
}
}
The job was successfully started using the VCPU and MEMORY requirements specified in my ContainerOverride fields.
I hope this information was helpful!
Relevant content
- asked 4 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago

Justin, thank you very much for all the info. I will get with our Cloud team and see if we can start using Scheduler. That definitely seems like the better way to go!