Amazon Redshift is a quick, scalable, and absolutely managed cloud knowledge warehouse that means that you can course of and run your complicated SQL analytics workloads on structured and semi-structured knowledge. Tens of hundreds of consumers use Amazon Redshift to course of massive quantities of information, modernize their knowledge 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 knowledge into actionable insights with unprecedented velocity and effectivity. By way of this collaboration, Amazon Redshift now helps AWS IAM Id Heart integration with ThoughtSpot, enabling seamless and safe knowledge 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 Id Heart integration, ThoughtSpot customers didn’t have native connectivity to combine Amazon Redshift with their identification suppliers (IdPs), which might present unified governance and identification propagation throughout a number of AWS providers like AWS Lake Formation and Amazon Easy Storage Service (Amazon S3).
Now, ThoughtSpot customers can natively hook up with Amazon Redshift utilizing the IAM Id Heart integration, which streamlines knowledge analytics entry administration whereas sustaining strong safety. By configuring Amazon Redshift as an AWS managed software, organizations profit from SSO capabilities with trusted identification propagation and a trusted token issuer (TTI). The IAM Id Heart integration with Amazon Redshift gives centralized consumer administration, mechanically synchronizing entry permissions with organizational modifications—whether or not staff be 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 Id Heart. Organizations can additional improve their safety posture by utilizing Lake Formation to outline granular entry management permissions on catalog sources for IdP identities. From a compliance and safety standpoint, the mixing presents complete audit trails by logging end-user identities each in Amazon Redshift and AWS CloudTrail, offering visibility into knowledge entry patterns and consumer actions.
Dime Dimovski, a Knowledge Warehousing Architect at Merck, shares:
“The latest integration of Amazon Redshift with our identification entry administration middle will considerably improve our knowledge 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’ll profit from a seamless single sign-on expertise—giving us granular entry controls in addition to the safety and effectivity we want.”
On this put up, we stroll you thru the method of establishing ThoughtSpot integration with Amazon Redshift utilizing IAM Id Heart authentication. The answer gives a safe, streamlined analytics setting that empowers your staff to concentrate on what issues most: discovering and sharing priceless enterprise insights.
Answer overview
The next diagram illustrates the structure of the ThoughtSpot SSO integration with Amazon Redshift, IAM Id Heart, and your IdP.
The answer consists of the next steps:
The consumer configures ThoughtSpot to entry Amazon Redshift utilizing IAM Id Heart.
When a consumer makes an attempt to sign up, ThoughtSpot initiates a browser-based OAuth stream and redirects the consumer to their most popular IdP (reminiscent of 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 Id Heart software and forwards the entry token.
Amazon Redshift passes the token to IAM Id Heart for validation.
IAM Id Heart first validates the token utilizing the OpenID Join (OIDC) discovery connection to the TTI and returns an IAM Id Heart generated entry token for a similar consumer. The TTI allows you to use trusted identification propagation with functions that authenticate outdoors of AWS. Within the previous determine, the IdP authorization server is the TTI.
Amazon Redshift makes use of IAM Id Heart APIs to acquire the consumer and group membership info from AWS Id Heart.
The ThoughtSpot consumer can now join with Amazon Redshift and entry knowledge primarily based on the consumer and group membership returned from IAM Id Heart.
On this put up, you’ll use the next steps to construct the answer:
Arrange an OIDC software.
Arrange a TTI in IAM Id Heart.
Arrange consumer connections and TTIs in Amazon Redshift.
Federate to Amazon Redshift from ThoughtSpot utilizing IAM Id Heart.
Stipulations
Earlier than you start implementing the answer, you have to 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 identification 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 Utility for Utility sort.
Select Subsequent.
On the Basic tab, present the next info:
For App integration identify, enter a reputation in your app integration. For instance, ThoughtSpot_Redshift_App.
For Grant sort, choose Authorization Code and Refresh Token.
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.
For Signal-out redirect URIs, maintain the default worth as http://localhost:8080.
Skip the Trusted Origins part and for Assignments, choose Skip group project for now.
Select Save.
Select the Assignments tab after which select Assign to Teams. On this instance, we’re assigning awssso-finance and awssso-sales.
Select Executed.
Arrange an EntraID OIDC software
To create your EntraID software, observe these steps:
Register to the Microsoft Entra admin middle as Cloud Utility Administrator (or increased stage of entry).
Browse to App registrations below Handle, and select New registration.
Enter a reputation for the applying. For instance, ThoughtSpot-OIDC-App.
Choose a supported account sort, which determines who can use the applying. For this instance, choose the primary possibility within the checklist.
Below 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 will probably 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, maintain the Microsoft beneficial default expiration worth of 6 months.
Select Add.
Copy the key worth.
The key worth will solely be offered one time; after that you may’t learn it. Ensure that to repeat it now. In the event you fail to reserve it, you have to generate a brand new consumer secret.
Within the navigation pane, below Handle, select Expose an API.
In the event you’re establishing for the primary time, you may see Add to the fitting of the applying ID URI.
Select Save.
After the applying 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.
Below OpenId permissions, select e mail, offlines_access, openid, and profile, and select Add permissions.
Arrange a TTI in IAM Id Heart
Assuming you might have accomplished the stipulations, you’ll set up your IdP as a TTI in your delegated administration account. To create a TTI, confer with Find out how to add a trusted token issuer to the IAM Id Heart console. On this put up, we stroll by 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 duplicate the Issuer
url.
Within the Map attributes part, select which IdP attributes correspond to Id Heart attributes. For instance, within the following screenshot, we mapped Okta’s Topic attribute to the Electronic mail attribute in IAM Id Heart.
Select Create trusted token issuer.
Arrange a TTI for EntraID
Full the next steps to arrange a TTI for EntraID:
To seek 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 a couple of signifies v2.0 tokens.
Subsequent, you might 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 could find the tenant ID worth as proven within the following screenshot. In the event you’re utilizing the v1.0 token, the issuer URL will probably be https://sts.home windows.internet//. In the event you’re utilizing the v2.0 token, the issuer URL will probably 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 Electronic mail from the IAM identification Heart attribute.
Select Create trusted token issuer.
Arrange consumer connections and TTIs in Amazon Redshift
On this step, you configure the Amazon Redshift functions that alternate 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 have to gather 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 duplicate 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 could find the viewers worth (Utility ID URI) as proven within the following screenshot.
Configure the applying
After you gather the viewers worth from the respective IdP, you might want to configure the Amazon Redshift software within the member account the place the Amazon Redshift cluster or serverless occasion exists.
Select IAM Id Heart connection within the navigation pane on the Amazon Redshift console.
Select the Amazon Redshift software that you just created as a part of the stipulations.
Select the Consumer connections tab and select Edit.
Select Sure below Configure consumer connections that use third-party IdPs.
Choose the test field for Trusted token issuer that you just created within the earlier part.
For Aud declare, enter the viewers declare worth below Configure chosen trusted token issuers.
Select Save.
Your IAM Id Heart, Amazon Redshift, and IdP configuration is full. Subsequent, you might want to configure ThoughtSpot.
Federate to Amazon Redshift from ThoughtSpot utilizing IAM Id Heart
Full the next steps in ThoughtSpot to federate with Amazon Redshift utilizing IAM Id Heart authentication:
Register to ThoughtSpot cloud.
Select Knowledge within the high navigation bar.
Open the Connections tab within the navigation pane, and choose the Redshift
Alternatively, you may select Create new within the navigation pane, select Connection, and choose the Redshift tile.
Create a reputation in your connection and an outline (non-obligatory), then select Proceed.
Below Authentication Sort, select AWS IDC OAuth and enter following particulars:
For Host, enter the Redshift endpoint. For instance, test-cluster.ab6yejheyhgf.us-east-1.redshift.amazonaws.com.
For Port, enter 5439.
For OAuth Consumer ID, enter the consumer ID from the IdP OIDC software.
For OAuth Consumer Secret, enter the consumer secret from the IdP OIDC software.
For Scope, enter the scope from the IdP software:
For Okta, use openid offline_access openid profile. You should use the Okta scope values shared earlier as is on ThoughtSpot. You possibly can modify the scope based on your necessities.
For EntraID, use the API scope and API permissions. For instance, api://1230a234-b456-7890-99c9-a12345bcc123/redshift_login offline_access.
For API scope worth, go to the OIDC software, and below Handle, select Expose an API to accumulate the worth.
For API permissions, go to the OIDC software, and below Handle, select API permissions to accumulate the permissions.
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.
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.
For AWS Id Namespace, enter the namespace configured in your Amazon Redshift IAM Id Heart software. The default worth is AWSIDC until beforehand personalized. For this instance, we use awsidc.
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’ll be redirected again to ThoughtSpot and logged in as an IAM Id Heart authenticated consumer.
Congratulations! You’ve logged in by IAM Id Heart and Amazon Redshift, and also you’re able to dive into your knowledge evaluation with ThoughtSpot.
Clear up
Full the next steps to wash up your sources:
Delete the IdP functions that you just created to combine with IAM Id Heart.
Delete the IAM Id Heart configuration.
Delete the Amazon Redshift software and the Amazon Redshift provisioned cluster or serverless occasion that you just created for testing.
Delete the IAM function and IAM coverage that you just created for IAM Id Heart and Amazon Redshift integration.
Delete the permission set from IAM Id Heart that you just 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 put up, we explored learn how to combine ThoughtSpot with Amazon Redshift utilizing IAM Id Heart. The method consisted of registering an OIDC software, establishing an IAM Id Heart TTI, and eventually configuring ThoughtSpot for IAM Id Heart authentication. This setup creates a strong and safe analytics setting that streamlines knowledge entry for enterprise customers.
For extra steerage and detailed documentation, confer with the next key sources:
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 knowledge 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 huge knowledge options to course of knowledge at scale. Earlier than AWS, he helped Amazon.com Provide Chain Optimization Applied sciences migrate its Oracle knowledge warehouse to Amazon Redshift and construct its subsequent era huge knowledge 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, guaranteeing seamless integration and optimum efficiency of ThoughtSpot’s cloud-based providers. 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 attainable within the analytics area, serving to organizations harness the complete potential of their knowledge.
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.
