Federate entry to Amazon SageMaker Unified Studio with AWS IAM Id Heart and Ping Id

With an identification supplier (IdP), you may handle your person identities outdoors of AWS and provides these exterior person identities permissions to make use of AWS assets in your AWS accounts. Exterior IdPs, reminiscent of Ping Id, can combine with AWS IAM Id Heart to be the supply of reality for Amazon SageMaker Unified Studio. SageMaker Unified Studio additionally helps trusted identification propagation for SQL analytics, together with Amazon Athena and Amazon Redshift.

SageMaker Unified Studio offers an built-in expertise to make use of your information and instruments for analytics and AI. You need to use SageMaker Unified Studio to find your information and put it to work utilizing acquainted AWS analytics and machine studying (ML) companies for mannequin growth, generative AI, huge information processing, and SQL analytics, assisted by Amazon Q Developer. By default, SageMaker domains assist AWS Id and Entry Administration (IAM) person credentials. You can too allow entry to SageMaker domains in SageMaker Unified Studio for customers with single sign-on (SSO) with IAM Id Heart and direct SAML integration with SageMaker Unified Studio.

Customers can entry SageMaker Unified Studio with their current company credentials. With IAM Id Heart, directors can join their current exterior IdPs and proceed to handle customers and teams in these current identification methods, which might then be synchronized with IAM Id Heart utilizing System for Cross-domain Id Administration (SCIM).On this submit, we present find out how to arrange workforce entry with SageMaker Unified Studio utilizing Ping Id as an exterior IdP with IAM Id Heart.

On this submit, we present find out how to arrange workforce entry with SageMaker Unified Studio utilizing Ping Id as an exterior IdP with IAM Id Heart.

Answer overview

We stroll via the next high-level steps to implement this resolution:

1. Allow IAM Id Heart.
2. Create a SageMaker Unified Studio area.
3. Arrange your IdP (for this instance, Ping Id).
4. Join Ping Id and IAM Id Heart.
5. Arrange computerized provisioning of customers and teams in IAM Id Heart.
6. Configure SageMaker Unified Studio SSO person entry.

Stipulations

For this walkthrough, you must have the next stipulations:

• An AWS account with IAM Id Heart enabled. It’s endorsed to make use of an organization-level IAM Id Heart occasion for finest practices and centralized identification administration throughout your AWS group.
• A Ping Id account.
• A browser with community connectivity to Ping Id and SageMaker Unified Studio.

Allow IAM Id Heart

To allow IAM Id Heart, comply with the directions in Allow IAM Id Heart.

Create a SageMaker Unified Studio area

To create a SageMaker Unified Studio area, check with the directions in Create a Amazon SageMaker Unified Studio area – guide setup.

On the SageMaker console, go to the area particulars and duplicate the Amazon Useful resource Identify (ARN) beneath Area ARN. You’ll use this worth while you add your belief coverage and while you join your IAM IdP to your Ping Id occasion.

Arrange your IdP (Ping Id)

On this part, we stroll via the process to arrange your IdP (for this instance, Ping Id).

Create an setting in Ping Id

Full the next steps to create an setting for Ping Id:

1. Log in to your Ping Id account.
2. Select Create Atmosphere.
3. Select Create a Buyer Answer.
4. Within the Tailor your experiences pop-up, select Skip.
   
   

Create a bunch in Ping Id

Full the next steps to create a group in Ping Id:

1. On the Environments web page, select Handle Environments.
2. Within the navigation pane, select Listing, then select Teams.
3. Select the plus signal so as to add a bunch.
4. For Group Identify, enter sagemaker
5. For Description, enter an optionally available description (for instance, Amazon SageMaker Unified Studio).
6. For Inhabitants, select Default.
7. Select Save.
   
   
8. On the Roles tab for the sagemaker group, assign the Atmosphere Admin function to the group.
   
   

Create a person in Ping Id

Full the next steps to create a person:

1. Within the navigation pane, select Listing, then select Customers.
2. Select the plus signal to create a person.
3. Present values for Given identify, Household identify, Username, and Electronic mail.
4. For Password, select First time password.
5. Select Save.

You possibly can add extra customers as wanted.

Assign group to person

Full the next steps to assign your group to your person:

1. Within the navigation pane, select Listing, then select Teams.
2. Select the sagemaker group you created.
3. On the Customers tab, select the plus signal so as to add a person.
4. Add the person you created.

Join Ping Id and IAM Id Heart

To configure the combination between Ping Id and IAM Id Heart, you want entry to each administration consoles. Though Ping Id’s utility catalog contains IAM Id Heart, we suggest configuring a regular SAML utility for larger management over settings and attribute mappings.

