Configure seamless single sign-on with SQL analytics in Amazon SageMaker Unified Studio

October 18, 2025

76

Amazon SageMaker Unified Studio offers a unified expertise for utilizing information, analytics, and AI capabilities. SageMaker Unified Studio now helps trusted id propagation (TIP) for SQL workloads, enabling fine-grained information entry management based mostly on particular person consumer identities. Organizations can use this integration to handle information permissions via AWS Lake Formation whereas utilizing their present single sign-on (SSO) infrastructure.

Organizations already utilizing Amazon Redshift with TIP can lengthen their present Lake Formation permissions to SageMaker Unified Studio. Customers merely log in via SSO and entry their approved information utilizing the SQL editor, sustaining constant safety controls throughout their analytics setting.

This publish demonstrates methods to configure SageMaker Unified Studio with SSO, arrange initiatives and consumer onboarding, and entry information securely utilizing built-in analytics instruments.

Resolution overview

For our use case, a retail company is planning to implement gross sales analytics to establish gross sales patterns and product classes which can be doing properly. This may assist the gross sales group enhance on gross sales planning with focused promotions and assist the finance group plan budgeting with higher stock administration. The company shops a buyer desk in an Amazon Easy Storage Service (Amazon S3) information lake and a store_sales desk in a Redshift cluster.

The company makes use of SageMaker Unified Studio because the UI, with customers onboarded from their id supplier (IdP) to AWS IAM Id Middle with TIP. Amazon SageMaker Lakehouse centralizes information from Amazon S3 and Amazon Redshift, and Lake Formation offers fine-grained entry management based mostly on consumer id. For our instance use case, we discover two completely different customers. The next desk summarizes their roles, the instruments they use, and their information entry.

Person	Group	Device	Information Entry
Ethan (Information Analyst)	Gross sales	Amazon Athena for interactive SQL evaluation	Non-sensitive buyer information (`id`, `c_country`, `birth_year`) and `store_sales` full desk entry
Frank (BI Analyst)	Finance	Amazon Redshift for reviews and visualization	US buyer information (`c_country='US'`)

The next diagram illustrates the answer structure.

SageMaker Unified Studio with IAM Id Middle simplifies the consumer journey from authentication to information evaluation. The workflow consists of the next steps:

Customers check in with organizational SSO credentials via their IdP and are redirected to SageMaker Unified Studio.
Customers configure IAM Id Middle authentication for Amazon Redshift, linking id administration with information entry.
Customers entry the question editor for Amazon Redshift or SageMaker Lakehouse, triggering IAM Id Middle federation to generate session and entry tokens.
SageMaker Unified Studio retrieves consumer authorization particulars and group membership utilizing the session token.
Customers are authenticated as IAM Id Middle customers, able to discover and analyze information utilizing Amazon Redshift and Amazon Athena.

To implement our answer, we stroll via the next high-level steps:

Arrange SageMaker Lakehouse assets.
Create a SageMaker Unified Studio area with SSO and TIP enabled.
Configure Amazon Redshift for TIP and validate entry.
Validate information entry utilizing Amazon Athena.

Stipulations

Earlier than you start implementing the answer, you could have the next in place:

When you don’t have an AWS account, you possibly can join for one.
We offer utility scripts to assist arrange numerous sections of the publish. To make use of them:

Proper-click this hyperlink and save the utility scripts zip file.
Unzip the file to a terminal that has the AWS Command Line Interface (AWS CLI) configured. It’s also possible to use AWS CloudShell.
Run the scripts solely when prompted within the related sections.

Notice: The utility scripts are configured for
us-east-1 area. When you choose one other area, edit the area within the scripts earlier than operating them.

