Combine ThoughtSpot with Amazon Redshift utilizing AWS IAM Identification Middle

Amazon Redshift is a quick, scalable, and absolutely managed cloud information warehouse that permits you to course of and run your advanced SQL analytics workloads on structured and semi-structured information. Tens of hundreds of shoppers use Amazon Redshift to course of massive quantities of knowledge, modernize their information analytics workloads, and supply insights for his or her enterprise customers.

The mix of Amazon Redshift and ThoughtSpot’s AI-powered analytics service permits organizations to remodel their uncooked information into actionable insights with unprecedented velocity and effectivity. By this collaboration, Amazon Redshift now helps AWS IAM Identification Middle integration with ThoughtSpot, enabling seamless and safe information entry with streamlined authentication and authorization workflows. This single sign-on (SSO) integration is out there throughout ThoughtSpot’s cloud panorama and can be utilized for each embedded and standalone analytics implementations.

Previous to the IAM Identification Middle integration, ThoughtSpot customers didn’t have native connectivity to combine Amazon Redshift with their id suppliers (IdPs), which might present unified governance and id propagation throughout a number of AWS companies like AWS Lake Formation and Amazon Easy Storage Service (Amazon S3).

Now, ThoughtSpot customers can natively hook up with Amazon Redshift utilizing the IAM Identification Middle integration, which streamlines information analytics entry administration whereas sustaining strong safety. By configuring Amazon Redshift as an AWS managed software, organizations profit from SSO capabilities with trusted id propagation and a trusted token issuer (TTI). The IAM Identification Middle integration with Amazon Redshift gives centralized consumer administration, mechanically synchronizing entry permissions with organizational adjustments—whether or not staff be a part of, transition roles, or go away the group. The answer makes use of Amazon Redshift role-based entry management options that align with IdP teams synced in IAM Identification Middle. Organizations can additional improve their safety posture through the use of Lake Formation to outline granular entry management permissions on catalog assets for IdP identities. From a compliance and safety standpoint, the mixing affords complete audit trails by logging end-user identities each in Amazon Redshift and AWS CloudTrail, offering visibility into information entry patterns and consumer actions.

Dime Dimovski, a Information Warehousing Architect at Merck, shares:

“The latest integration of Amazon Redshift with our id entry administration heart will considerably improve our information entry administration as a result of we will propagate consumer identities throughout numerous instruments. Through the use of OAuth authentication from ThoughtSpot to Amazon Redshift, we are going to profit from a seamless single sign-on expertise—giving us granular entry controls in addition to the safety and effectivity we want.”

On this submit, we stroll you thru the method of establishing ThoughtSpot integration with Amazon Redshift utilizing IAM Identification Middle authentication. The answer gives a safe, streamlined analytics surroundings that empowers your staff to deal with what issues most: discovering and sharing precious enterprise insights.

Answer overview

The next diagram illustrates the structure of the ThoughtSpot SSO integration with Amazon Redshift, IAM Identification Middle, and your IdP.

The answer consists of the next steps:

The consumer configures ThoughtSpot to entry Amazon Redshift utilizing IAM Identification Middle.
When a consumer makes an attempt to check in, ThoughtSpot initiates a browser-based OAuth circulate and redirects the consumer to their most popular IdP (similar to Okta or Microsoft EntraID) sign-in web page to enter their credentials.
Following profitable authentication, IdP points authentication tokens (ID and entry token) to ThoughtSpot.
The Amazon Redshift driver then makes a name to the Amazon Redshift enabled AWS Identification Middle software and forwards the entry token.
Amazon Redshift passes the token to IAM Identification Middle for validation.
IAM Identification Middle first validates the token utilizing the OpenID Join (OIDC) discovery connection to the TTI and returns an IAM Identification Middle generated entry token for a similar consumer. The TTI allows you to use trusted id propagation with purposes that authenticate exterior of AWS. Within the previous determine, the IdP authorization server is the TTI.
Amazon Redshift makes use of IAM Identification Middle APIs to acquire the consumer and group membership info from AWS Identification Middle.
The ThoughtSpot consumer can now join with Amazon Redshift and entry information based mostly on the consumer and group membership returned from IAM Identification Middle.

