Amazon Web Services cloud application

You must be signed in as a super administrator for this task.

Using Security Assertion Markup Language (SAML), your users can use their Google Cloud credentials to sign in to enterprise-cloud applications.

Set up SSO via SAML for Amazon Web Services

Here's how to set up single sign-on (SSO) via SAML for the Amazon Web Services application.

Before you begin

Before setting up user provisioning, you need to create a custom user attribute for Amazon Web Services. Follow these steps:

  1. Sign in to your Google Admin console.

    Sign in using an account with super administrator privileges (does not end in @gmail.com).

  2. From the Admin console Home page, go to Users.
  3. At the top of Users list, click Manage user attributes "".
  4. At the top right, click Add Custom Attribute.
  5. Configure the custom attribute as follows:
    • Category: Amazon
    • Description: Amazon Custom Attributes

    For Custom fields, enter the following:

    • Name: Role
    • Info type: Text
    • Visibility: Visible to user and admin
    • No. of values: Multi-value
  6. Click Add.

    The new category appears in the Manage user attributes page.

Step 1: Get Google identity provider (IdP) information
  1. Sign in to your Google Admin console.

    Sign in using an account with super administrator privileges (does not end in @gmail.com).

  2. From the Admin console Home page, go to Securityand thenSet up single sign-on (SSO) for SAML applications.

    You must be signed in as a super administrator for this task.

  3. Download the IDP Metadata.

Leave the Admin console open, you'll continue with SSO configuration after performing the next step in the Amazon Management Console.

Step 2: Set up Amazon Web Services as a SAML 2.0 service provider (SP)
  1. In a new browser tab, log in to the AWS Management Console and open the IAM console at https://console.aws.amazon.com/iam/.
  2. In the navigation pane, select Identity Providers > Create Provider.
  3. For Provider Type, select SAML.
  4. Enter a Provider Name, such as GoogleApps.
  5. Click Choose File and select the IDP metadata file you downloaded in Step 1 above.
  6. Click Continue Step, then click Create.

    On the Identity Providers page, GoogleApps should appear in the table of IdPs.

  7. In the left sidebar, click Roles > Create a New Role.
  8. Under Set role name, enter a Role Name.
  9. Click Continue Step.
  10. On the Select Role Type page, under Role for Identity Provider Access, select Grant Web Single Sign-On (WebSSO) access to SAML providers
  11. Click Continue Step.
  12. On the Establish trust page, leave the default settings and click Next Step.
  13. Choose policies to grant permissions to users logging in to AWS via Google SSO. Example: AdministratorAccess. 
  14. Click Continue Step.
  15. On the following page, note the Role ARN, which contains your AWS Account ID and the name of the role.

    Example: arn:aws:iam::ACCOUNT_NUMBER:role/SSO

  16. Click Create the Role.
  17. Select your Google service from the identity providers list and note the Provider ARN. This contains your AWS Account ID and the name of the provider.

    Example: arn:aws:iam::ACCOUNT_NUMBER:saml-provider/GoogleApps.

  18. Click Save to save the Federated Web single sign-on configuration details.
Step 3: Set up Google as a SAML identity provider (IdP)
  1. Return to the browser tab where the Admin Console is open.
  2. From the Admin console Home page, go to Appsand thenWeb and mobile apps.
  3. Enter Amazon Web Services in the search field.
  4. In the search results, hover over the Amazon Web Services SAML app and click Select.
  5. On the  Google Identity Provider details page, click Continue.

    On the Service provider details page, the ACS URL and Entity ID values for Amazon Web Services are configured by default.

  6. Click Continue.
  7. On the Attribute Mapping page, click the Select field menu and map the following Google directory attributes to their corresponding Amazon Web Services attributes:
     
    Google directory attribute Amazon Web Services attribute
    Basic Information > Primary Email https://aws.amazon.com/SAML/Attributes/RoleSessionName
    Amazon > Role* https://aws.amazon.com/SAML/Attributes/Role

    (*) Custom attribute created in Before you begin above.

  8. Click Finish.
Step 4: Enable the Amazon Web Services app
  1. Sign in to your Google Admin console.

    Sign in using an account with super administrator privileges (does not end in @gmail.com).

  2. From the Admin console Home page, go to Appsand thenWeb and mobile apps.
  3. Select Amazon Web Services.
  4. Click User access.
  5. To turn on or off a service for everyone in your organization, click On for everyone or Off for everyone, and then click Save.

  6. (Optional) To turn a service on or off for an organizational unit:

    1. At the left, select the organizational unit.
    2. Select On or Off.
    3. Click Override to keep your setting if the service for the parent organizational unit is changed.
    4. If Overridden is already set for the organizational unit, choose an option:
      • Inherit—Reverts to the same setting as its parent.
      • Save—Saves your new setting (even if the parent setting changes).

    Learn more about organizational structure.

  7. (Optional) Turn on the service for a group of users.
    Use access groups to turn on a service for specific users within or across your organizational units. Learn more

  8. Ensure that your Amazon Web Services user account email IDs match with those in your Google domain.
Step 5: Verify that SSO is working between G Suite and Amazon Web Services (G Suite only)

Note: Make sure you're still signed in to the account where you configured Amazon Web Services.

  1. Sign in to your Google Admin console.

    Sign in using an account with super administrator privileges (does not end in @gmail.com).

  2. From the Admin console Home page, go to Appsand thenWeb and mobile apps.
  3. Select Amazon Web Services.
  4. At the top left, click Test SAML login

    Amazon Web Services should open in a separate tab. If it doesn’t, use the information in the resulting SAML error messages to update your IdP and SP settings as needed, then retest SAML login.

Step 6: Set up user provisioning

You don't need to set up user provisioning for Amazon Web Services.

AWS supports role based logins to all SAML 2.0 IdP (Identity Provider) authenticated federated users. Specify the role by mapping the attribute value https://aws.amazon.com/SAML/Attributes/Role to a custom attribute corresponding to the Amazon Web Services account. See Step 3 above.

After you create this role mapping, your SAML SSO enabled users can sign in to the AWS Management Console, to a specified AWS Identity and Access Management (IAM) role, without you having to create corresponding IAM users in the Management Console.

Refer to AWS documentation for more details on AWS role mapping.



Google, Google Workspace, and related marks and logos are trademarks of Google LLC. All other company and product names are trademarks of the companies with which they are associated.
Was this helpful?
How can we improve it?

Need more help?

Sign in for additional support options to quickly solve your issue