The new Sagemaker Studio (non Classic) allows bringing your own JupyterLab container images. According to the CreateDomain API, the StudioWebPortalSettings has a property HiddenSageMakerImageVersionAliases, so that we can hide unwanted images from the dropdown list in the portal, or even restrict it only to the internal corporate approved image (this is the actual goal)
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.
Volunteering to Work on This Issue
If you are interested in working on this issue, please leave a comment.
If this would be your first contribution, please review the contribution guide.
Description
The new Sagemaker Studio (non Classic) allows bringing your own JupyterLab container images. According to the CreateDomain API, the StudioWebPortalSettings has a property
HiddenSageMakerImageVersionAliases
, so that we can hide unwanted images from the dropdown list in the portal, or even restrict it only to the internal corporate approved image (this is the actual goal)Affected Resource(s) and/or Data Source(s)
aws_sagemaker_domain
Potential Terraform Configuration
References
https://docs.aws.amazon.com/sagemaker/latest/APIReference/API_CreateDomain.html https://docs.aws.amazon.com/sagemaker/latest/APIReference/API_UserSettings.html#sagemaker-Type-UserSettings-StudioWebPortalSettings
Would you like to implement a fix?
None