On this submit, you’ll use the next steps to construct the answer:

Arrange an OIDC software.
Arrange a TTI in IAM Identification Middle.
Arrange consumer connections and TTIs in Amazon Redshift.
Federate to Amazon Redshift from ThoughtSpot utilizing IAM Identification Middle.

Conditions

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

Arrange an OIDC software

On this part, we’ll present you the step-by-step course of to arrange an OIDC software utilizing each Okta and EntraID because the id suppliers.

Arrange an Okta OIDC software

Full the next steps to arrange an Okta OIDC software:

Register to your Okta group as a consumer with administrative privileges.
On the admin console, below Purposes within the navigation pane, select Purposes.
Select Create App Integration.
Choose OIDC – OpenID Join for Signal-in methodology and Net Software for Software kind.
Select Subsequent.
On the Normal tab, present the next info:
1. For App integration identify, enter a reputation to your app integration. For instance, ThoughtSpot_Redshift_App.
2. For Grant kind, choose Authorization Code and Refresh Token.
3. For Signal-in redirect URIs, select Add URI and together with the default URI, add the URI https:///callosum/v1/connection/generateTokens. The sign-in redirect URI is the place Okta sends the authentication response and ID token for the sign-in request. The URIs have to be absolute URIs.
4. For Signal-out redirect URIs, preserve the default worth as http://localhost:8080.
5. Skip the Trusted Origins part and for Assignments, choose Skip group project for now.
6. Select Save.
Select the Assignments tab after which select Assign to Teams. On this instance, we’re assigning awssso-finance and awssso-sales.
Select Carried out.

Arrange an EntraID OIDC software

To create your EntraID software, observe these steps:

Register to the Microsoft Entra admin heart as Cloud Software Administrator (or greater degree of entry).
Browse to App registrations below Handle, and select New registration.
Enter a reputation for the appliance. For instance, ThoughtSpot-OIDC-App.
Choose a supported account kind, which determines who can use the appliance. For this instance, choose the primary possibility within the listing.
Underneath Redirect URI, select Net for the kind of software you wish to create. Enter the URI the place the entry token is shipped to. Your redirect URL shall be within the format https:///callosum/v1/connection/generateTokens.
Select Register.
Within the navigation pane, select Certificates & secrets and techniques.
Select New consumer secret.
Enter an outline and choose an expiration for the key or specify a customized lifetime. For this instance, preserve the Microsoft really helpful default expiration worth of 6 months.
Select Add.
Copy the key worth.

The key worth will solely be introduced one time; after that you may’t learn it. Be sure that to repeat it now. In case you fail to reserve it, you should generate a brand new consumer secret.

Within the navigation pane, below Handle, select Expose an API.

In case you’re establishing for the primary time, you’ll be able to see Add to the appropriate of the appliance ID URI.

Select Save.
After the appliance ID URI is about up, select Add a scope.
For Scope identify, enter a reputation. For instance, redshift_login.
For Admin consent show identify, enter a show identify. For instance, redshift_login.
For Admin consent description, enter an outline of the scope.
Select Add scope.
Within the navigation pane, select API permissions.
Select Add a permission and select Microsoft Graph.
Select Delegated Permission.
Underneath OpenId permissions, select electronic mail, offlines_access, openid, and profile, and select Add permissions.

Arrange a TTI in IAM Identification Middle

Assuming you have got accomplished the conditions, you’ll set up your IdP as a TTI in your delegated administration account. To create a TTI, check with add a trusted token issuer to the IAM Identification Middle console. On this submit, we stroll by means of the steps to arrange a TTI for each Okta and EntraID.

Arrange a TTI for Okta

To get the issuer URL from Okta, full the next steps:

Register as an admin to Okta and navigate to Safety after which to API.
Select Default on the Authorization Servers tab and replica the Issuer
url.
Within the Map attributes part, select which IdP attributes correspond to Identification Middle attributes. For instance, within the following screenshot, we mapped Okta’s Topic attribute to the E-mail attribute in IAM Identification Middle.
Select Create trusted token issuer.

