 |
I’m happy to announce a brand new use case primarily based on trusted identification propagation, a lately launched functionality of AWS IAM Identification Heart.
Tableau, a generally used enterprise intelligence (BI) utility, can now propagate end-user identification all the way down to Amazon Redshift. This has a triple profit. It simplifies the sign-in expertise for finish customers. It permits knowledge homeowners to outline entry primarily based on actual end-user identification. It permits auditors to confirm knowledge entry by customers.
Trusted identification propagation permits functions that eat knowledge (comparable to Tableau, Amazon QuickSight, Amazon Redshift Question Editor, Amazon EMR Studio, and others) to propagate the person’s identification and group memberships to the companies that retailer and handle entry to the information, comparable to Amazon Redshift, Amazon Athena, Amazon Easy Storage Service (Amazon S3), Amazon EMR, and others. Trusted identification propagation is a functionality of IAM Identification Heart that improves the sign-in expertise throughout a number of analytics functions, simplifies knowledge entry administration, and simplifies audit. Finish customers profit from single sign-on and shouldn’t have to specify the IAM roles they wish to assume to hook up with the system.
Earlier than diving into extra particulars, let’s agree on terminology.
I exploit the time period “identification suppliers” to seek advice from the methods that maintain person identities and group memberships. These are the methods that immediate the person for credentials and carry out the authentication. For instance, Azure Listing, Okta, Ping Identification, and extra. Test the complete checklist of identification suppliers we assist.
I exploit the time period “user-facing functions” to designate the functions that eat knowledge, comparable to Tableau, Microsoft PowerBI, QuickSight, Amazon Redshift Question Editor, and others.
And eventually, once I write “downstream companies”, I seek advice from the analytics engines and storage companies that course of, retailer, or handle entry to your knowledge: Amazon Redshift, Athena, S3, EMR, and others.
To know the good thing about trusted identification propagation, let’s briefly discuss how knowledge entry was granted till right now. When a user-facing utility accesses knowledge from a downstream service, both the upstream service makes use of generic credentials (comparable to “tableau_user“) or assumes an IAM position to authenticate in opposition to the downstream service. That is the supply of two challenges.
First, it makes it troublesome for the downstream service administrator to outline entry insurance policies which might be fine-tuned for the precise person making the request. As seen from the downstream service, all requests originate from that widespread person or IAM position. If Jeff and Jane are each mapped to the BusinessAnalytics IAM position, then it’s not doable to provide them totally different ranges of entry, for instance, readonly and read-write. Moreover, if Jeff can be within the Finance group, he wants to decide on a task through which to function; he can not entry knowledge from each teams in the identical session.
Secondly, the duty of associating a data-access occasion to an finish person entails some undifferentiated heavy lifting. If the request originates from an IAM position known as BusinessAnalytics, then extra work is required to determine which person was behind that motion.
Nicely, this explicit instance would possibly look quite simple, however in actual life, organizations have lots of of customers and hundreds of teams to match to lots of of datasets. There was a chance for us to Invent and Simplify.
As soon as configured, the brand new trusted identification propagation offers a technical mechanism for user-facing functions to entry knowledge on behalf of the particular person behind the keyboard. Understanding the precise person identification provides three fundamental benefits.
First, it permits downstream service directors to create and handle entry insurance policies primarily based on precise person identities, the teams they belong to, or a mixture of the 2. Downstream service directors can now assign entry by way of customers, teams, and datasets. That is the best way most of our prospects naturally take into consideration entry to knowledge—intermediate mappings to IAM roles are now not essential to realize these patterns.
Second, auditors now have entry to the unique person identification in system logs and might confirm that insurance policies are applied accurately and comply with all necessities of the corporate or industry-level insurance policies.
Third, customers of BI functions can profit from single sign-on between functions. Your end-users now not want to grasp your organization’s AWS accounts and IAM roles. As an alternative, they will register to EMR Studio (for instance) utilizing their company single sign-on that they’re used to for thus many different issues they do at work.
How does trusted identification propagation work?
Trusted identification propagation depends on customary mechanisms from our {industry}: OAuth2 and JWT. OAuth2 is an open customary for entry delegation that permits customers to grant third-party user-facing functions entry to knowledge on different companies (downstream companies) with out exposing their credentials. JWT (JSON Internet Token) is a compact, URL-safe technique of representing identities and claims to be transferred between two events. JWTs are signed, which suggests their integrity and authenticity will be verified.
Learn how to configure trusted identification propagation
Configuring trusted identification propagation requires setup in IAM Identification Heart, on the user-facing utility, and on the downstream service as a result of every of those must be advised to work with end-user identities. Though the particulars might be totally different for every utility, they are going to all comply with this sample:
- Configure an identification supply in AWS IAM Identification Heart. AWS recommends enabling automated provisioning in case your identification supplier helps it, as most do. Automated provisioning works by means of the SCIM synchronization customary to synchronize your listing customers and teams into IAM Identification Heart. You most likely have configured this already should you at the moment use IAM Identification Heart to federate your workforce into the AWS Administration Console. It is a one-time configuration, and also you don’t should repeat this step for every user-facing utility.
- Configure your user-facing utility to authenticate its customers together with your identification supplier. For instance, configure Tableau to make use of Okta.
- Configure the connection between the user-facing utility and the downstream service. For instance, configure Tableau to entry Amazon Redshift. In some circumstances, it requires utilizing the ODBC or JDBC driver for Redshift.
Then comes the configuration particular to trusted identification propagation. For instance, think about your group has developed a user-facing internet utility that authenticates the customers together with your identification supplier, and that you just wish to entry knowledge in AWS on behalf of the present authenticated person. For this use case, you’d create a trusted token issuer in IAM Identification Heart. This highly effective new assemble offers you a approach to map your utility’s authenticated customers to the customers in your IAM Identification Heart listing in order that it could make use of trusted identification propagation. My colleague Becky wrote a weblog publish to indicate you methods to develop such an utility. This extra configuration is required solely when utilizing third-party functions, comparable to Tableau, or a customer-developed utility, that authenticate outdoors of AWS. When utilizing user-facing functions managed by AWS, comparable to Amazon QuickSight, no additional setup is required.
Lastly, downstream service directors should configure the entry insurance policies primarily based on the person identification and group memberships. The precise configuration varies from one downstream service to the opposite. If the appliance reads or writes knowledge in Amazon S3, the information proprietor could use S3 Entry Grants within the Amazon S3 console to grant entry for customers and teams to prefixes in Amazon S3. If the appliance makes queries to an Amazon Redshift knowledge warehouse, the information proprietor should configure IAM Identification Heart trusted connection within the Amazon Redshift console and match the viewers declare (aud) from the identification supplier.
Now that you’ve a high-level overview of the configuration, let’s dive into a very powerful half: the person expertise.
The tip-user expertise
Though the exact expertise of the tip person will clearly be totally different for various functions, in all circumstances, it will likely be easier and extra acquainted to workforce customers than earlier than. The person interplay will start with a redirect-based authentication single sign-on movement that takes the person to their identification supplier, the place they will register with credentials, multi-factor authentication, and so forth.
Let’s take a look at the small print of how an finish person would possibly work together with Okta and Tableau when trusted identification propagation has been configured.
Right here is an illustration of the movement and the principle interactions between methods and companies.
Right here’s the way it goes.
1. As a person, I try and register to Tableau.
2. Tableau initiates a browser-based movement and redirects to the Okta sign-in web page the place I can enter my sign-in credentials. On profitable authentication, Okta points an authentication token (ID and entry token) to Tableau.
3. Tableau initiates a JDBC reference to Amazon Redshift and contains the entry token within the connection request. The Amazon Redshift JDBC driver makes a name to Amazon Redshift. As a result of your Amazon Redshift administrator enabled IAM Identification Heart, Amazon Redshift forwards the entry token to IAM Identification Heart.
4. IAM Identification Heart verifies and validates the entry token and alternate the entry token for an Identification Heart issued token.
5. Amazon Redshift will resolve the Identification Heart token to find out the corresponding Identification Heart person and authorize entry to the useful resource. Upon profitable authorization, I can join from Tableau to Amazon Redshift.
As soon as authenticated, I can begin to use Tableau as traditional.
And once I hook up with Amazon Redshift Question Editor, I can observe the sys_query_history desk to test who was the person who made the question. It accurately reviews awsidc:<e mail deal with>, the Okta e mail deal with I used once I related from Tableau.
You’ll be able to learn Tableau’s documentation for extra particulars about this configuration.
Pricing and availability
Trusted identification propagation is offered at no extra price in the 26 AWS Areas the place AWS IAM Identification Heart is accessible right now.
Listed below are extra particulars about trusted identification propagation and downstream service configurations.
Completely satisfied studying!
With trusted identification propagation, now you can configure analytics methods to propagate the precise person identification, group membership, and attributes to AWS companies comparable to Amazon Redshift, Amazon Athena, or Amazon S3. It simplifies the administration of entry insurance policies on these companies. It additionally permits auditors to confirm your group’s compliance posture to know the actual identification of customers accessing knowledge.
Get began now and configure your Tableau integration with Amazon Redshift.
PS: Writing a weblog publish at AWS is at all times a staff effort, even if you see just one identify below the publish title. On this case, I wish to thank Eva Mineva, Laura Reith, and Roberto Migli for his or her much-appreciated assist in understanding the various subtleties and technical particulars of trusted identification propagation.