Using Google SSO with Amazon Business

In this article I use "Amazon" to refer to Business as opposed to Amazon Web Services (AWS).

Most of the documentation available for using Google Workspace (formerly GSuite) as an single sign-on (SSO) identity provider (IdP) for Amazon pertains to AWS, not Business. We started looking at single-sign-on for Amazon in order to automatically create new purchasing accounts for employees. I have set up SSO for many cloud platforms using Google as the IdP and all have been straightforward until now. While Amazon does have documentation for setting up SSO, it is not specific to any identity provider, let alone Google Workspace. As I learned, there are a few configuration options that are either not specified or are wrong in the Amazon documentation. I have therefore written this tutorial to help others setup SSO for Business using Google Workspace as an IdP.

A big thanks to the support teams at Google (thanks David!) and Amazon for their patience and persistance in getting this integration to work.


Start in Google Workspace

  1. Once signed into Google Workspace, go to Apps > SAML Apps
  2. Click on Add App > Add custom SAML app
  3. Enter a name for the app (e.g. Amazon Business) and click Continue
  4. Download the IdP (identity provider) metadata file. The IdP metadata file contains all of the information in Option 2 and it is all available in plan text after the initial setup.
  5. Click Continue

Switch to Amazon

  1. Sign into Amazon Business using an administrator account
  2. Hover over the "Hello, " towards the top of the screen and click on System Integrations
  3. Click Setup under Single Sign-On (SSO)
  4. Select Google gSuite from the dropdown (as of this post, Amazon is still using gSuite not Google Workspace)
  5. Click Next
  6. Select a default group and buying role for new users
  7. Upload your metadata file from Google (GoogleIDPMetadata.xml)
  8. The next page will confirm the details from the metadata file. Click Next
  9. Set the attribute mapping to match the screenshot. Click the "Add a field" link above the next button to add additional fields.
  10. The attributes should be mapped as follows: Amazon Attribute Map
  11. Click Next

Switch to Google

  1. We left off on the Service provider details page. Copy the SSO URL from Amazon and paste it into the ACS URL field. It should be:
  2. Enter "" into the Entity ID field in Google (without the quotation marks)
  3. Leave the Start URL field blank
  4. Leave the Signed response checkbox unchecked.
  5. In the Name ID section, set the Name ID format to EMAIL and the Name ID to Basic Information > Primary email
  6. Click continue
  7. On the Attributes screen, click ADD MAPPING three times
  8. In the first attribute, select Primary email from the dropdown on the left and type "Email" on the right.
  9. In the second attribute, select First name from the dropdown on the left and type "First Name" on the right.
  10. In the third attribute, select Last name from the dropdown on the left and type "Last Name" on the right.
  11. Amazon Attribute Map
  12. The attribute names are case sensitive, so double check and click finish
  13. Click on the User access section on the SAML app overview page
  14. Select "ON for everyone", turn on by organizational unit
  15. Click Save
  16. Click on the "Service status" header or "Amazon Business" in the top-left of the screen to go back to the overview page

Switch to Amazon

  1. Back on Amazon's website, check the "I confirm that Amazon's metadata has been configured on my IDP"
  2. Click the orange "start testing" button.
  3. If the test succeeds, click activate to complete the setup. Once you activate the connection, you will not be able to deactivate it or change SSO providers without contacting Amazon's customer service.

Google Settings

User Access

ON for everyone

*You can also turn it on for certain organization units only.

Service Provider details

Entity ID:
Start URL: (blank)
Signed response: unchecked

Certificate: make sure that a certificate is selected

Name ID format: EMAIL
Name ID: Basic Information > Primary email

SAML attribute mapping

Basic Information > Primary email: Email
Basic Information > First name: First Name
Basic Information > Last name: Last Name

Amazon Settings


The "Signing Certificate Public Key" should match your certificate in Google Workspace

New user account defaults

Choose the default group and role for new users.

Connection data

This should automatically populate from the Google metadata file. It should look something like:


Attribute mapping

Unique ID: Email
Email: Email
First Name: First Name
Last Name: Last Name

Amazon connection data


Previous: Microsoft's reversal on password expiration
Next: Installing a LibreSpeed Speedtest Server on CentOS