Duo Single Sign-On for Amazon EMR Studio

Overview

As business applications move from on-premises to cloud hosted solutions, users experience password fatigue due to disparate logons for different applications. Single sign-on (SSO) technologies seek to unify identities across systems and reduce the number of different credentials a user has to remember or input to gain access to resources.

While SSO is convenient for users, it presents new security challenges. If a user's primary password is compromised, attackers may be able to gain access to multiple resources. In addition, as sensitive information makes its way to cloud-hosted services it is even more important to secure access by implementing two-factor authentication and zero-trust policies.

About Duo Single Sign-On

Duo Single Sign-On is our cloud-hosted SSO product which layers Duo's strong authentication and flexible policy engine on top of Amazon EMR Studio logins. Duo Single Sign-On acts as an identity provider (IdP), authenticating your users using existing on-premises Active Directory (AD) or another SSO IdP. Duo SSO prompts users for two-factor authentication and performs endpoint assessment and verification before permitting access to Amazon EMR Studio.

Duo Single Sign-On is available in Duo Premier, Duo Advantage, and Duo Essentials plans, which also include the ability to define policies that enforce unique controls for each individual SSO application. For example, you can require that Salesforce users complete two-factor authentication at every login, but only once every seven days when accessing Amazon EMR Studio. Duo checks the user, device, and network against an application's policy before allowing access to the application.

Configure Single Sign-On

Before configuring Amazon EMR Studio with Duo SSO using Security Assertion Markup Language (SAML) 2.0 authentication you'll first need to enable Duo Single Sign-On for your Duo account and configure a working authentication source.

Once you have your SSO authentication source working, continue to the next step of creating the Amazon EMR Studio application in Duo.

Create the Amazon EMR Studio Application in Duo

1. Log on to the Duo Admin Panel and navigate to Applications.

2. Click Protect an Application and locate the entry for Amazon EMR Studio with a protection type of "2FA with SSO hosted by Duo (Single Sign-On)" in the applications list. Click Protect to the far-right to start configuring Amazon EMR Studio. See Protecting Applications for more information about protecting applications in Duo and additional application options. You'll need the information on the Amazon EMR Studio page under Downloads later.

3. Amazon EMR Studio uses the Mail attribute when authenticating. We've mapped the <Email Address> bridge attribute to Duo Single Sign-On supported authentication source attributes as follows:

   Bridge Attribute	Active Directory	SAML IdP
   <Email Address>	mail	Email

   If you are using a non-standard email attribute for your authentication source, check the Custom attributes box and enter the name of the attribute you wish to use instead.

4. You can adjust additional settings for your new SAML application at this time — like changing the application's name from the default value, enabling self-service, or assigning a group policy.

5. Keep the Duo Admin Panel open. You will come back to it later.

Duo Universal Prompt

The Duo Universal Prompt provides a simplified and accessible Duo login experience for web-based applications, offering a redesigned visual interface with security and usability enhancements.

Universal Prompt	Traditional Prompt

We've already updated the Duo Amazon EMR Studio application hosted in Duo's service to support the Universal Prompt, so there's no action required on your part to update the application itself. If you created your Amazon EMR Studio application before March 2024, you can activate the Universal Prompt experience for users from the Duo Admin Panel. Amazon EMR Studio applications created after March 2024 have the Universal Prompt activated by default.

If you created your Amazon EMR Studio application before March 2024, it's a good idea to read the Universal Prompt Update Guide for more information, about the update process and the new login experience for users, before you activate the Universal Prompt for your application.

Activate Universal Prompt

Activation of the Universal Prompt is a per-application change. Activating it for one application does not change the login experience for your other Duo applications.

The "Universal Prompt" area of the application details page shows that this application is "Ready to activate", with these activation control options:

• Show traditional prompt: Your users experience Duo's traditional prompt via redirect when logging in to this application.
• Show new Universal Prompt: (Default) Your users experience the Universal Prompt via redirect when logging in to this application.

The application's Universal Prompt status shows "Activation complete" here and on the Universal Prompt Update Progress report.

Should you ever want to roll back to the traditional prompt, you can return to this setting and change it back to Show traditional prompt. However, this will still deliver the Duo prompt via redirect, not in an iframe. Keep in mind that support for the traditional Duo prompt ended for the majority of applications in March 2024.

Universal Update Progress

Click the See Update Progress link to view the Universal Prompt Update Progress report. This report shows the update availability and migration progress for all your Duo applications. You can also activate the new prompt experience for multiple supported applications from the report page instead of visiting the individual details pages for each application.

Enable Amazon EMR Studio for SSO

To enable Amazon EMR Studio for SSO, do the sections below in the order they appear.

Create an EMR Studio

