Amazon Web Services cloud application

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. In the Admin console, go to Menu  DirectoryUsers.
3. At the top of Users list, click More options Manage custom attributes.
   Requires the Schema Management privilege.
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.

1. Sign in to your Google Admin console.

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

2. In the Admin console, go to Menu  SecurityAuthenticationSSO with SAML applications.
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.

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 > Add Provider.
3. For Provider Type, select SAML.
4. Enter a Provider Name, such as GoogleWorkspace.

   Note: The provider name cannot contain spaces.

5. Click Choose File and select the IDP metadata file you downloaded in Step 1 above.
6. Click Add Provider.

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

7. In the left sidebar, click Roles.
8. Click Create role.
9. For Trusted entity type, choose SAML 2.0 federation.
10. Under SAML 2.0 federation, choose the SAML provider name you added for Google Workspace (in our example, GoogleWorkspace) and choose an access option.
11. Click Next.
12. In Permissions policies, search for and choose policies to grant permissions to users logging in to AWS via Google SSO. Example: AdministratorAccess. 
13. Click Next.
14. Under Role details, enter a Role name, for example, GoogleSSO.
15. Click Create role.

    You're returned to the Roles page, where the new GoogleSSO role appears in the list.

16. Copy and save the Identity Provider ARN for the GoogleSSO role, which contains your AWS Account ID and the name of the identity provider (in our example, GoogleWorkspace). This value is needed to configure the custom Amazon user attribute for each user in Step 4 below.

    Example: arn:aws:iam::ACCOUNT_NUMBER:saml-provider/GoogleWorkspace

17. Click the GoogleSSO role to open the Summary page for the role.
18. Copy and save the role ARN. This contains your AWS Account ID and the name of the role (in our example, GoogleSSO). This value is needed to configure the custom Amazon user attribute for each user in Step 4 below.

    Example: arn:aws:iam::ACCOUNT_NUMBER:role/GoogleSSO.

Continue setup in the Google Admin console with Step 3.

1. Return to the browser tab where the Admin Console is open.
2. In the Admin console, go to Menu  AppsWeb and mobile apps.
3. Click Add appSearch for apps.
4. Enter Amazon Web Services in the search field.
5. In the search results, hover over the Amazon Web Services SAML app and click Select.
6. 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.

7. Click Continue.
8. 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.

9. (Optional) To enter group names that are relevant for this app:

   1. For Group membership (optional), click Search for a group, enter one or more letters of the group name, and select the group name.
   2. Add additional groups as needed (maximum of 75 groups).
   3. For App attribute, enter the corresponding groups attribute name of the service provider.

   Regardless of how many group names you enter, the SAML response includes only groups that a user is a member of (directly or indirectly). For more information, go to About group membership mapping.

10. Click Finish.

1. Sign in to your Google Admin console.

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

2. In the Admin console, go to Menu  AppsWeb and mobile apps.
3. Select Amazon Web Services.
4. Click User access.

5. To turn a service on or off 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. To change the Service status, select On or Off.
   3. Choose one:
      • If the Service status is set to Inherited and you want to keep the updated setting, even if the parent setting changes, click Override.
      • If the Service status is set to Overridden, either click Inherit to revert to the same setting as its parent, or click Save to keep the new setting, even if the parent setting changes.
        Note: Learn more about organizational structure.
7. (Optional) To turn on a service for a set of users across or within organizational units, select an access group. For details, go to Use groups to customize service access.
8. Ensure that your Amazon Web Services user account email IDs match with those in your Google domain.
9. For each user signing in to AWS via SSO, configure the custom user attribute you created in Before you begin:
   1. On the user's account page, click User information.
   2. Click the Amazon custom attribute.
   3. In the Role field, add the AWS Role ARN and the Provider ARN (copied in Step 2 above) separated by a comma, as follows: 

      arn:aws:iam::ACCOUNT_NUMBER:role/GoogleSSO,arn:aws:iam::ACCOUNT_NUMBER:provider/GoogleWorkspace

   4. Click Save.

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. In the Admin console, go to Menu  AppsWeb 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.

As a super administrator, you can automatically provision users in the Amazon Web Services application.