Tutorial: Azure Active Directory integration with Amazon Web Services (AWS)

In this tutorial, you learn how to integrate Amazon Web Services (AWS) with Azure Active Directory (Azure AD). Integrating Amazon Web Services (AWS) with Azure AD provides you with the following benefits:

  • You can control in Azure AD who has access to Amazon Web Services (AWS).
  • You can enable your users to be automatically signed-in to Amazon Web Services (AWS) (Single Sign-On) with their Azure AD accounts.
  • You can manage your accounts in one central location - the Azure portal.

If you want to know more details about SaaS app integration with Azure AD, see What is application access and single sign-on with Azure Active Directory. If you don't have an Azure subscription, create a free account before you begin.

Amazon Web Services (AWS)

You can configure multiple Identifiers for multiple instances as below.

  • https://signin.aws.amazon.com/saml#1

  • https://signin.aws.amazon.com/saml#2

With these values, Azure AD will remove the value of # and send the correct value https://signin.aws.amazon.com/saml as the Audience URL in the SAML Token.

We recommend to use this approach for the following reasons:

a. Each application will provide you the unique X509 certificate and so each instance can have a different certificate expiry date and you can manage this on the individual AWS account basis. Overall certificate rollover will be easy in this case.

b. You can enable User Provisioning with AWS app in Azure AD and then our service will fetch all the roles from that AWS account. You don’t have to manually add or update the AWS roles on the app.

c. You can assign the app owner individually for the app who can manage the app directly in Azure AD.

Note

Make sure you use only Gallery App

Prerequisites

To configure Azure AD integration with Amazon Web Services (AWS), you need the following items:

  • An Azure AD subscription. If you don't have an Azure AD environment, you can get one-month trial here
  • Amazon Web Services (AWS) single sign-on enabled subscription

Note

To test the steps in this tutorial, we do not recommend using a production environment.

To test the steps in this tutorial, you should follow these recommendations:

  • Do not use your production environment, unless it is necessary.
  • If you don't have an Azure AD trial environment, you can get a one-month trial.

Note

If you want to integrate multiple AWS accounts to one Azure account for Single Sign on, please refer this article.

Scenario description

In this tutorial, you configure and test Azure AD single sign-on in a test environment.

  • Amazon Web Services (AWS) supports SP and IDP initiated SSO

To configure the integration of Amazon Web Services (AWS) into Azure AD, you need to add Amazon Web Services (AWS) from the gallery to your list of managed SaaS apps.

To add Amazon Web Services (AWS) from the gallery, perform the following steps:

  1. In the Azure portal, on the left navigation panel, click Azure Active Directory icon.

    The Azure Active Directory button

  2. Navigate to Enterprise Applications and then select the All Applications option.

    The Enterprise applications blade

  3. To add new application, click New application button on the top of dialog.

    The New application button

  4. In the search box, type Amazon Web Services (AWS), select Amazon Web Services (AWS) from result panel then click Add button to add the application.

    Amazon Web Services (AWS) in the results list

Configure and test Azure AD single sign-on

In this section, you configure and test Azure AD single sign-on with Amazon Web Services (AWS) based on a test user called Britta Simon. For single sign-on to work, a link relationship between an Azure AD user and the related user in Amazon Web Services (AWS) needs to be established.

To configure and test Azure AD single sign-on with Amazon Web Services (AWS), you need to complete the following building blocks:

  1. Configure Azure AD Single Sign-On - to enable your users to use this feature.
  2. Configure Amazon Web Services (AWS) Single Sign-On - to configure the Single Sign-On settings on application side.
  3. Create an Azure AD test user - to test Azure AD single sign-on with Britta Simon.
  4. Assign the Azure AD test user - to enable Britta Simon to use Azure AD single sign-on.
  5. Create Amazon Web Services (AWS) test user - to have a counterpart of Britta Simon in Amazon Web Services (AWS) that is linked to the Azure AD representation of user.
  6. Test single sign-on - to verify whether the configuration works.

Configure Azure AD single sign-on

In this section, you enable Azure AD single sign-on in the Azure portal.