1. In your Amazon console, type EMR into the Search bar at the top of the page.

2. In the search results, click EMR. The "Amazon EMR" page opens.

3. In the left menu sidebar, navigate to EMR Studio → Studios. The "Studios" page opens.

4. Click Create Studio. The "Create a Studio" page opens.

5. In the "Setup options" section, click the Custom radio button.

6. In the "Studio settings" section, enter a unique name for your studio into the Studio name field.

7. At the bottom of the "Studio settings" section, click View permission details. The "Permission details" pop-up window opens.

   

8. Open your Amazon console in a new web page tab. Type IAM into the search bar at the top of the page. In the search results, click IAM. The "IAM Dashboard" opens.

9. In the "AWS Account" section, copy the Account ID and paste it into the Duo Admin Panel Account Number field, under "Service Provider".

   

10. Go to the IAM web page tab. In the left menu sidebar, navigate to Access management → Roles. The "Roles" page opens.

11. Click Create role. The "Select trusted entity" page opens.

12. In the "Trusted entity type" section, click the Custom trust policy radio button.

13. Go to the EMR Studio web page tab. In the "Permission details" pop-up window, copy the "Trust policy".

14. Go to the IAM web page tab. In the "Select trusted entity" page, paste the trust policy into the Custom trust policy field.

    

15. Scroll to the bottom of the "Select trusted entity" page and click Next. The "Add permissions" page opens.

16. Scroll to the bottom of the page and click Next again. The "Name, review, and create" page opens.

17. In the "Role details" section, enter a unique name for your role into the Role name field.

18. Scroll to the bottom of the page and click Create role.

19. In the left menu sidebar, click Policies. The "Policies" page opens.

20. Click Create policy. The "Specify permissions" page opens.

21. In the "Policy editor" section, click JSON.

22. Go to the EMR Studio web page tab. In the "Permission details" pop-up window, copy the "IAM policy".

23. Go to the IAM web page tab. In the "Specify permissions" page, paste the IAM policy into the Policy editor field.

    

24. Scroll to the bottom of the "Specify permissions" page and click Next. The "Review and create" page opens.

25. In the "Policy details" section, enter a unique name for your policy into the Policy name field.

26. Scroll to the bottom of the page and click Create policy.

27. In the left menu sidebar, click Roles. The "Roles" page opens.

28. In the Role name column, click the role you created earlier. Your role page opens.

29. In the "Permissions policies" section, click the Add permissions drop-down menu and select Attach policies. The "Attach policy to (your role)" page opens.

30. Click the checkbox next to the policy you created earlier.

31. Scroll to the bottom of the page and click Add permissions.

32. Go to the EMR Studio web page tab. Close the "Permission details" pop-up window to return to the "Create a Studio" page.

33. In the "Create a Studio" page, at the bottom of the "Studio settings" section, click the refresh button next to the Service role to let Studio access your AWS resources drop-down menu.

34. Click the Service role to let Studio access your AWS resources drop-down menu and select the role you created earlier.

35. Scroll down to the "Authentication" section. Click the Identity provider - optional drop-down menu and select Other/None.

36. Return to the Duo Admin Panel. Under "Metadata", copy the Login URL.

    

37. Return to the EMR Studio web page tab. Paste the login URL into the Identity provider URL - optional field of the "Authentication" section.

38. Type RelayState into the RelayState parameter name field. "RelayState" is case-sensitve.

39. Scroll to the bottom of the page and click Create Studio.

Add an Identity Provider

1. Go to the IAM web page tab. In the left menu sidebar, click Identity providers. The "Identity providers" page opens.

2. Click Add provider. The "Add an Identity provider" page opens.

3. In the "Configure provider" section, click the SAML radio button.

4. Enter a unique name for your identity provider into the Provider name field.

5. Copy your provider name and paste it into the Duo Admin Panel Provider Name field, under "Service Provider.

   

6. In the Duo Admin Panel under "Downloads", click Download XML.

7. Go to the IAM web page tab. In the "Configure provider" section, click Choose file and open the XML file you downloaded from Duo earlier.

8. Scroll to the bottom of the page and click Add provider.

Create a Role

1. Go to the IAM web page tab. In the left menu sidebar, click Roles. The "Roles" page opens.

2. Click Create role. The "Select trusted entity" page opens.

3. In the "Trusted entity type" section, click the SAML 2.0 federation radio button.

4. In the "SAML 2.0 federation" section, click the SAML 2.0-based provider drop-down menu and select the identity provider you created earlier.

5. Click the Allow programmatic access only radio button.

6. Click the Attribute drop-down menu and select SAML:sub_type.

7. Type persistent into the Value field. "persistent" is case-sensitive.

8. Click Next. The "Add permissions" page opens.

