Sagemaker Unified Studio set-up using CDK and SDK - Lack of documentation

I understand your frustration with the lack of documentation for provisioning Amazon SageMaker Unified Studio using CDK and SDK. Unfortunately, as of now, there isn't specific documentation or direct support for provisioning SageMaker Unified Studio through CDK or SDK.

SageMaker Unified Studio is a relatively new offering from AWS, currently in preview. As such, the tooling and documentation for infrastructure-as-code solutions like CDK are still catching up.

For the time being, the best approach would be to use the existing SageMaker constructs in CDK, which are primarily L1 constructs that map directly to CloudFormation resources. These can be found in the 'aws-cdk-lib/aws-sagemaker' module. However, these constructs may not fully cover all the features specific to SageMaker Unified Studio.

It's worth noting that there are no official hand-written (L2) constructs for SageMaker in CDK yet. You might want to keep an eye on the AWS CDK GitHub repository and the official AWS documentation for updates as SageMaker Unified Studio moves out of preview and becomes generally available.

In the meantime, you could consider using the AWS Management Console for setting up SageMaker Unified Studio, as the setup process involves several steps including configuring AWS IAM Identity Center, setting up necessary VPC and IAM roles, creating a SageMaker domain, and enabling certain features like Amazon Q Developer Pro.

As the service matures and moves out of preview, it's likely that more comprehensive documentation and support for infrastructure-as-code solutions will become available. Until then, you may need to rely on a combination of existing SageMaker CDK constructs and manual configuration through the console or CLI.
Sources
aws-cdk-lib.aws_sagemaker module · AWS CDK
sagemaker unified studio | AWS re:Post
Introducing the next generation of Amazon SageMaker: The center for all your data, analytics, and AI | AWS News Blog