Amazon SageMaker Unified Studio is in preview release and is subject to change.
Git connections in Amazon SageMaker Unified Studio
Git connections enable you to check in and check out files, and manage your code repository. When you create an Amazon SageMaker platform domain, a default git connection to CodeCommit is provided for you to manage your code. You can also create and enable new 3P Git connections to GitHub, GitHub Enterprise Server, GitLab, and GitLab Self-Managed.
You can use the following procedures to create 3P Git connections.
Topics
Github connections
Complete the following procedure to create a 3P Git connection to GitHub:
-
Navigate to the Amazon SageMaker management console at https://console.aws.amazon.com/datazone
and use the region selector in the top navigation bar to choose the appropriate AWS Region. -
Choose View domains and then choose the domain where you want to add a 3P Git connection to GitHub.
-
On the domain's details page, choose the Connections tab.
-
Expand the Create Git connection drop-down menu and then choose Github.
-
In the Create a connection window, in the Connection name field, specify the name of the connection. (Optional - enter in any AWS tags you want to add to the connection and then choose Connect to Github.
-
Enter in your GitHub credentials if you are prompted to provide them.
-
Optional - for the app installation, either choose an AWS application to connect to Amazon SageMaker Unified Studio that you previously installed, or install a new application.
-
If you have installed an AWS application, search for and select that application.
-
If you do not have an AWS application, choose Install a new app. A popup window appears.
-
Select the account you want to install the application and establish a connection to.
-
Select whether you want the app to connect to All repositories or Only select repositories.
-
Choose Install.
-
-
-
Choose Connect.
-
Close the popup window and refresh the Connections tab. The connection appears in the list with a connection status of Available. You then need to enable the connection for project access in the Amazon SageMaker Unified Studio.
Github Enterprise server connections
Complete the following procedure to create a 3P Git connection to GitHub Enterprise Server:
-
Navigate to the Amazon SageMaker management console at https://console.aws.amazon.com/datazone
and use the region selector in the top navigation bar to choose the appropriate AWS Region. -
Choose View domains and then choose the domain where you want to add a 3P Git connection to GitHub Enterprise Server.
-
On the domain's details page, choose the Connections tab.
-
Expand the Create Git connection drop-down menu and then choose GitHub Enterprise.
-
In Connection name, provide a name for the connection.
-
In URL, specify the URL of your GitHub Enterprise Server instance.
-
If your GitHub Enterprise Server instance is only available in a VPC, choose Use a VPC and then specify the VPC ID.
-
(Optional) Under TLS certificate, specify your TLS certificate.
-
(Optional) Specify any AWS tags you want to add to the connection.
-
Choose Connect to GitHub Enterprise Server. This brings you to the connection details page, and the status of the connection is Pending. You then need to update the pending connection to make it active.
Complete the following procedure to update a pending 3P Git connection to GitHub Enterprise Server:
-
Navigate to the Amazon SageMaker management console at https://console.aws.amazon.com/datazone
and use the region selector in the top navigation bar to choose the appropriate AWS Region. -
Choose View domains and then choose the domain where you want to add a 3P Git connection to GitHub.
-
On the domain's details page, choose the Connections tab and then choose the Git connection that you want to update.
-
Choose Update pending connection. A new popup window appears inviting you to enter information for your GitHub Enterprise Server.
-
If you have installed an AWS application to connect to Amazon SageMaker Unified Studio, search for it and select that application and choose Connect. If you do not have an AWS application to connect to Amazon SageMaker Unified Studio, choose Install a new application.
-
In the pop up window, choose Leave page. This takes you to the new application installation.
-
Select the organization in which you want to install the application and establish a connection.
-
Select whether you want the app to connect to All repositories or Only select repositories.
-
Choose Install.
This brings you to the connection details page, and the status of the connection changes to Available. You then need to enable the connection for project access in the Amazon SageMaker Unified Studio.
GitLab connections
Complete the following procedure to create a 3P Git connection to GitLab:
-
Navigate to the Amazon SageMaker management console at https://console.aws.amazon.com/datazone
and use the region selector in the top navigation bar to choose the appropriate AWS Region. -
Choose View domains and then choose the domain where you want to add a 3P Git connection to GitLab.
-
On the domain's details page, choose the Connections tab.
-
Expand the Create Git connection drop-down menu and then choose GitLab.
-
In Connection name, provide a name for the connection, optionally, enter in any AWS tags you want to add to the connection, and then choose Connect to GitLab.
-
Enter in your GitLab credentials when you are prompted to provide them. Once authenticated, choose Authorize AWS connector for GitLab.
-
On the Connect to GitLab page, choose Connect.
-
Close the popup window and refresh the Connections tab. The new GitLab connection appears in the list with a connection status of Available. You must then enable this connection for project access in the Amazon SageMaker Unified Studio.
GitLab self-managed connections
Complete the following procedure to create a 3P Git connection to GitLab Self-Managed:
-
Navigate to the Amazon SageMaker management console at https://console.aws.amazon.com/datazone
and use the region selector in the top navigation bar to choose the appropriate AWS Region. -
Choose View domains and then choose the domain where you want to add a 3P Git connection to GitLab self-managed.
-
On the domain's details page, choose the Connections tab.
-
Expand the Create Git connection drop-down menu and then choose GitLab self-managed.
-
On the Connect to GitLab self-managed page, in Connection name, specify the name for the connection, and in the URL, specify the endpoint of the server to connect to, and then choose Connect to GitLab self-managed. This brings you to the connection details page, and the status of the connection is Pending. You then need to update the pending connection to make it active.
Complete the following procedure to update a pending 3P Git connection to GitLab self-managed:
-
Navigate to the Amazon SageMaker management console at https://console.aws.amazon.com/datazone
and use the region selector in the top navigation bar to choose the appropriate AWS Region. -
Choose View domains and then choose the domain where you want to update your pending connection.
-
On the domain's details page, choose the Connections tab and then choose the Git connection that you want to update.
-
Choose Update pending connection. A new popup window appears inviting you to enter information for your GitLab self-managed.
-
If you have installed an AWS application to connect to Amazon SageMaker Unified Studio, search for it and select that application and choose Connect. If you do not have an AWS application to connect to Amazon SageMaker Unified Studio, choose Install a new application.
-
In the pop up window, choose Leave page. This takes you to the new application installation.
-
Select the organization in which you want to install the application and establish a connection.
-
Select whether you want the app to connect to All repositories or Only select repositories.
-
Choose Install.
Enable connections for project access
After a 3P Git connection is created and updated to become available, you can enable it for project members to use in your domain. Complete the following procedure to enable project access for a 3P Git connection:
-
Navigate to the Amazon SageMaker management console at https://console.aws.amazon.com/datazone
and use the region selector in the top navigation bar to choose the appropriate AWS Region. -
Choose View domains and then choose the domain where you want to enable your connections for project members to use.
-
On the domain's details page, choose the Connections tab.
-
Choose the connection that you want to enable, and then choose Enable. A popup window appears so that you can confirm the decision.
-
Choose Enable. When you refresh the page, the connection then appears as Enabled. This means that project members have access to the connection and can use it in projects within that domain.
Note
All tagged connections will be accessible from all domains in the account and all projects in the associated accounts.