aws-sagemaker: Studio Lifecycle Configuration can not be created with aws-cdk
- Dominant language
- TypeScript
- Stars
- 12.9k
- Forks
- 4.6k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 83
Description
### Describe the feature
One can not create a Sagemaker Studio Lifecycle Configuration using aws-cdk
### Use Case
I want to create a Sagemaker Studio Domain with a Lifecycle Configuration. There exists no classes to create a Lifecycle Configuration.
```
cfn_domain = sagemaker.CfnDomain(self, "MyCfnDomain",
auth_mode="authMode",
default_user_settings=sagemaker.CfnDomain.UserSettingsProperty(
execution_role="executionRole",
jupyter_server_app_settings=sagemaker.CfnDomain.JupyterServerAppSettingsProperty(
default_resource_spec=sagemaker.CfnDomain.ResourceSpecProperty(
instance_type="instanceType",
lifecycle_config_arn="lifecycleConfigArn",
sage_maker_image_arn="sageMakerImageArn",
sage_maker_image_version_arn="sageMakerImageVersionArn"
)
),
```
https://docs.aws.amazon.com/cdk/api/v2/python/aws_cdk.aws_sagemaker/CfnDomain.html
### Proposed Solution
_No response_
### Other Information
_No response_
### Acknowledgements
- [ ] I may be able to implement this feature request
- [ ] This feature might incur a breaking change
### CDK version used
2.50.0
### Environment details (OS name and version, etc.)
macOS Monterey 12.6
Contributor guide
Research direction
Start with the aws-sagemaker CfnDomain API linked in the issue and the corresponding AWS SageMaker CloudFormation resource documentation. Trace how aws-cdk exposes SageMaker resources, then determine the missing Lifecycle Configuration construct and its expected properties; done means a lifecycle configuration can be defined and attached to a Studio Domain through the CDK API.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, python, typescript
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100