Full the next steps:

1. Go to the Ping Id setting you created and select Functions within the navigation pane.
2. Select the plus signal so as to add an utility:
   1. For Utility identify, enter a reputation (for this instance, we use unifiedstudio).
   2. For Description, enter an optionally available description.
   3. For Utility Sort, select SAML Utility.
   4. Select Configure.

   

3. Sign up to the IAM Id Heart console as a person with administrative privileges.
4. Within the navigation pane, select Settings to replace your settings:
   1. On the Id supply tab, select Change identification supply on the Actions dropdown menu.
      
      
   2. For Select identification supply, choose Exterior identification supplier, then select Subsequent.

      

   3. Within the Service supplier metadata part, select Obtain metadata file to obtain the IAM Id Heart metadata file.

      You’ll use this service supplier metadata file within the subsequent step while you join Ping Id with IAM Id Heart.

   

5. Return to the Ping Id console and the SAML utility web page.
6. Within the SAML Configuration part, choose Import Metadata, add the metadata file you downloaded, then select Save.

   

7. On the Overview tab of the appliance web page, select Obtain Metadata beneath Connection particulars to obtain the Ping Id IdP metadata.
   
   You’ll use this for the SAML configuration in IAM Id Heart to arrange Ping Id as an IdP within the subsequent step.

   

8. Return to the IAM Id Heart console and proceed configuring your identification supply:
   1. Within the Id supplier metadata part, select Select file beneath IdP SAML metadata, add the metadata file you downloaded from Ping Id, then select Subsequent.

      

   2. Select Settle for to simply accept the disclaimer.
   3. Select Change identification supply.
9. Return to the Ping Id console to finish the SAML configuration.
10. On the Configuration tab, select the edit icon to replace the configuration:
    1. For Signal, select Signal Assertion & Response.
    2. For Topic Identify ID, enter urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress.
    3. For Assertion Validity Period, enter 300.
    4. Go away the remaining values as default.

    

11. On the Attributes tab, select the edit icon.
12. Select +Add so as to add two attribute mappings:
    1. Map the attribute saml-subject to Username, and depart Identify format as default.
    2. Map the attribute https://aws.amazon.com/SAML/Attributes/PrincipalTag:Electronic mail to Electronic mail Handle, and set Identify format to Unspecified.
    3. Select Save.

    

13. On the PingOne Insurance policies tab, choose Single Issue, then select Save.
    
    This submit makes use of single-factor authentication for demonstration functions solely. In your environments, comply with your group’s safety requirements and governance framework.

    

14. On the Entry tab, seek for the sagemaker group beneath Group Membership Coverage, and assign the unifiedstudio SAML utility to the group.
15. Allow the appliance.
    
    

Arrange computerized provisioning of customers and teams from Ping Id into IAM Id Heart

To configure the automated provisioning of customers and teams between Ping Id and IAM Id Heart via SCIM, you should have entry to each administration consoles. Full the next steps:

1. On the IAM Id Heart console, select Settings within the navigation pane.
2. Within the Automated provisioning part, select Allow.
   
   

   This allows computerized provisioning in IAM Id Heart and shows the mandatory SCIM endpoint and entry token data.

3. Within the Inbound computerized provisioning dialog field, copy the values for SCIM endpoint and Entry token, then select Shut.
   
   You’ll use these values to configure provisioning in Ping Id within the subsequent step.

   

   This completes the setup course of in IAM Id Heart.

4. Log in to the Ping Id console.
5. Within the navigation pane, select Integrations, then select Provisioning.
6. Select the plus signal so as to add a brand new connection.
   
   
7. For Select a connection kind, select Choose subsequent to Id Retailer.
   
   
8. Present a reputation (for this instance, we use Identitycenter) and an optionally available description, then select Subsequent.
   
   
9. Below Configuration Authentication, present the next configuration:
   1. For SCIM BASE URL, enter the SCIM endpoint from IAM Id Heart.
   2. For Authentication Methodology, select OAuth 2 Bearer Token.
   3. For Oauth Entry Token, enter the entry token from IAM Id Heart.
   4. For Auth Sort Header, select Bearer (default possibility).
   5. Select Take a look at Connection to validate the connection between Ping Id and IAM Id Heart, then select Subsequent.

   

10. Below Configuration Choice, present the next configuration:
    1. For Consumer Filter Expression, enter userName Eq “%s”.
    2. For Group Membership Dealing with, choose Merge.
    3. Go away the remaining settings as default and select Save.

    