To deploy the infrastructure, right-click this hyperlink and choose ‘Save Hyperlink As’ to put it aside as sagemaker-unified-studio-infrastructure.yaml. Then add the file when creating a brand new stack within the AWS CloudFormation console, which can create the next assets:
1. An S3 bucket to carry the shopper information used on this publish.
2. An AWS Id and Entry Administration (IAM) function referred to as DataTransferRole with permissions as outlined in Stipulations for managing Amazon Redshift namespaces within the AWS Glue Information Catalog.
3. An IAM function referred to as IAMIDCRedshiftRole, which will probably be used later to arrange the IAM Id Middle Redshift utility.
4. An IAM function referred to as LakeFormationRegistrationRole, following the directions in Necessities for roles used to register places, and vital IAM insurance policies.
When you don’t have a Lake Formation consumer, you possibly can create one. For this publish, we use an admin consumer. For directions, see Create an information lake administrator.
If IAM Id Middle just isn’t enabled, discuss with Enabling AWS IAM Id Middle for directions to allow it.
1. If it is advisable to migrate present Redshift customers and teams, use the IAM Id Middle Redshift migration utility.
2. For a fast option to check the characteristic and familiarize your self with the method, we offer a script to generate mock customers and teams. Run the setup-idc.sh script, which is supplied in Step 2, to create check customers and teams in IAM Id Middle for demonstration functions.
Combine IAM Id Middle with Lake Formation. For directions, see Connecting Lake Formation with IAM Id Middle.
Register the S3 bucket as an information lake location:
1. On the Lake Formation console, select Information lake places within the navigation pane.
2. Select Register location.
3. For the function, use LakeFormationRegistrationRole.
Create an IAM Id Middle Redshift utility, as detailed in our earlier publish:
1. On the Amazon Redshift console, select IAM Id Middle connections within the navigation pane and select Create utility.
2. For each the show title and utility title, enter redshift-idc-app.
3. Set the IdP namespace to awsidc.
4. Select IAMIDCRedshiftRole because the IAM function.
5. Select Subsequent to create the applying.
6. Be aware of the applying Amazon Useful resource Identify (ARN) to make use of in subsequent steps. The ARN format is arn:aws:sso:::utility/ssoins-/apl-.
When you don’t have present Redshift tables to work with, run the script setup-producer-redshift.sh, which is supplied in Step 2, to create a producer namespace and workgroup, arrange a pattern gross sales database, and generate vital tables with check information.
The publish additionally makes use of simulated buyer information saved within the AWS Glue Information Catalog. To arrange this information and configure the mandatory Lake Formation permissions, run the setup-glue-tables-and-access.sh script supplied in Step 2.

Arrange SageMaker Lakehouse assets

On this part, we configure the foundational lakehouse assets required for SageMaker to entry and analyze information throughout a number of storage programs. We’ll register the Redshift occasion to the AWS Glue Information Catalog to make warehouse information discoverable and set up Lake Formation permissions on lakehouse assets for consumer identities to make sure safe, ruled entry to each information lake and information warehouse assets from inside SageMaker environments.

Register Redshift occasion to the Information Catalog

On this step, we use the store_sales information, which we created earlier utilizing the setup-producer-redshift.sh script. You’ll be able to register complete clusters to the Information Catalog and create catalogs managed by AWS Glue. To register a cluster to the Information Catalog, full the next steps:

On the Lake Formation console, select Administrative roles and duties within the navigation pane.
Beneath Information lake directors, select Add.
Select Learn-only administrator, then select AWSServiceRoleForRedshift.
On the Amazon Redshift console, open your namespace.
On the Actions dropdown menu, selected Register with AWS Glue Information Catalog, then select Register.
Check in to the Lake Formation console as the info lake administrator and select Catalogs within the navigation pane.
Beneath Pending catalog invites, choose the namespace and settle for the invitation by selecting Approve and create catalog.
Present the title for the catalog as salescatalog.
Choose Entry this catalog from Apache Iceberg suitable engines, select DataTransferRole for the IAM function, then select Subsequent.
Select Add permissions and select the admin IAM function underneath IAM customers and roles.
Choose Tremendous consumer for catalog permissions and select Add.
Select Subsequent.
Select Create catalog.

Arrange Lake Formation permission on lakehouse assets for consumer identities

On this part, we configure Lake Formation permissions to allow safe entry to lakehouse assets for federated consumer identities. Lake Formation offers fine-grained entry management that works seamlessly with IAM Id Middle, permitting you to handle permissions centrally whereas sustaining safety boundaries.

We’ll concentrate on granting database entry to IAM Id Middle teams in Lake Formation and setting table-level permissions for federated Redshift catalog tables. These permissions kind the safety basis for our federated question structure, enabling customers to seamlessly entry each S3 information lake and Redshift information warehouse assets via a unified interface.

Grant database entry to IAM Id Middle teams in Lake Formation

After you share your Redshift catalog with the Information Catalog and combine with Lake Formation, you could grant acceptable database entry. Observe these steps to arrange permissions in your information lake assets for company identities:

On the Lake Formation console, underneath Permissions within the navigation pane, select Information permissions.
Select Grant.
Choose Principals for Principal sort.
Beneath Principals, choose IAM Id Middle and select Add.
Within the pop-up window, if that is your first time assigning customers and teams, select Get began.
Seek for and choose the IAM Id Middle teams awssso-sales and awssso-finance.
Select Assign.
Beneath LF-Tags or catalog assets, select Named Information Catalog assets.
1. Select :salescatalog/dev for Catalogs.
2. Select sales_schema for Database.
Beneath Database permissions, choose Describe.
Select Grant to use the permissions.

