---
title: "How To Enable Single Sign-On for Amazon Web Services (AWS)"
slug: "sso-configurations-for-amazon-web-services"
description: "Set up SSO for Amazon Web Services (AWS) with Scalefusion. Follow our step-by-step guide to enable secure Single Sign-On (SSO) integration, simplifying access management for AWS resources."
tags: ["configure SSO for Microsoft", "Microsoft access management", "Microsoft Entra integration", "Microsoft Entra SSO", "Scalefusion SSO setup", "sso for microsoft 365", "SSO for Microsoft cloud apps", "SSO with Scalefusion"]
updated: 2026-10-28T13:17:42Z
published: 2026-10-28T13:17:42Z
canonical: "help.scalefusion.com/sso-configurations-for-amazon-web-services"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.scalefusion.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How to Setup Amazon Web Services (AWS) SSO (Single Sign-On) Integration

This document provides a step-by-step guide for setting up SSO Configuration to configure AWS IAM Identity center, allowing users to sign in to Amazon Web Services (AWS) using their OneIdP credentials and securely access these services.

## Pre-requisites

1. The Custom Domain for which you are authorising, should be [verified](/docs/setup-oneidp-2#custom-domain) through OneIdP.
2. Users belonging to custom domain should be added to Scalefusion Dashboard and [migrated](/docs/setup-oneidp-2#actions-on-directory) to OneIdP.
3. IT Admins should have access to Amazon Web Service’s (Service Providers') admin console.
4. [Users should be added](/v1/docs/sso-configurations-for-amazon-web-services#add-users-on-aws-portal) to AWS portal

## Create SSO Configuration for AWS

1. Sign in to Scalefusion Dashboard and navigate to **OneIdP >** **SSO Configuration**
2. Click on **New SSO Configuration** button on top right.

![aws sso](https://cdn.document360.io/175c0eac-012f-4410-bdc5-ac60794f82d8/Images/Documentation/Step 1(2).png)
3. After clicking New SSO Configuration, a window will appear. Search for **Amazon Web Services** in the list, select it, and then click **Configure**.

![](https://cdn.document360.io/175c0eac-012f-4410-bdc5-ac60794f82d8/Images/Documentation/image-BWQPE0EM.png)
4. This opens the **SSO Configuration** **wizard** with the following tabs on the left panel:
  1. [Application Basics](/v1/docs/sso-configurations-for-microsoft-365-entra#application-basics)
  2. [SSO Scope Management](/v1/docs/sso-configurations-for-microsoft-365-entra#sso-scope-management)
  3. [Permissions](/v1/docs/sso-configurations-for-microsoft-365-entra#permissions)
  4. [SSO Settings](/v1/docs/sso-configurations-for-microsoft-365-entra#sso-settings)
  5. [Conditional Access](/v1/docs/sso-configurations-for-microsoft-365-entra#conditional-access)
  6. [User Facing Messages](/v1/docs/sso-configurations-for-microsoft-365-entra#user-facing-messages) Navigate to each tab and enter required details. You can navigate to next tab only after you have entered complete details in the current section. All are explained in detail below.

### **Application Basics**

Configure basic application details by entering the following:

- **Enter Application Name:** Enter a name for your App which will be an identifier for your configuration. The name must be at-least 5 characters long. The maximum allowed length is 128 characters.
- **Select Hosting Type:** This will be pre-selected as **Cloud**
- **Select Domains:** All the custom domains you have configured and verified using OneIdP, will be listed here. Select the domain(s) which you want to be SAML SSO enabled.
- **Select Authentication Type:** This will be pre-selected as **SAML**.
- **Enter Login URL:** Provide URL that you use to sign in to that service. In case of AWS, it will be pre-populated as [https://aws.amazon.com](https://aws.amazon.com) Once you have entered all details click **Next**

![](https://cdn.document360.io/175c0eac-012f-4410-bdc5-ac60794f82d8/Images/Documentation/image-XU7D2B6J.png)

### **SSO Scope Management**

With SSO scope management you can configure the procedure for managing the users who will be accessing this application. It basically allows how SAML settings for the users are going to be managed. Following are the settings:

#### **User assignment**

SSO Configuration would allow only assigned users to access the app. Choose one from the following options:

1. **Allow all users imported to Scalefusion to access the application:** All users (belonging to the domain) imported to Scalefusion and migrated to OneIdP will be allowed to access the application.
2. **Allow only assigned users to access the application:** Only the user(s) whom you have assigned the SSO configuration, will be allowed to access the application. With this option, after SSO configuration is created, you need to manually select and assign the users.
  1. **Revoke access for all users once when the configuration is saved**: If this is checked, the access is revoked from the users who are currently assigned with the configuration. As a result, it will invalidate all user sessions and logout users from their current running session. ![sso aws](https://cdn.document360.io/175c0eac-012f-4410-bdc5-ac60794f82d8/Images/Documentation/image-1718194238002.png)

#### **Enforcement Rules**

From here, you can configure and enforce users that at what point of time SSO Configuration should invalidate the **current** session and logout users. Following options can be selected:

1. **Immediately on User Assignment and post grace period if applied:** Once SSO configuration is assigned to user
2. **Immediately on User Un-Assignment:** When user is unassigned the SSO configuration
3. **Immediately on Deleting this configuration:** When SSO configuration is deleted from Scalefusion Dashboard

> [!WARNING]
> Users will not get logged out in case of Amazon Web Services

![single sign-on aws](https://cdn.document360.io/175c0eac-012f-4410-bdc5-ac60794f82d8/Images/Documentation/image-1725005574835.png)

### **Permissions**

Here, you do not need to grant any additional permissions. Click **Next** to go to the next step.

![sso in aws](https://cdn.document360.io/175c0eac-012f-4410-bdc5-ac60794f82d8/Images/Documentation/image-ZTAN0S02.png)

### SSO Settings

This section allows admins to configure the Service Provider (AWS) settings and obtain the SSO URLs which will be added on the AWS portal.

1. Enter the Service Provider details on Scalefusion Dashboard, as provided in the web-console of your service provider SSO/SAML section
  1. **Service Provider Entity ID:** If your service provider has given you an Entity ID, also known as an audience or identifier, please enter it here. Otherwise, leave it blank to have it automatically decoded from the incoming request.
  2. **Service Provider ACS URL:** If your service provider has provided an ACS URL, sometimes also called a destination or recipient, then please enter it here, else leave it blank to auto-decode it from the incoming request

![](https://cdn.document360.io/175c0eac-012f-4410-bdc5-ac60794f82d8/Images/Documentation/image-215NU9Y2.png)
  3. **SAML Subject Name Id Format & Value:** Most service providers accept Email as the SAML Subject NameID as the user identifier. Change this only if your service provider wants a different value. Here, select the following:
    1. **Select Service Provider Name Id Format:** Select **email_address** from the drop-down
    2. **Select OneIdP User Value:** Select **Username** from the drop-down ![aws sso setup](https://cdn.document360.io/175c0eac-012f-4410-bdc5-ac60794f82d8/Images/Documentation/image-KMYUAE1N.png)
  4. **Session Duration:** Configure the duration (in hours) after which the user will be asked to re-authorize. Make sure to select a value potentially higher than your Service providers' session value. It can be anywhere from 1 to 720 hours. By default it is set to 336.
2. **OneIdP SSO URL:** Copy this URL from Scalefusion Dashboard and paste it on Amazon Web Services console by following the steps below:
  1. Login to AWS portal and search for IAM Identity Center. In the search results, click on **IAM Identity Center** ![](https://cdn.document360.io/175c0eac-012f-4410-bdc5-ac60794f82d8/Images/Documentation/image-ZYOOLWA1.png)
  2. On the IAM Identity Center Setup page, click on Confirm Identity Source / Go to Settings ![](https://cdn.document360.io/175c0eac-012f-4410-bdc5-ac60794f82d8/Images/Documentation/image-GHUC563A.png)
  3. This opens Settings page. On Settings page, click on **Actions** drop-down and select **Change Identity Source**

![](https://cdn.document360.io/175c0eac-012f-4410-bdc5-ac60794f82d8/Images/Documentation/image-UBOGHKR3.png)
  4. On the next page, make sure **External Service Provider** is selected. Click **Next** to go to next page ![](https://cdn.document360.io/175c0eac-012f-4410-bdc5-ac60794f82d8/Images/Documentation/image-PSV90SLN.png)
  5. This will open **Configure External Identity Provider** page. Scroll down to go to **Identity Provider metadata** section. Under this section, enter the following:
    1. **IdP sign-in URL:** Copy the OneIdP SSO URL from Scalefusion Dashboard and paste it here
    2. **IdP issuer URL:** Copy the OneIdP SSO URL from Scalefusion Dashboard and paste it here
    3. **IdP Certificate:** Download OneIdP Verification Certificate from Scalefusion Dashboard (SSO Settings page) and upload it here. Click **Next** to go to next page

> [!NOTE]
> You can either provide IdP sign-in and issuer URL, upload IdP Certificate or download metadata file from Scalefusion Dashboard (SSO Settings page) and upload it under IdP SAML metadata

![](https://cdn.document360.io/175c0eac-012f-4410-bdc5-ac60794f82d8/Images/Documentation/image-KUKMPLZV.png)
  6. On the next page, review and confirm all the details. After reviewing, enter **ACCEPT** in the last field and click on **Change Identity Source** ![](https://cdn.document360.io/175c0eac-012f-4410-bdc5-ac60794f82d8/Images/Documentation/image-6UW1T059.png)
3. Now, on Scalefusion Dashboard, click **Next** in **SSO Settings**

### Conditional Access

From this section you can define the additional conditions on the basis of which users will be allowed/disallowed from accessing the application on device. This is divided into following sections:

1. Conditional Access Settings
2. Access Exceptions

#### Conditional Access Settings

**Device Policy**

1. **For Android, iOS/iPad OS, Windows & macOS, Linux, Chrome OS:** Choose one from the following two conditions:
  1. **Only if the device is managed by Scalefusion:** The application will be accessible only on devices managed (enrolled) by Scalefusion.
  2. **If the device is managed by Scalefusion or an OTP using Scalefusion Authenticator app from a managed device:** The application is accessible if any of the following conditions is met:
    1. **Device is managed by Scalefusion:** If device is managed you will not be asked to enter OTP for authentication, or
    2. If device is **unmanaged**, OTP is required for authentication. OTP can be taken from **Authenticator** app installed on a Scalefusion managed device.
  3. **Allow users to access by setting up MFA using third party authenticator app or OTP sent on email:** This option is activated only when Multi-factor Authentication is enabled in [Directory Settings](/docs/directory-settings). **Note:** The left side panel is for configuring Device Policy on **Android & iOS/iPad OS** and right side is for **Windows & macOS** and **Linux, ChromeOS** below them. Hence, you can configure separate device policies based on platform.
  4. **Skip Password on Scalefusion managed devices:** When enabled, this option allows users to access applications on managed devices without the need to enter a password during sign-in.

![](https://cdn.document360.io/175c0eac-012f-4410-bdc5-ac60794f82d8/Images/Documentation/image-A67WPMAL.png)

**For ChromeOS:** Choose one from the following two conditions:
    1. **Allow users to sign in using an OTP from Scalefusion authenticator app:** OTP can be taken from Authenticator app installed on a Scalefusion managed device.
    2. **Allow users to access by setting up MFA using third party authenticator app or OTP sent on email:**

> [!NOTE]
> Note:
> 
> This option will be enabled if MFA is enabled in [Directory Settings](/docs/directory-settings).
      1. OTP is required for authentication. OTP can be taken from any 3rd party authenticator app or an OTP received via email, based on the MFA settings in Directory Settings.
    3. **Allow access using email and password without MFA:** Authorization check will not happen, and users can login directly with their email and password.
    4. **Block Access:** When enabled, this setting prevents the user from accessing ChromeOS.

![](https://cdn.document360.io/175c0eac-012f-4410-bdc5-ac60794f82d8/Images/Documentation/image-FO1DN1ML.png)

#### **Browser Policy**

From here, you can select one or more browsers and specify minimum versions on which you want to allow the access to the application. Following are the options:

- All Browsers
- Google Chrome with minimum version
- Microsoft Edge with minimum version
- Safari with minimum version
- Mozilla Firefox with minimum version

**Important Points on Browser Policy:**

1. By default all browsers are allowed.
2. Only major versions are validated. For eg. if you mention browser version: 23.5.8.10 then the respective browser with minimum major version(23) will be allowed. After configuring Device Policy and Browser Policy, click **Next** ![](https://cdn.document360.io/175c0eac-012f-4410-bdc5-ac60794f82d8/Images/Documentation/image-00NVEL7K.png)

#### Access Exceptions

From this section you can configure the exceptions where the users are allowed to access the applications even if the conditions are not met. In general, these exceptions will be useful or addresses scenarios where :

1. IT Admins have setup Android Enterprise using Google Workspace Or
2. IT Admins have setup Apple User Enrollment with ABM/ASM federated to Google Workspace

Following are the exceptions that can be configured:

1. **Enrollment Exceptions**
  1. **Allow users to access the application till they enroll their first device:** Allows users to access the application till they enroll at-least one device. This option is helpful in conditions where the enrollment steps requires them to authenticate with the service provider. With this, you can also configure the following:
    1. **Maximum sessions allowed per user:** Configure no. of sessions that should be exempted. It can range from 1 to 3. Ideally 1 session per user is recommended.
    2. **Configure the OS where the exceptions are applied:** Select the platform(s) on which this exemption would be allowed to users.
2. **User Exceptions** Here you can add the users who are always exempted from the conditions and will never be asked to manage their device. Enter comma separated email addresses of users or click on Add Users on the right and in the new window, select the users who should be exempted. **Note:** These users still need to sign in with their OneDirectory credentials if they fall under the SSO Scope, however the conditions will not be enforced.
3. **User Group Exceptions** Here you can add the user groups which will always be exempted from the conditions and will never be asked to manage their device. Enter comma separated User Groups or click on **Add User Groups** on the right and in the new window, select the user groups which should be exempted.

> [!NOTE]
> The users belonging to such user groups still need to sign in with their OneDirectory credentials if they fall under the SSO Scope, however the conditions will not be enforced.

![](https://cdn.document360.io/175c0eac-012f-4410-bdc5-ac60794f82d8/Images/Documentation/image-3PUUHGES.png)

### User Facing Messages

User Facing Messages helps admins configure messages that end users may be shown when they are unable to access the application if any of the compliance conditions are not met. You can configure messages under following:

- **Configure Instructions for a Non-Compliant Device:** This message is shown when the device is not compliant and needs to be enrolled to Scalefusion
- **Configure Instructions for a Non-Compliant Browser:** Shown when the browser is not compliant as per configurations
- **Configure a Message to be displayed when Access is Denied:** Any other cases where access to application is denied.

There are some pre-configured messages displayed on Dashboard which you can edit as per requirement.

![](https://cdn.document360.io/175c0eac-012f-4410-bdc5-ac60794f82d8/Images/Documentation/image-1717744463733.png)

After configuring user facing messages, click on **Save**

The SSO configuration is created and listed on SSO Configuration page as a separate card with the name you have defined. You can create multiple SSO configurations in the same manner. ![](https://cdn.document360.io/175c0eac-012f-4410-bdc5-ac60794f82d8/Images/Documentation/image-FZQS9U2Z.png)

The [next document](/docs/managing-sso-configurations) explains how the configurations can be managed and other actions you can perform through SSO configurations.

### **Add Users** on AWS portal

1. 
  1. On AWS portal, navigate to Users section and click on **Add User**

![](https://cdn.document360.io/175c0eac-012f-4410-bdc5-ac60794f82d8/Images/Documentation/image-VFY2YDKS.png)
  2. On the page that opens, enter username, user’s email address and other details
  3. After entering, click **Next**.
  4. Review all user details and click **Add User**