Define SageMaker Unified Studio projects with your own CloudFormation!
Hi, it's Shii-chan! Here's a good update for SageMaker Unified Studio administrators.
AWS What's New
aws.amazon.com
What was announced?
AWS What's New announced that Amazon SageMaker Unified Studio now supports custom Tooling blueprints. Domain administrators can define the foundation of every project using their own AWS CloudFormation templates.
What changes
You can tailor project environments to your organization's requirements. For example, IAM role names can follow company naming standards, or you can use custom permissions boundaries instead of AWS managed policies.
Dive Deep
How it works:
- An administrator writes a CloudFormation template describing the project environment and registers it as a custom Tooling blueprint
- The service validates the template at registration and again after each project deployment, confirming the required resources exist before any team member uses the project
- Templates can include any CloudFormation-supported resource, such as AWS Lake Formation grants, Amazon Athena workgroups, or VPC security groups
- A template works across multiple AWS accounts and Regions without per-project edits
- At deployment, reserved template parameters such as the project ID and domain ID are filled in automatically, so you define the template once and apply it everywhere
It's available in all AWS Regions where SageMaker Unified Studio is available. See "Custom blueprints as Tooling" in the administrator guide for details.
Wrap-up
- Define project foundations with your own CloudFormation templates
- Match IAM role names and permissions boundaries to your standards
- Templates are validated at registration and after deployment
- Works across accounts and Regions without per-project edits
It's a good fit for admins of SageMaker Unified Studio in organizations with strict naming and permission rules.