Arrange a TTI for EntraID

Full the next steps to arrange a TTI for EntraID:

To search out out which token your software is utilizing, below Handle, select Manifest.
Find the accessTokenAcceptedVersion parameter: null or 1 point out v1.0 tokens, and 2 signifies v2.0 tokens.

Subsequent, you want to discover the tenant ID worth from EntraID.

Go to the EntraID software, select Overview, and a brand new web page will seem containing the Necessities
You’ll find the tenant ID worth as proven within the following screenshot. In case you’re utilizing the v1.0 token, the issuer URL shall be https://sts.home windows.internet//. In case you’re utilizing the v2.0 token, the issuer URL shall be https://login.microsoftonline.com//v2.0.
For Map attributes, the next instance makes use of Different, the place we’re specifying the consumer principal identify (upn) because the IdP attribute to map with E-mail from the IAM id Middle attribute.
Select Create trusted token issuer.

Arrange consumer connections and TTIs in Amazon Redshift

On this step, you configure the Amazon Redshift purposes that change externally generated tokens to make use of the TTI you created within the earlier step. Additionally, the viewers declare (or aud declare) out of your IdP have to be specified. You must acquire the viewers worth from the respective IdP.

Purchase the viewers worth from Okta

To accumulate the viewers worth from Okta, full the next steps:

Register as an admin to Okta and navigate to Safety after which to API.
Select Default on the Authorization Servers tab and replica the Viewers worth.

Purchase the viewers worth from EntraID

Equally, to get the viewers worth EntraID, full the next steps:

Go to the EntraID software, select Overview, and a brand new web page will seem containing the Necessities
You’ll find the viewers worth (Software ID URI) as proven within the following screenshot.

Configure the appliance

After you acquire the viewers worth from the respective IdP, you want to configure the Amazon Redshift software within the member account the place the Amazon Redshift cluster or serverless occasion exists.

Select IAM Identification Middle connection within the navigation pane on the Amazon Redshift console.
Select the Amazon Redshift software that you simply created as a part of the conditions.
Select the Shopper connections tab and select Edit.
Select Sure below Configure consumer connections that use third-party IdPs.
Choose the verify field for Trusted token issuer that you simply created within the earlier part.
For Aud declare, enter the viewers declare worth below Configure chosen trusted token issuers.
Select Save.

Your IAM Identification Middle, Amazon Redshift, and IdP configuration is full. Subsequent, you want to configure ThoughtSpot.

Federate to Amazon Redshift from ThoughtSpot utilizing IAM Identification Middle

Full the next steps in ThoughtSpot to federate with Amazon Redshift utilizing IAM Identification Middle authentication:

Register to ThoughtSpot cloud.
Select Information within the high navigation bar.
Open the Connections tab within the navigation pane, and choose the Redshift

Alternatively, you’ll be able to select Create new within the navigation pane, select Connection, and choose the Redshift tile.

Create a reputation to your connection and an outline (elective), then select Proceed.
Underneath Authentication Kind, select AWS IDC OAuth and enter following particulars:
1. For Host, enter the Redshift endpoint. For instance, test-cluster.ab6yejheyhgf.us-east-1.redshift.amazonaws.com.
2. For Port, enter 5439.
3. For OAuth Shopper ID, enter the consumer ID from the IdP OIDC software.
4. For OAuth Shopper Secret, enter the consumer secret from the IdP OIDC software.
5. For Scope, enter the scope from the IdP software:
  - For Okta, use openid offline_access openid profile. You should utilize the Okta scope values shared earlier as is on ThoughtSpot. You possibly can modify the scope in response to your necessities.
  - For EntraID, use the API scope and API permissions. For instance, api://1230a234-b456-7890-99c9-a12345bcc123/redshift_login offline_access.
