Describe the bug
It seems that the Batch MultiNodeJobDefinition CDK Construct requires instance type to be defined. However, instanceType is not required by the Batch AWS SDK.
This seems to be more than a documentation issue, as I'm unable to create a MultiNodeJobDefinition in my CDK package without specifying instance type.
This constraint takes away from one of the primary advantages to having Batch manage our EC2 resources in that they optimally assign batch jobs to instance types based on availability/resource requirements.
Expected Behavior
We shouldn't need to specify instance type. Batch should determine it based on job resource requirements.
Current Behavior
CDK requires instance type to be required at job definition level.
Reproduction Steps
Create a MultiNodeJobDefinition.
Possible Solution
No response
Additional Information/Context
No response
CDK CLI Version
2.96.2
Framework Version
No response
Node.js Version
18.x
OS
linux
Language
Typescript
Language Version
No response
Other information
No response
Describe the bug
It seems that the Batch MultiNodeJobDefinition CDK Construct requires instance type to be defined. However, instanceType is not required by the Batch AWS SDK.
This seems to be more than a documentation issue, as I'm unable to create a MultiNodeJobDefinition in my CDK package without specifying instance type.
This constraint takes away from one of the primary advantages to having Batch manage our EC2 resources in that they optimally assign batch jobs to instance types based on availability/resource requirements.
Expected Behavior
We shouldn't need to specify instance type. Batch should determine it based on job resource requirements.
Current Behavior
CDK requires instance type to be required at job definition level.
Reproduction Steps
Create a MultiNodeJobDefinition.
Possible Solution
No response
Additional Information/Context
No response
CDK CLI Version
2.96.2
Framework Version
No response
Node.js Version
18.x
OS
linux
Language
Typescript
Language Version
No response
Other information
No response