Add two-factor authentication and flexible security policies to Amazon Web Services (AWS) SAML 2.0 logins with Duo Single-Sign On, our cloud-hosted SSO identity provider, offering inline self-service enrollment and authentication with Duo Universal Prompt.
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.
Duo Single Sign-On is our cloud-hosted SSO product which layers Duo's strong authentication and flexible policy engine on top of Amazon Web Services (AWS) 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 Web Services (AWS).
Duo Single Sign-On is available in Duo Beyond, Duo Access, and Duo MFA 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 Web Services (AWS). Duo checks the user, device, and network against an application's policy before allowing access to the application.
Before configuring Amazon Web Services (AWS) 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 Web Services (AWS) application in Duo.
Log on to the Duo Admin Panel and navigate to Applications.
Click Protect an Application and locate the entry for Amazon Web Services 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 Web Services. See Protecting Applications for more information about protecting applications in Duo and additional application options. You'll need the information on the Amazon Web Services page under Metadata later.
The new 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 Web Services (AWS) 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. You can activate the Universal Prompt experience for users of new and existing Duo Amazon Web Services (AWS) applications from the Duo Admin Panel.
Before you activate the Universal Prompt for your application, 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.
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 "New Prompt Ready", with these activation control options:
Enable the Universal Prompt experience by selecting Show new Universal Prompt, and then scrolling to the bottom of the page to click Save.
Once you activate the Universal Prompt, the application's Universal Prompt status shows "Update 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.
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 in-scope for Universal Prompt support. 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.
You'll first configure the AWS Single Sign-On settings in the Security Admin Console to enable SAML 2.0 federation and add the SSO information from Duo Single Sign-On.
Log in to the AWS console and click IAM.
Click Identity providers; then click the Create Provider button.
Choose the Provider Type SAML from the drop-down.
Enter sso in lowercase as the "Provider Name".
Click Download XML next to "Metadata Document" button on the Amazon Web Services application's page in the Duo Admin Panel under Downloads to download the Duo Single Sign-On XML file.
Return to the AWS console. Click the Choose File button, select the XML file to upload, and click Next Step.
Verify the provider information and click the Create button.
Next, create a role in AWS that uses the SAML provider you just created and grant AWS service and resource access to that role.
In the AWS IAM console, click Roles.
Click the Create role button.
Under "Select type of trusted entity" click SAML 2.0 federation.
Select the sso SAML provider you created earlier from the drop-down for "SAML provider".
Select Allow programmatic and AWS Management Console access. Values should automatically populate for "Attribute" and "Value".
Click Next: Permissions.
Select the policies you want attached to the IAM role. In this example the AWS "AdministratorAccess" policy is attached to the role. Click Next: Tags after selecting the policies.
On the "Add tags" page you can optionally add key-value pair tags with information about the role. Click Next: Review.
On the "Review" page enter a name into Role name. You may also enter Role description.
Click Create role. You'll return to the "Roles" page upon successful creation of the role.
If you'd like to change the default session time from one hour do the following:
Click on the name of the role you just created.
On the role page click Edit in the upper-right corner. A pop up will appear.
In the pop up under Maxium session duration use the dropdown to select the maximum amount of time you'd like a session to last when a user is assigned to this role.
Click Save changes.
Return to the Duo Admin Panel with the Amazon Web Services application open. Find the Service Provider section.
Enter your AWS account ID in the Account Number field. If you don't know your AWS account ID you can find it in the AWS console on the "My Account" page.
Enter sso into the Provider Name field. If you used a different provider name earlier than enter that name.
Enter the amount of time in seconds that you'd like the AWS session to last into Session Duration. This can be between 900 to 43200 seconds with a default of 3600. The number entered here must be the same or lower than the Maxium session duration set on the role in the AWS Admin Console.
Select the type of AWS account type that you have from the Account Type dropdown. If you're unsure, leave "AWS Regions" selected.
Under Role attributes you can type the name of the AWS role you defined earlier in the AWS Role field and which users should have access to that role by selecting Duo groups in the Duo Groups field. The members of those groups will be given access to that role in AWS.
If you have additional AWS roles you can click the + button next to the "Duo Groups" field to add additional rows.
AWS 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|
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.
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.
Scroll to the bottom of the page and click the Save button.
You can log into AWS using Duo Central, our cloud-hosted portal which allows users to access all of their applications in one spot. Link to AWS in Duo Central by adding it as an application tile. Once the tile has been added, log into Duo Central and click the tile for AWS.
You can also log on to AWS using the Duo SSO Login URL provided by under the "Metadata" section of the AWS application in the Duo Admin Panel (https://sso-abc1def2.sso.duosecurity.com/saml2/sp/DIABC123678901234567/metadata).
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.
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.
Successful verification of your primary credentials by Active Directory or a SAML IdP redirects back to Duo. Complete Duo two-factor authentication when prompted.
*Universal Prompt experience shown.
After authenticating you'll be forwarded to the AWS site with the appropriate IAM role access. If you are a member of multiple AWS IAM role groups, you have the opportunity to select the role to assume for your session.
Congratulations! Your AWS console users now authenticate using Duo Single Sign-On.
AWS does not support SP-initiated SSO login at this time.
To minimize additional Duo two-factor prompts when switching between AWS and your other Duo Single Sign-On SAML applications, be sure to apply a shared "Remembered Devices" policy to your SAML applications.