Amazon Quick’s desktop application can now use the same sign-in method an organization already uses for Quick on the web, AWS announced on November 2, 2026. With this shared sign-in path, administrators no longer need to register a separate OpenID Connect (OIDC) application with their identity provider or configure desktop-specific sign-in.
How administrators enable desktop access
An administrator must still add the desktop connector once in the Amazon Quick console. Users then enter their Quick account name in the desktop application, choose Sign In and complete authentication through their browser.
AWS says this works for accounts using IAM Identity Center, IAM federation or native Amazon Quick users. Once desktop access is enabled, users who can sign in to Quick on the web can also sign in to the desktop application.
What changes for identity teams
The practical benefit is one fewer identity-provider integration to configure when using shared sign-in. Adding the desktop connector remains a required administrative step, but creating a separate OIDC application is no longer a prerequisite for this path.
Organizations that want to manage desktop sign-in separately can still set up a dedicated identity-provider configuration. AWS names Microsoft Entra ID, Google Workspace, Okta and Ping Identity as examples.
For engineering teams, the setup decision is therefore whether to reuse existing Quick authentication or configure desktop sign-in separately—not whether every desktop deployment requires another identity-provider integration.
Availability and regional scope
AWS says Amazon Quick on desktop is available in Regions that support the full Amazon Quick feature set. The release notice does not list individual Regions, so teams should verify their target Region’s support before planning a rollout.
See the original announcement for availability and release details.