6. For API scope worth, go to the OIDC software, and below Handle, select Expose an API to amass the worth.
7. For API permissions, go to the OIDC software, and below Handle, select API permissions to amass the permissions.
8. For Auth Url, enter the authorization endpoint URI:
  - For Okta use https:// /oauth2/default/v1/authorize. For instance, https://prod-1234567.okta.com/oauth2/default/v1/authorize.
  - For EntraID, use https://login.microsoftonline.com//oauth2/v2.0/authorize. For instance, https://login.microsoftonline.com/e12a1ab3-1234-12ab-12b3-1a5012221d12/oauth2/v2.0/authorize.
9. For Entry token Url, enter the token endpoint URI:
  - For Okta, use https:///oauth2/default/v1/token. For instance, https://prod-1234567.okta.com/oauth2/default/v1/token.
  - For EntraID, use https://login.microsoftonline.com//oauth2/v2.0/token. For instance, https://login.microsoftonline.com/e12a1ab3-1234-12ab-12b3-1a5012221d12/oauth2/v2.0/token.
10. For AWS Identification Namespace, enter the namespace configured in your Amazon Redshift IAM Identification Middle software. The default worth is AWSIDC until beforehand custom-made. For this instance, we use awsidc.
11. For Database, enter the database identify you wish to join. For instance, dev.
Select Proceed.
Enter your IdP consumer credentials within the browser pop-up window.

The next screenshot illustrates the ThoughtSpot integration with Amazon Redshift utilizing Okta because the IdP.

The next screenshot exhibits the ThoughtSpot integration with Amazon Redshift utilizing EntraID because the IdP.

Upon a profitable authentication, you may be redirected again to ThoughtSpot and logged in as an IAM Identification Middle authenticated consumer.

Congratulations! You’ve logged in by means of IAM Identification Middle and Amazon Redshift, and also you’re able to dive into your information evaluation with ThoughtSpot.

Clear up

Full the next steps to wash up your assets:

Delete the IdP purposes that you simply created to combine with IAM Identification Middle.
Delete the IAM Identification Middle configuration.
Delete the Amazon Redshift software and the Amazon Redshift provisioned cluster or serverless occasion that you simply created for testing.
Delete the IAM function and IAM coverage that you simply created for IAM Identification Middle and Amazon Redshift integration.
Delete the permission set from IAM Identification Middle that you simply created for Amazon Redshift Question Editor V2 within the administration account.
Delete the ThoughtSpot connection to combine with Amazon Redshift utilizing AWS IDC OAuth.

Conclusion

On this submit, we explored how you can combine ThoughtSpot with Amazon Redshift utilizing IAM Identification Middle. The method consisted of registering an OIDC software, establishing an IAM Identification Middle TTI, and at last configuring ThoughtSpot for IAM Identification Middle authentication. This setup creates a strong and safe analytics surroundings that streamlines information entry for enterprise customers.

For added steerage and detailed documentation, check with the next key assets:

In regards to the authors

Maneesh Sharma is a Senior Database Engineer at AWS with greater than a decade of expertise designing and implementing large-scale information warehouse and analytics options. He collaborates with numerous Amazon Redshift Companions and prospects to drive higher integration.

BP Yau is a Sr Accomplice Options Architect at AWS. His function is to assist prospects architect large information options to course of information at scale. Earlier than AWS, he helped Amazon.com Provide Chain Optimization Applied sciences migrate its Oracle information warehouse to Amazon Redshift and construct its subsequent technology large information analytics platform utilizing AWS applied sciences.

Ali Alladin is the Senior Director of Product Administration and Accomplice Options at ThoughtSpot. On this function, Ali oversees Cloud Engineering and Operations, making certain seamless integration and optimum efficiency of ThoughtSpot’s cloud-based companies. Moreover, Ali spearheads the event of AI-powered options in augmented and embedded analytics, collaborating intently with expertise companions to drive innovation and ship cutting-edge analytics capabilities. With a strong background in product administration and a eager understanding of AI applied sciences, Ali is devoted to pushing the boundaries of what’s doable within the analytics house, serving to organizations harness the complete potential of their information.

Debu Panda is a Senior Supervisor, Product Administration at AWS. He’s an trade chief in analytics, software platform, and database applied sciences, and has greater than 25 years of expertise within the IT world.