9. Scroll to the bottom of the page and click Next again. The "Name, review, and create" page opens.

10. Enter a unique name for your role into the Role name field.

11. Scroll to the bottom of the page and click Create role.

Create an Inline Policy

1. On the "Roles" page, in the Role name column, click the role you created in the "Create a Role" section above. Your role page opens.

2. In the "Permissions policies" section, click the Add permissions drop-down menu and select Create inline policy. The "Specify permissions" page opens.

3. In the "Select a service" section, click the Service drop-down menu and select EMR.

4. In the "Actions allowed" section, click the All EMR actions (elasticmapreduce:*) checkbox.

5. Scroll down to the "Resources" section. Next to "studio", click Add ARNs. The "Specify ARN(s)" pop-up window opens.

6. Go to the EMR Studio web page tab. In the upper right corner of the page, click the region drop-down menu and copy your region code, as highlighted in the image below.

   

7. Go to the IAM web page tab. Paste the region code into the Resource region field of the "Specify ARN(s)" pop-up window.

8. Return to the Duo Admin Panel. Paste the region code into the Region ID field, under "Service Provider".

   

9. Go to the EMR web page tab. On the "Studios" page, in the Studio name column, click the studio you created earlier. Your studio page opens.

10. In the "Studio settings" section, copy the Studio ID.

11. Go to the IAM web page tab. Paste the studio ID into the Resource studio field of the "Specify ARN(s)" pop-up window.

12. Return to the Duo Admin Panel. Paste the studio ID into the Studio ID field, under "Service Provider".

    

13. Go to the IAM web page tab. In the "Specify ARN(s)" pop-up window, click Add ARNs.

14. Scroll to the bottom of the page and click Next. The "Review and create" page opens.

15. In the "Policy details" section, enter a unique name for your policy into the Policy name field.

16. Click Create policy.

Group Mapping

1. In the left menu sidebar, click Roles. The "Roles" page opens.

2. In the Role name column, copy the role you created earlier and paste it into the Duo Admin Panel Amazon Studio role field, under "Service provider".

3. In the Duo Admin Panel, click the Duo Groups drop-down menu and select the applicable group to map.

   

4. Scroll to the bottom of the page and click Save.

Learn more about Amazon EMR Studio SSO at AWS Documentation.

Add a Tile to Duo Central

Duo Central is our cloud-hosted portal which allows users to access all of their applications in one spot. Amazon EMR Studio requires IdP-initiated sign-on, so you must add an application tile for it to Duo Central for your users to access the application. To add a tile for Amazon EMR Studio to Duo Central, do the following:

1. In the Duo Admin Panel, navigate to Single Sign-On → Duo Central.

2. If you have not already enabled Duo Central, review the information on the page and click Get Started. Complete the initial Duo Central configuration before proceeding to the next step.

3. Click Add tile and then click Add application tile.

4. Click the checkbox next to "Amazon EMR Studio - Single Sign-On".

5. Click Add tile.

See Duo Central to learn more about adding an application tile.

Using SSO

Log into Duo Central with your custom URL, and then click the Amazon EMR Studio - Single Sign-On tile to be redirected to Duo Single Sign-On to begin authentication.

If you do not know your Duo Central custom URL, you can find it in the Duo Admin Panel by navigating to Single Sign-On → Duo Central. In the upper right corner of the page, click your Duo Central custom URL to access the Amazon EMR Studio tile.

Active Directory Login

With Active Directory as the Duo SSO authentication source, enter the primary username (email address) on the Duo SSO login page and click or tap Next.

Enter the AD primary password and click or tap Log in to continue.

Enable Duo Passwordless to log in to Duo SSO backed by Active Directory authentication without entering a password in the future.

SAML Login

With another SAML identity provider as the Duo SSO authentication source, Duo SSO immediately redirects the login attempt to that SAML IdP for primary authentication. Users do not see the Duo SSO primary login screen.

Duo Authentication

Successful verification of your primary credentials by Active Directory or a SAML IdP redirects back to Duo. Complete Duo two-factor authentication when prompted and then you'll return to Amazon EMR Studio to complete the login process.

* Universal Prompt experience shown.

Congratulations! Your Amazon EMR Studio users now authenticate using Duo Single Sign-On.

See the full user login experience, including expired password reset (available for Active Directory authentication sources) in the Duo End User Guide for SSO.

Enable Remembered Devices

To minimize additional Duo two-factor prompts when switching between Amazon EMR Studio and your other Duo Single Sign-On SAML applications, be sure to apply a shared "Remembered Devices" policy to your SAML applications.

Troubleshooting

Need some help? Try searching our Knowledge Base articles or Community discussions. For further assistance, contact Support.