Amazon Web Services announced on October 9, 2026, that Amazon SageMaker Unified Studio now supports custom Tooling blueprints. The new feature allows domain administrators to use their own AWS CloudFormation templates to define project environments.
Custom Project Environments
According to AWS, domain administrators can now define the foundation of every project by using their own AWS CloudFormation templates. This enables organizations to tailor project environments to meet specific requirements, such as compliance with company naming standards for IAM role names or custom permissions boundaries instead of AWS managed policies.
Templates can include any CloudFormation-supported resource, such as AWS Lake Formation grants, Amazon Athena workgroups, or VPC security groups, and work across multiple AWS accounts and Regions without per-project edits.
Template Validation and Deployment
Administrators start by authoring a CloudFormation template and registering it as a custom Tooling blueprint. The service validates the template at registration and again after each project deployment to confirm that required resources exist before any team member uses the project.
AWS stated that the service automatically populates reserved template parameters, such as the project ID and domain ID, at deployment time so administrators can define the template once and apply it everywhere. The feature is available in all AWS Regions where Amazon SageMaker Unified Studio is available.
Key facts and where they come from
- Amazon SageMaker Unified Studio now supports custom Tooling blueprints using AWS CloudFormation templates.
Amazon SageMaker Unified Studio now supports custom Tooling blueprints, giving domain administrators the ability to define the foundation of every project by using their own AWS CloudFormation templates.
- Administrators can tailor project environments for IAM role names and custom permissions boundaries.
Administrators can tailor project environments to meet organization-specific requirements, such as IAM role names that comply with company naming standards or custom permissions boundaries instead of AWS managed policies.
- The service validates templates at registration and after each project deployment.
The service validates the template at registration and again after each project deployment, confirming that the required resources exist before any team member uses the project.