Feature comparison matrix
The following table provides a comprehensive comparison of key features between Git-based and S3 storage options to help you make informed decisions when configuring storage for your Amazon SageMaker Unified Studio projects.
| Feature | Git-based projects | S3-based projects |
|---|---|---|
| Audit trail | Full Git commit history tracks all changes including author information, timestamps, and detailed commit messages. Complete audit trail is maintained in the Git repository. | No systematic tracking of file changes or user attribution. Basic file modification timestamps are available, but no detailed change history or commit messages are maintained. |
| Version history | Complete Git versioning with full commit history, branching, and merging capabilities. Version history is accessible through Git commands in JupyterLab or through the Git provider's web interface. | S3 bucket versioning must be enabled from the S3 console by administrators. When enabled, version history will be available from the S3 console, allowing you to view and restore previous versions of files. |
| Shared storage | All project members work through same Git repository. Files must be "Saved to project" or pushed to the repo | Shared folder (shared_files/) accessible by all project members. Direct file sharing. |
| Cross-project sharing | Multiple SMUS projects can connect to the same Git repository, enabling code and resource sharing across different project teams. | Each project has its own dedicated S3 storage location. Files cannot be directly shared between projects without manual copying. |
| Regional availability | Limited by availability of CodeConnections service. | Available in all regions where S3 is available. |
| Change documentation | All changes are documented through Git commit messages that developers write when saving changes. Provides detailed context for each modification. | No built-in mechanism for documenting changes. File modifications occur without requiring or capturing change descriptions. |
| Setup complexity | Requires Git repository configuration | Minimal configuration required |