To configure Azure AD single sign-on with Amazon Web Services (AWS), perform the following steps:

  1. In the Azure portal, on the Amazon Web Services (AWS) application integration page, select Single sign-on.

    Configure single sign-on link

  2. On the Select a Single sign-on method dialog, select SAML/WS-Fed mode to enable single sign-on.

    Single sign-on select mode

  3. On the Set up Single Sign-On with SAML page, click Edit icon to open Basic SAML Configuration dialog.

    Edit Basic SAML Configuration

  4. On the Basic SAML Configuration section, the application is pre-configured and the necessary URLs are already pre-populated with Azure. The user needs to save the configuration by clicking the Save button.

    image

  5. When you are configuring more than one instance, please provide Identifier value. From second instance onwards, please provide Identifier value in following format. Please use a # sign to specify a unique SPN value.

    https://signin.aws.amazon.com/saml#2

    Amazon Web Services (AWS) Domain and URLs single sign-on information

  6. Amazon Web Services (AWS) application expects the SAML assertions in a specific format. Configure the following claims for this application. You can manage the values of these attributes from the User Attributes section on application integration page. On the Set up Single Sign-On with SAML page, click Edit button to open User Attributes dialog.

    image

  7. In the User Claims section on the User Attributes dialog, configure SAML token attribute as shown in the image above and perform the following steps:

    Name Source Attribute Namespace
    RoleSessionName user.userprincipalname https://aws.amazon.com/SAML/Attributes
    Role user.assignedroles https://aws.amazon.com/SAML/Attributes
    SessionDuration "provide a value between 900 seconds (15 minutes) to 43200 seconds (12 hours)" https://aws.amazon.com/SAML/Attributes

    a. Click Add new claim to open the Manage user claims dialog.

    image

    image

    b. In the Name textbox, type the attribute name shown for that row.

    c. In the Namespace textbox, type the Namespace value shown for that row.

    d. Select Source as Attribute.

    e. From the Source attribute list, type the attribute value shown for that row.

    f. Click Ok

    g. Click Save.

  8. On the Set up Single Sign-On with SAML page, in the SAML Signing Certificate section, click Download to download the Federation Metadata XML from the given options as per your requirement and save it on your computer.

    The Certificate download link

  9. On the Set up Amazon Web Services (AWS) section, copy the appropriate URL(s) as per your requirement.

    Copy configuration URLs

    a. Login URL

    b. Azure AD Identifier

    c. Logout URL

Configure Amazon Web Services (AWS) Single Sign-On

  1. In a different browser window, sign-on to your Amazon Web Services (AWS) company site as administrator.

  2. Click AWS Home.

    Configure Single Sign-On home

  3. Click Identity and Access Management.

    Configure Single Sign-On Identity

  4. Click Identity Providers, and then click Create Provider.

    Configure Single Sign-On Provider

  5. On the Configure Provider dialog page, perform the following steps:

    Configure Single Sign-On dialog

    a. As Provider Type, select SAML.

    b. In the Provider Name textbox, type a provider name (for example: WAAD).

    c. To upload your downloaded metadata file from Azure portal, click Choose File.

    d. Click Next Step.

  6. On the Verify Provider Information dialog page, click Create.

    Configure Single Sign-On Verify

  7. Click Roles, and then click Create role.

    Configure Single Sign-On Roles

  8. On the Create role page, perform the following steps:

    Configure Single Sign-On Trust

    a. Select SAML 2.0 federation under Select type of trusted entity.

    b. Under Choose a SAML 2.0 Provider section, select the SAML provider you have created previously (for example: WAAD)

    c. Select Allow programmatic and AWS Management Console access.

    d. Click Next: Permissions.

  9. On the Attach Permissions Policies dialog, please attach appropriate policy as per your organization. Click Next: Review.

    Configure Single Sign-On Policy

  10. On the Review dialog, perform the following steps:

    Configure Single Sign-On Review

    a. In the Role name textbox, enter your Role name.

    b. In the Role description textbox, enter the description.

    c. Click Create Role.

    d. Create as many roles as needed and map them to the Identity Provider.

  11. Use AWS service account credentials for fetching the roles from AWS account in Azure AD User Provisioning. For this, open the AWS console home.

  12. Click on Services -> Security, Identity& Compliance -> IAM.

    fetching the roles from AWS account

  13. Select the Policies tab in the IAM section.

    fetching the roles from AWS account

  14. Create a new policy by clicking on Create policy for fetching the roles from AWS account in Azure AD User Provisioning.

    Creating new policy

  15. Create your own policy to fetch all the roles from AWS accounts by performing the following steps:

    Creating new policy

    a. In the “Create policy” section click on “JSON” tab.

    b. In the policy document, add the below JSON.

    
    {
    
    "Version": "2012-10-17",
    
    "Statement": [
    
    {
    
    "Effect": "Allow",
    
    "Action": [
    
    "iam:ListRoles"
    
    ],
    
    "Resource": "*"
    
    }
    
    ]
    
    }
    
    

    c. Click on Review Policy button to validate the policy.

    Define the new policy

  16. Define the new policy by performing the following steps:

    Define the new policy

    a. Provide the Policy Name as AzureAD_SSOUserRole_Policy.

    b. You can provide Description to the policy as This policy will allow to fetch the roles from AWS accounts.

    c. Click on “Create Policy” button.

  17. Create a new user account in the AWS IAM Service by performing the following steps:

    a. Click on Users navigation in the AWS IAM console.

    Define the new policy

    b. Click on Add user button to create a new user.

    Add user

    c. In the Add user section, perform the following steps:

    Add user

    • Enter the user name as AzureADRoleManager.

    • In the Access type, select the Programmatic access option. This way the user can invoke the APIs and fetch the roles from AWS account.

    • Click on the Next Permissions button in the bottom right corner.

  18. Now create a new policy for this user by performing the following steps:

    Add user

    a. Click on the Attach existing policies directly button.

    b. Search for the newly created policy in the filter section AzureAD_SSOUserRole_Policy.

    c. Select the policy and then click on the Next: Review button.

  19. Review the policy to the attached user by performing following steps:

    Add user

    a. Review the user name, access type, and policy mapped to the user.

    b. Click on the Create user button at the bottom right corner to create the user.

  20. Download the user credentials of a user by performing following steps:

    Add user

    a. Copy the user Access key ID and Secret access key.

    b. Enter these credentials into Azure AD user provisioning section to fetch the roles from AWS console.

    c. Click on Close button at the bottom.

  21. Navigate to User Provisioning section of Amazon Web Services app in Azure AD Management Portal.

    Add user

  22. Enter the Access Key and Secret in the Client Secret and Secret Token field respectively.

    Add user

    a. Enter the AWS user access key in the clientsecret field.

    b. Enter the AWS user secret in the Secret Token field.

    c. Click on the Test Connection button and you should able to successfully test this connection.

    d. Save the setting by clicking on the Save button at the top.

  23. Now make sure that you enable the Provisioning Status On in the Settings section by making the switch on and then clicking on the Save button at the top.

    Add user

