CDK Sagemaker Batch Transform: TransformAmiVersion is not supported as part of TransformResources
- Dominant language
- TypeScript
- Stars
- 12.9k
- Forks
- 4.6k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 83
Description
### Describe the feature
We can deploy a sagemaker batch transform job with addition `TransformAmiVersion` field via boto3, but CDK does not accepts this argument.
https://docs.aws.amazon.com/sagemaker/latest/APIReference/API_TransformResources.html
https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_stepfunctions_tasks.TransformResources.html
### Use Case
This is important to get around the limitation of cuda 11.4 on batch transform jobs and launch sagemaker batch transform in an ami that supports new cuda and nvidia drivers.
https://docs.aws.amazon.com/sagemaker/latest/dg/inference-gpu-drivers.html
### Proposed Solution
We should add support for this field.
### Other Information
_No response_
### Acknowledgements
- [x] I may be able to implement this feature request
- [ ] This feature might incur a breaking change
### AWS CDK Library version (aws-cdk-lib)
2.207.0
### AWS CDK CLI version
2.207.0
### Environment details (OS name and version, etc.)
osx, linux
Contributor guide
Research direction
Start with the aws_stepfunctions_tasks.TransformResources API reference linked in the issue and compare it with the AWS SageMaker TransformResources API documentation. Determine how the missing TransformAmiVersion field is represented there, then verify that CDK accepts it and includes it in the resulting batch transform definition.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, typescript
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100