SageMaker Unified Studio CI/CD now supports notebook promotion and AI-generated manifests!
Hi, I'm Shii-chan! Today I found some great news for teams working with SageMaker Unified Studio, so let me walk you through it!
AWS What's NewWhat was announced?
This comes from AWS What's New. Amazon SageMaker Unified Studio's CI/CD toolkit just got two new capabilities:
- AI-assisted manifest generation via a new agent skill called generate-bundle-manifest
- Native notebook promotion support
Both are additions to the open-source CI/CD toolkit, aimed at helping teams move projects from development to production more smoothly.
The story so far
This CI/CD toolkit already let teams promote code, workflows, and catalog assets across development, test, and production accounts using bundle / deploy / destroy / dry-run commands. But native SageMaker Unified Studio Notebooks weren't part of that promotion flow, and building deployment manifests for each environment wasn't automated either.
What changes
These two additions cut down the effort of getting a project into production.
- AI-assisted manifest authoring: the generate-bundle-manifest skill inspects a project's connections, storage, and workflows to produce a ready-to-use deployment manifest
- Notebooks join the promotion flow: native notebooks can now be promoted across environments alongside code, workflows, and catalog assets
- Run history is preserved: notebooks are created on first deployment and updated on later ones, so run history survives across releases
- Fits right into existing commands: it works with the current bundle / deploy / destroy / dry-run commands, so there's no need to rebuild your pipeline
Dive Deep
The generate-bundle-manifest skill doesn't just spit out a template — it bakes in best practices:
- Applies least-privilege IAM guidance
- Substitutes environment variables in place of hardcoded resource identifiers
- Sets safe defaults, such as opt-in catalog handling
You can import this skill into your own agents, which is handy for standardizing how your team packages and promotes SageMaker Unified Studio projects.
Notebook promotion uses an in-place synchronization model: it creates a notebook on first deployment and updates it on subsequent ones. You can promote every notebook in a project or select specific ones by ID. There's also a dry-run mode that validates S3 connectivity, IAM permissions, and notebook counts before you actually deploy, so you can catch issues before they hit production.
This toolkit is open source and available in every AWS region where SageMaker Unified Studio operates. The code lives in the CICD-for-SageMakerUnifiedStudio GitHub repository.
Wrap-up
- The generate-bundle-manifest skill auto-generates deployment manifests from a project's connections, storage, and workflows, applying least-privilege IAM and environment-variable best practices automatically
- Native notebooks can now be promoted across environments just like code, workflows, and catalog assets
- Notebook promotion uses in-place sync (create on first deploy, update afterward) to preserve run history, and you can target all notebooks or specific ones by ID
- Dry-run mode checks S3 connectivity, IAM permissions, and notebook counts before deployment
- It integrates with the existing bundle / deploy / destroy / dry-run commands, is open source, and works in all regions
This is a great fit for data teams running SageMaker Unified Studio projects across multiple environments, and for DevOps folks looking to tighten up their CI/CD pipeline!