Using the SAML 2.0 standard, you can configure single sign-on (SSO) for a number of cloud apps. After you set up SSO, your users can use their Google Workspace credentials to sign in to an app using SSO.
Use SAML to set up SSO for Amazon Web Services
You must be signed in as a super administrator for this task.
Before you beginBefore configuring SSO, you must create a custom user attribute.
- Sign in with a super administrator account to the Google Admin console.
If you aren’t using a super administrator account, you can’t complete these steps.
- Go to Menu Directory > Users .
- Click More options Manage custom attributes.
- At the top, click Add Custom Attribute.
- In the Add custom fieldssection:
- For Category, enter Amazon.
- For Description, enter Amazon Custom Attributes.
- For Name, enter Role.
- Click Info typeand select Text.
- Click Visibilityand select Visible to user and admin.
- Click No. of valuesand select Multi-value.
-
Click Add.
The custom attribute appears in the Custom attributessection on the Manage user attributespage.
- Sign in with a super administrator account to the Google Admin console.
If you aren’t using a super administrator account, you can’t complete these steps.
- Download the identity provider metadata.
- Leave the Admin console open. You'll continue with the configuration in the Admin console after the setup steps in the app.
- Open an Incognito browser window and sign in to the AWS Management Console .
- Open the IAM console .
- Go to Identity Providers Add Provider.
- Click Provider Typeand select SAML.
- For Provider Name, enter a name (for example, GoogleWorkspace).
Note: The provider name can't contain spaces.
- Click Choose Fileand select the metadata file that you downloaded in Step 1.
- Click Add Provider.
On the Identity Providerspage, the provider name you entered, such as GoogleWorkspace, should appear in the list of identity providers.
- Click Roles Create role Trusted entity type SAML 2.0 federation.
- For SAML 2.0 federation, select the SAML provider name you previously added and choose an access option.
- Click Next.
- For Permissions policies, search for and choose policies to grant permissions to users who are signing in to Amazon Web Services using SSO (for example, AdministratorAccess).
- Click Next.
- In the Role detailssection, enter a Role name(for example, GoogleSSO).
- Click Create role.
- On the Rolespage, copy and save the Identity Provider ARN for the role name that you created in step 12.
This value is needed to configure the custom Amazon user attribute for each user in Step 4. - Click the role name that you previously created.
- On the Summarypage, copy and save the Role ARN.
This value is needed to configure the custom Amazon user attribute for each user in Step 4.
- Sign in with a super administrator account to the Google Admin console.
If you aren’t using a super administrator account, you can’t complete these steps.
-
- Click Add app Search for apps.
- For Enter app name, enter Amazon Web Services.
- In the search results, point to Amazon Web Servicesand click Select.
- In the Google Identity Provider detailswindow, click Continue.
On the Service provider detailspage, the app details are configured by default. - Click Continue.
- In the Attribute Mappingwindow, click Select fieldand map the following Google directory attributes to their corresponding
Amazon Web Services attributes. The https://aws.amazon.com/SAML/Attributes/RoleSessionName and https://aws.amazon.com/SAML/Attributes/Role attributes are required.
* The custom attribute that you created in the Before you begin section.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 - (Optional) To add additional mappings, click Add Mappingand select the fields that you need to map.
- (Optional) To enter group names that are relevant for this app:
- For Group membership (optional), click Search for a group, enter one or more letters of the group name, and select the group name.
- Add additional groups as needed (maximum of 75 groups).
- 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 .
- Click Finish.
Before you begin: To turn a service on or off for certain users, put their accounts in an organizational unit (to control access by department) or add them to an access group (to allow access for users across or within departments).
- Sign in with a super administrator account to the Google Admin console.
If you aren’t using a super administrator account, you can’t complete these steps.
-
- Click Amazon Web Services.
- Click User access.
-
To turn a service on or off for everyone in your organization, click On for everyoneor Off for everyone, and then click Save.
- (Optional) To turn a service on or off for an organizational unit:
- At the left, select the organizational unit.
- To change the Service status, select Onor Off.
- 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 Inheritto revert to the same setting as its parent, or click Saveto keep the new setting, even if the parent setting changes.
Learn more about organizational structure .
- (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 .
- Ensure that your Amazon Web Services user account email domains match the primary domain of your organization’s managed Google Account.
- For each user signing in to Amazon Web Services using SSO, configure the custom user attribute that you previously created:
- On the user's account page, click User informationthe Amazon custom attribute.
- For Role, enter the Role ARN and the Identity Provider ARN that you copied in Step 2, separated by a comma. For example:
arn:aws:iam::ACCOUNT_NUMBER:role/GoogleSSO,arn:aws:iam::ACCOUNT_NUMBER:provider/GoogleWorkspace
- Click Save.
Amazon Web Services supports only identity provider-initiated SSO.
Verify identity provider-initiated SSO
Before you begin: Make sure you're signed in to the account where you configured Amazon Web Services.
- Sign in with a super administrator account to the Google Admin console.
If you aren’t using a super administrator account, you can’t complete these steps.
-
- Click Amazon Web Services.
- In the Amazon Web Servicessection, click Test SAML Login.
The app should open in a separate tab. If it doesn’t, troubleshoot the error message and try again. For details on troubleshooting, go to SAML app error messages .
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.