Create an Azure AD test user

The objective of this section is to create a test user in the Azure portal called Britta Simon.

  1. In the Azure portal, in the left pane, select Azure Active Directory, select Users, and then select All users.

    The "Users and groups" and "All users" links

  2. Select New user at the top of the screen.

    New user Button

  3. In the User properties, perform the following steps.

    The User dialog box

    a. In the Name field enter BrittaSimon.

    b. In the User name field type brittasimon@yourcompanydomain.extension
    For example, BrittaSimon@contoso.com

    c. Select Show password check box, and then write down the value that's displayed in the Password box.

    d. Click Create.

Assign the Azure AD test user

In this section, you enable Britta Simon to use Azure single sign-on by granting access to Amazon Web Services (AWS).

  1. In the Azure portal, select Enterprise Applications, select All applications, then select Amazon Web Services (AWS).

    Enterprise applications blade

  2. In the applications list, type and select Amazon Web Services (AWS).

    The Amazon Web Services (AWS) link in the Applications list

  3. In the menu on the left, select Users and groups.

    The "Users and groups" link

  4. Click the Add user button, then select Users and groups in the Add Assignment dialog.

    The Add Assignment pane

  5. In the Users and groups dialog select Britta Simon in the Users list, then click the Select button at the bottom of the screen.

  6. If you are expecting any role value in the SAML assertion then in the Select Role dialog select the appropriate role for the user from the list, then click the Select button at the bottom of the screen.

  7. In the Add Assignment dialog click the Assign button.

Create Amazon Web Services (AWS) test user

The objective of this section is to create a user called Britta Simon in Amazon Web Services (AWS). Amazon Web Services (AWS) doesn't need a user to be created in their system for SSO, so you don't need to perform any action here.

Test single sign-on

In this section, you test your Azure AD single sign-on configuration using the Access Panel.

When you click the Amazon Web Services (AWS) tile in the Access Panel, you should be automatically signed in to the Amazon Web Services (AWS) for which you set up SSO. For more information about the Access Panel, see Introduction to the Access Panel.

Known issues

  • In the Provisioning section, the Mappings sub-section will show a "Loading..." message and never display the attribute mappings. The only provisioning workflow supported today is the import of roles from AWS into Azure AD for selection during user/group assignment. The attribute mappings for this are predetermined and not configurable.

  • The Provisioning section only supports entering one set of credentials for one AWS tenant at a time. All imported roles are written to the appRoles property of the Azure AD servicePrincipal object for the AWS tenant. Multiple AWS tenants (represented by servicePrincipals) can be added to Azure AD from the gallery for provisioning, however there is a known issue with not being able to automatically write all of the imported roles from the multiple AWS servicePrincipals used for provisioning into the single servicePrincipal used for single sign-on. As a workaround, the Microsoft Graph API can be used to extract all of the appRoles imported into each AWS servicePrincipal where provisioning is configured. These role strings can be subsequently added to the AWS servicePrincipal where single sign-on is configured.

Additional resources