11. On the Provisioning tab, select the plus signal, then select New Rule to create a rule for the SCIM connection.
    
    
12. Enter a reputation (for this instance, unifiedstudio) and an optionally available description, then select Create Rule.
13. Below the newly created rule, select the plus signal subsequent to Obtainable Connections so as to add the connection identitycenter, then select Save.
14. Edit the person filter:
    1. For Attribute, select Enabled.
    2. For Operator, select Equals.
    3. For Worth, select true.
    4. Select Save.

    

15. Select the edit icon subsequent to Attribute Mapping and set the attribute mappings as proven within the following screenshot:
    1. Delete the Major Telephone attribute mapping as a result of it’s optionally available in AWS. Leaving this area clean could cause Ping Id’s SCIM connector to generate errors throughout person provisioning.
    2. Add a brand new attribute known as Username beneath PingOne Listing after which map to displayName beneath Identitycenter.

    

16. Below Group Provisioning, select the sagemaker group if you wish to sync all sagemaker group customers with auto provisioning.
    1. Within the pop-up, choose I perceive and wish to proceed, then select Save.

    

    

17. On the Provisioning web page, select the Connections tab.
18. Allow the SCIM connection Identitycenter and rule unifiedstudio.

    

    

This completes the SCIM setup course of between Ping Id and IAM Id Heart.

Configure SageMaker Unified Studio SSO person entry

Full the next steps to configure SSO person entry to SageMaker Unified Studio to your SageMaker area:

1. On the SageMaker console, select Domains within the navigation pane.
2. Select the area for which you wish to configure SAML person entry.
3. On the area particulars web page, you will discover the SSO configuration in two places:
   1. From the principle area view, select Configure subsequent to Configure SSO person entry.
   2. Alternatively, scroll right down to the Consumer administration tab and select Configure SSO person entry.

   

4. On the Select person authentication methodology web page, choose IAM Id Heart, then select Subsequent.
   
   
5. For Select person and group project methodology, select from the next choices, then select Subsequent:
   1. Require assignments: Customers and teams have to be explicitly added to the area to achieve entry. This offers extra granular management over who can entry the area.
   2. Don’t require assignments: All licensed Ping Id customers and teams can entry this area if they’ve been assigned to the SAML utility in Ping Id.

   For both possibility, customers or teams should have entry to the Ping Id SAML utility (unifiedstudio on this instance) to authenticate efficiently.

   

6. On the Evaluation and save web page, evaluate your decisions and select Save. These settings can’t be modified after you save them.
   
   
7. When you’ve chosen to require assignments, use the Add customers and teams part so as to add SAML customers and teams to your area.
   
   

Now, customers will be capable of entry SageMaker Unified Studio utilizing the area URL with their SSO credentials.

You possibly can discover completely different initiatives to your customers and assign these initiatives primarily based in your IdP person teams for fine-grained entry controls. For instance, you may create completely different SAML person teams primarily based on their job perform in Ping Id, then assign these Ping Id teams to the unifiedstudio SAML utility in Ping Id, after which assign these Ping Id SAML teams to their respective undertaking profiles in SageMaker Unified Studio. To assign undertaking profiles for his or her respective teams, select the Challenge profiles tab and select your undertaking profile. On the Licensed customers and teams web page, select Add, then select SSO teams. Select Add customers and teams button to finish the undertaking profile project.

Validate entry with Ping Id customers

Full the next steps to validate entry:

1. On the SageMaker area particulars web page, select the hyperlink for the SageMaker Unified Studio URL.
   
   
2. Log in along with your person credentials.
   
   After profitable login, you’ll be redirected to the SageMaker Unified Studio house web page. Right here, you may discover completely different initiatives to your customers and assign these initiatives primarily based in your SAML person teams for fine-grained entry management.

   

3. To assign an authorization coverage, these Govern after which Area models.
4. Select your SageMaker area, then select an appropriate authorization coverage. For this instance, we select Challenge creation coverage.
   
   
5. Select Add coverage grant to assign person teams or customers to their respective undertaking profiles.
   
   

You could have efficiently federated SageMaker Unified Studio with Ping Id as an IdP with IAM Id Heart. You possibly can hook up with SageMaker Unified Studio through the use of your Ping Id credentials.

Clear up

After you take a look at out this resolution, bear in mind to delete the assets you created to keep away from incurring future expenses. For directions to delete your SageMaker Unified Studio area, check with Delete domains. If you wish to delete your Ping Id account, attain out to Ping Id for help.

Conclusion

On this submit, we demonstrated find out how to arrange Ping Id as an IdP over SAML authentication for SageMaker Unified Studio entry via IAM Id Heart federation. To be taught extra, check with the Amazon SageMaker Unified Studio Consumer Information, which offers steerage on find out how to construct information and AI purposes utilizing SageMaker.

Concerning the authors