Amazon Quick Desktop with IAM IDC

Amazon Quick (Web version) supports native integration with IAM Identity Center.

Amazon Quick Suite is an application compatible with IAM Identity Center; administrators can manage Quick access permissions (admin/author/reader) based on IAM Identity Center group memberships through this native integration. While SAML 2.0 federation is possible, it is not recommended for most use cases.

However, there are limitations specific to "Quick Desktop."

Quick Desktop does not support authentication using IAM Identity Center's built-in directory directly. Amazon Quick Desktop requires an external OIDC IdP (Microsoft Entra ID, Okta, or Ping Identity) for enterprise login, and there is no authentication path available for customers relying on IAM Identity Center's built-in directory.

In short, the configuration looks like this:

❌ IAM Identity Center built-in directory → Quick Desktop (Direct integration not possible)

✅ External IdP (Entra ID/Okta/Ping)

↓ Federation

IAM Identity Center

↓

Quick Desktop (Integration possible via OIDC) Note: Regional constraints also apply.

Using Quick Desktop requires the Amazon Quick account's home region to be a supported AWS region; this is related to the previously mentioned "ID region" constraints. Cases have been reported where additional configuration is required if the IAM Identity Center home region differs from the region where Quick features are provided (often us-east-1).

Yes, Amazon Quick Desktop does work with AWS IAM Identity Center. The documentation confirms that all identity types are supported for Amazon Quick on desktop for enterprise deployments, including IAM Identity Center, IAM federation, and native Amazon Quick (username/password) users. The prerequisite is that you must have an AWS account with an active Amazon Quick subscription, and the Amazon Quick account's home region (identity region) must be in a supported AWS Region. While the setup documentation focuses on configuring OIDC application registrations with your identity provider, IAM Identity Center is explicitly listed as a supported identity type for the desktop application.
Sources
Setting up Amazon Quick on desktop for enterprise deployments - Amazon Quick

Yes, Amazon Quick Desktop works with IAM Identity Center — the setup depends on how your Identity Center is configured.

Quick Desktop authenticates using the OIDC protocol (with PKCE). Per the enterprise setup docs, all identity types are supported — including IAM Identity Center, IAM federation, and native Quick users. The practical path differs based on your IdP:

If your Identity Center is federated to an external IdP (Okta, Entra ID, Ping): You connect that OIDC-compatible IdP directly to Quick Desktop. This is the standard enterprise path:

1. Register a public OIDC client in your IdP (record the Client ID + OIDC endpoints).
2. Add an extension access in the Amazon Quick admin console using those values.
3. Create the extension on the Extensions page in the Amazon Quick console.
4. Distribute the desktop app; users sign in with "Continue with SSO."

If you're using the Identity Center native directory (no external IdP): You can bridge it using Amazon Cognito as the OIDC provider, then federate Cognito with Identity Center. There's a public step-by-step walkthrough here: https://aws-samples.github.io/sample-amazon-quick-suite-knowledge-hub/amazon-quick-on-desktop/

One requirement in both cases: the email address in your identity provider must exactly match the user's email in Amazon Quick, or identity mapping will fail.

Also worth confirming: your Quick account's home Region must support the full Quick feature set — Regions that only support QuickSight capabilities don't include Desktop. See Supported AWS Regions.

I did the Amazon Cognito as the OIDC provider, it works, my Quick desktop signs in using my AWS SSO, but its not syncing chats between the desktop and web, chats are synced between web and mobile, but nothing is synced to or from desktop, is there something I need to change, a setting? Or is this because I'm using Cognito?