Source control and file storage in Amazon SageMaker Unified Studio
Every project in Amazon SageMaker Unified Studio includes S3 shared storage by default. S3 shared storage is active from the moment your project is created and requires no setup. All project members can immediately read, write, and share files.
Repositories are an optional, additive capability. Once a domain administrator configures a Git connection, you can add repositories to your project for version control, branching, and commit-based collaboration. Adding repositories does not replace or disable S3 shared storage. Both coexist in the same project, and you choose per-artifact whether to track it in a repository or not. In this documentation, "artifacts" refers to objects you create in tools (queries, notebooks, ETL jobs, workflows), and "files" refers to their representation in a repository.
Use the following pages based on your needs:
-
To learn about the default storage available in every project, see S3 shared storage.
-
To learn how to use repositories for version control, see Git repositories.
-
If your project uses the previous force-push experience (where every save pushes directly to the remote without commit messages or branching) and you want to migrate, see Legacy experience and migration.
The following table compares the two storage options.
| Feature | S3 shared storage | Repositories |
|---|---|---|
| Setup required | None | Domain administrator must configure a Git connection |
| Version history | No | Yes, full commit history |
| Branching | No | Yes, unlimited branches per repository |
| Collaboration model | Last-write-wins | Branch-based with commit and push |
| Change attribution | No | Yes, per-commit authorship |
| CI/CD integration | No | Yes, through your Git provider |
| Best for | Scratch work, temporary artifacts, quick collaboration | Production workloads, change attribution, safe iteration |
Important
On July 30, 2026, Amazon SageMaker Unified Studio launched a new repository experience that provides per-artifact version control, multi-repository support, and branch-based collaboration. For documentation, see Git repositories. If your project uses the previous force-push based storage model, see Legacy experience and migration for documentation on that experience. For migration steps, see Migrating to the new repository experience.