Grant table-level permissions for federated Redshift catalog tables

Full the next steps to grant desk permissions to the IAM Id Middle teams:

On the Lake Formation console, underneath Permissions within the navigation pane, select Information permissions.
Select Grant.
Choose Principals for Principal sort.
Beneath Principals, choose IAM Id Middle and select Add.
Within the pop-up window, if that is your first time assigning customers and teams, select Get began.
Seek for and choose the IAM Id Middle group awssso-sales.
Select Assign.
Beneath LF-Tags or catalog assets, select Named Information Catalog assets.
1. Select :salescatalog/dev for Catalogs.
2. Select sales_schema for Database.
3. Select store_sales for Desk.
Choose Choose and Describe for Desk permissions.
Select Grant to use the permissions.

Create a SageMaker Unified Studio area with SSO and TIP enabled

For directions to create a SageMaker Unified Studio area, discuss with Create an Amazon SageMaker Unified Studio area – fast setup. As a result of your IAM Id Middle integration is already full, you possibly can specify an IAM Id Middle consumer within the area configuration settings.

Allow TIP in SageMaker Unified Studio

Full the next steps to allow TIP in SageMaker Unified Studio:

On the SageMaker console, use the AWS Area selector within the high navigation bar to decide on the suitable Area.
Select View domains and select the area’s title from the listing.
On the area’s particulars web page, on the Venture profiles tab, select a undertaking profile, for instance, SQL analytics.
Choose SQL analytics and select Edit.
Within the Blueprint parameters part, choose enableTrustedIdentityPropagationPermissions and select Edit.
Replace the worth as true.
To implement authorization-based on TIP, the SageMaker Unified Studio admin could make this parameter non-editable.
Select Save.

Allow consumer entry for SageMaker Unified Studio area

Full the next steps to allow consumer entry for the SageMaker Unified Studio area:

Open the SageMaker console within the acceptable Area and select Domains within the navigation pane.
Select an present SageMaker Unified Studio area the place you wish to add SSO consumer entry.
On the area’s particulars web page, on the Person administration tab, within the Customers part, select Add and Add SSO customers and teams.
Select the consumer (for this publish, we add the consumer Frank) from the dropdown listing and select Add customers and teams.

Add undertaking members

SageMaker Unified Studio initiatives facilitate group collaboration for various enterprise initiatives. Because the undertaking proprietor, Ethan now can add Frank as a group member to allow their collaboration. So as to add members to an present undertaking, full the next steps:

Check in to the SageMaker Unified Studio console utilizing the SSO credentials of who owns the undertaking (for this publish, Ethan).
Select Choose a undertaking.
Select the undertaking you wish to edit.
On the Venture overview web page, increase Actions and select Handle members.
Select Add members.
Enter the title of the consumer or group you wish to add (for this publish, we add Frank).
Choose Contributor if you wish to add the undertaking member as a contributor.
(Elective) Repeat these steps so as to add extra undertaking members. You’ll be able to add as much as eight undertaking members at a time.
Select Add members.

Create a SQL analytics undertaking in Unified Studio

On this step, we federate into SageMaker Unified Studio and create a undertaking utilizing SQL analytics. Full the next steps:

Federate into SageMaker Unified Studio utilizing your IAM Id Middle credentials:
1. On the SageMaker console, select Domains within the navigation pane.
2. Copy the SageMaker Unified Studio URL to your area and enter it into a brand new browser window.
3. Select Check in with SSO.
4. A browser pop-up will redirect you to your most well-liked IdP login web page, the place you enter your IdP credentials.
5. If authentication if profitable, you may be redirected to SageMaker Unified Studio.
After logging in, select Create undertaking.
Enter a reputation to your undertaking. This undertaking title is closing and may’t be modified later.
(Elective) Enter an outline to your undertaking. You’ll be able to edit this later.
Select a undertaking profile. For this demo, we select the SQL analytics profile from the accessible templates.
Go away the default values as they’re or modify them based on your use case, then select Proceed.
Select Create undertaking to finalize the undertaking and initialize your SQL analytics workspace.

For extra detailed info and superior configurations, discuss with Create a undertaking.

Configure Amazon Redshift for TIP and validate entry

Run the setup-consumer-redshift.sh script (supplied within the stipulations). This script will create a brand new namespace and workgroup and add the required tags, which you’ll use later to combine with SageMaker Unified Studio compute.

If you’re creating the cluster manually, add one of many following tags to the Redshift cluster or workgroup that you simply wish to add to SageMaker Unified Studio:

