Describe the feature
Add support for launchTemplateId when attaching a launchTemplate to a Batch Compute environment. Currently it requires using a launchTemplateName.
new batch.ComputeEnvironment(this, 'ComputeEnv', {
computeResources: {
launchTemplate: {
launchTemplateName: myLaunchTemplate.launchTemplateName as string, //or simply use an existing template name
},
vpc,
}
});
This should be supported: https://docs.aws.amazon.com/batch/latest/APIReference/API_LaunchTemplateSpecification.html
Use Case
I would like to stop naming resources explicitly as per CDK best practice and let CDK handle naming the launch template.
Proposed Solution
No response
Other Information
No response
Acknowledgements
CDK version used
1.153.1
Environment details (OS name and version, etc.)
Amazon Linux 2
Describe the feature
Add support for
launchTemplateIdwhen attaching a launchTemplate to a Batch Compute environment. Currently it requires using a launchTemplateName.This should be supported: https://docs.aws.amazon.com/batch/latest/APIReference/API_LaunchTemplateSpecification.html
Use Case
I would like to stop naming resources explicitly as per CDK best practice and let CDK handle naming the launch template.
Proposed Solution
No response
Other Information
No response
Acknowledgements
CDK version used
1.153.1
Environment details (OS name and version, etc.)
Amazon Linux 2