Possibility 1 – Add a tag to permit solely a selected SageMaker Unified Studio undertaking to entry it: AmazonDataZoneProject=
Possibility 2 – Add a tag to permit all SageMaker Unified Studio initiatives on this account to entry it: for-use-with-all-datazone-projects=true

Create compute utilizing IAM Id Middle authentication

After you arrange your undertaking, the following step is to ascertain a compute useful resource connection on the SageMaker Unified Studio console. Observe these steps so as to add both Amazon Redshift Serverless or a provisioned cluster to your undertaking setting:

Go to the Compute part of your undertaking in SageMaker Unified Studio.
On the Information warehouse tab, select Add compute.
You’ll be able to create a brand new compute useful resource or select an present one. For this publish, we select Connect with present compute assets, then select Subsequent.
Select the kind of compute useful resource you wish to add, then select Subsequent. For this publish, we select Redshift Serverless.
Beneath Connection properties, present the JDBC URL or the compute you wish to add, which is built-in with IAM Id Middle. If the compute useful resource is in the identical account as your SageMaker Unified Studio undertaking, you possibly can choose the compute useful resource from the dropdown menu. In our instance, we use the buyer account that was simply provisioned.
Beneath Authentication, choose IAM Id Middle.
For Identify, enter the title of the Redshift Serverless or provisioned cluster you wish to add.
For Description, enter an outline of the compute useful resource.
Select Add compute.

The SageMaker Unified Studio Venture Compute and Information pages will now show info for that useful resource.

If all the things is configured accurately, your compute will probably be created utilizing IAM Id Middle. As a result of your IdP credentials are already cached whilst you’re logged in to SageMaker Unified Studio, it makes use of the identical credentials and creates the compute.

Check information entry utilizing Amazon Redshift

When Ethan logs in to SageMaker Unified Studio utilizing IAM Id Middle authentication, he efficiently federates and may entry buyer information from all nations however just for non-sensitive columns. Let’s connect with Amazon Redshift in SageMaker Unified Studio by following these steps:

Select Actions and select Open Question editor.
Select Redshift within the Information explorer pane.
Run the shopper gross sales calculation question to watch that consumer Ethan (an information analyst) can entry buyer information from all nations however solely non-sensitive columns (id, birth_country, product_id):
```
choose current_user, c.*, sum(s.sales_amount) as total_sales
from "awsdatacatalog"."customerdb"."buyer" c
be part of "dev@salescatalog"."sales_schema"."store_sales" s 
on c.id=s.id
group by all;
```

You might have efficiently configured Redshift to make use of IAM Id Middle authentication in SageMaker Unified Studio.

Validate information entry utilizing Amazon Athena

When Frank logs in to SageMaker Unified Studio utilizing IAM Id Middle authentication, he efficiently federates and may entry buyer information just for america. To question with Athena, full the next steps:

Select Actions and select Open Question editor.
Select Lakehouse within the Information explorer pane.
Discover AwsDataCatalog, increase the database, select the respective desk, and on the choices menu (three dots), select Preview information.

The next demonstration illustrates how consumer Frank, a BI analyst, can carry out SQL evaluation utilizing Athena. As a result of row-level filtering carried out via Lake Formation, Frank’s entry is restricted to buyer information from america solely. Moreover, you possibly can observe that within the Information explorer pane, Frank can solely view the customerdb database. The dev@salescatalog database just isn’t seen to Frank as a result of no entry has been granted to his respective group from Lake Formation.

The IAM Id Middle authentication integration is full; you should use each Amazon Redshift and Athena via SageMaker Unified Studio in a simplified, all-in-one interface.Notice that, on the time of writing, Athena doesn’t work with Redshift Managed Storage (RMS).

Clear up

Full the next steps to wash up the assets you created as a part of this publish:

Delete the info from the S3 bucket.
Delete the Information Catalog objects.
Delete the Lake Formation assets and Athena account.
Delete the SageMaker Unified Studio undertaking and related area.
When you created new Redshift cluster for testing this answer, delete the cluster.

Conclusion

On this publish, we supplied a complete information to enabling trusted id propagation inside SageMaker Unified Studio. We coated the setup of a SageMaker Unified Studio area with SSO, the creation of tailor-made initiatives, environment friendly consumer onboarding with acceptable permissions, and the administration of AWS Glue and Amazon Redshift managed catalog permissions utilizing Lake Formation. Via sensible examples, we demonstrated methods to use each Amazon Redshift and Athena inside SageMaker Unified Studio, showcasing safe information entry and evaluation capabilities. This method helps organizations keep strict id controls whereas serving to information scientists and analysts derive invaluable insights from each information lake and information warehouse environments, supporting each safety and productiveness in machine studying workflows.

For extra info on this integration, discuss with Trusted id propagation.