AWS Single Sign-On

Name: AWS Single Sign-On API
Brand: AWS Single Sign-On
Availability: InStock

★ Only Publicly Available OpenAPI DocumentIdentity AuthAuthenticationapiKey4 EndpointsREST

For Agents

Exchange an IAM Identity Center bearer token for AWS account roles and short-lived credentials. Agents can list accounts, list roles, get role credentials, and log out.

Connect the AWS Single Sign-On to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AWS Single Sign-On, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with AWS Single Sign-On API.

List the AWS accounts the current bearer token has access to with ListAccounts

List the IAM roles assigned to a specific account via ListAccountRoles

Exchange a bearer token plus account and role for sigv4 credentials with GetRoleCredentials

Invalidate the current portal session with the Logout operation

GET STARTED

Start building with AWS Single Sign-On API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for AWS Single Sign-On, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for AWS Single Sign-On, keeping it validated and agent-ready. AWS IAM Identity Center (formerly AWS Single Sign-On) Portal is the runtime that lets users and tools list the AWS accounts and roles assigned to them and exchange a bearer token for short-lived sigv4 credentials. Agents can list accessible accounts, list roles within an account, fetch role credentials for use with other AWS APIs, and log out the current session. The four endpoints model the sign-in portal's read flow only — administration of permission sets and assignments is handled through the sso-admin API.

Use Cases

Patterns agents use AWS Single Sign-On API for, with concrete tasks.

★ Programmatic Federation from CLI or Custom Tooling

Tools that need temporary AWS credentials for IAM Identity Center users follow this flow: the user authenticates via the OIDC device flow (sso-oidc), the tool receives a bearer token, and then ListAccountRoles and GetRoleCredentials yield the AccessKeyId, SecretAccessKey, SessionToken needed to call other AWS APIs. The Logout operation revokes the active session.

Call ListAccounts with the bearer token, then ListAccountRoles for a chosen accountId, then GetRoleCredentials for roleName='ReadOnlyAccess' to obtain AccessKeyId, SecretAccessKey, and SessionToken.

Account and Role Discovery for Federated Users

Internal portals that surface 'which AWS environments can I access?' use ListAccounts and ListAccountRoles against the user's bearer token. The portal renders a list of (account, role) tuples and lets the user pick one to federate into, then calls GetRoleCredentials.

ListAccounts with the bearer token, then for the first account ListAccountRoles to display all assigned roles to the user.

Session Termination on Logout

When a user signs out of an internal tool, the application calls the SSO Logout operation with the bearer token to revoke the session at IAM Identity Center. Subsequent calls with that token then return Unauthorized.

Call the Logout operation with the active x-amz-sso_bearer_token header to revoke the user's portal session.

AI Agent Multi-Account Access via Jentic

AI agents using Jentic that operate across many AWS accounts can call SSO through Jentic to fetch fresh role credentials per account on demand. Through Jentic, the bearer token is held in the vault and short-lived credentials are produced inside Jentic — never exposed to the agent's prompt.

Search Jentic for 'get role credentials from aws sso', execute GetRoleCredentials for accountId and roleName, and use the returned RoleCredentials to call other AWS APIs through Jentic.

Key Endpoints

4 endpoints — jentic publishes the only available openapi specification for aws single sign-on, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/assignment/accounts#x-amz-sso_bearer_token

List AWS accounts assigned to the bearer token (ListAccounts)

GET

/assignment/roles#x-amz-sso_bearer_token&account_id

List roles assigned in a specific account (ListAccountRoles)

GET

/federation/credentials#role_name&account_id&x-amz-sso_bearer_token

Get short-lived role credentials (GetRoleCredentials)

POST

/logout#x-amz-sso_bearer_token

Invalidate the current portal session (Logout)

GET

/assignment/accounts#x-amz-sso_bearer_token

List AWS accounts assigned to the bearer token (ListAccounts)

GET

/assignment/roles#x-amz-sso_bearer_token&account_id

List roles assigned in a specific account (ListAccountRoles)

GET

/federation/credentials#role_name&account_id&x-amz-sso_bearer_token

Get short-lived role credentials (GetRoleCredentials)

POST

/logout#x-amz-sso_bearer_token

Invalidate the current portal session (Logout)

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The IAM Identity Center bearer token is stored encrypted in the Jentic vault. Jentic injects it into each SSO Portal call server-side and returns short-lived role credentials to the agent only when needed — the long-lived bearer token never enters the agent's prompt.

Intent-based discovery

Agents search by intent (for example, 'list aws accounts assigned to me' or 'get role credentials for an account') and Jentic returns the matching SSO operations with parameter schemas, letting the agent invoke ListAccounts or GetRoleCredentials directly.

Time to first call

Direct SSO integration: 1-2 days for OIDC device flow, token caching, and credential refresh logic. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

AWS SSO OIDC

OIDC device flow that issues the bearer token consumed by the SSO Portal

Call sso-oidc first to get the bearer token, then use the SSO Portal to list accounts and fetch role credentials

Complementary

AWS Single Sign-On Admin

Administrative API for permission sets and account assignments

Use sso-admin to configure who can access what; use the SSO Portal to consume those assignments at runtime

Alternative

AWS Security Token Service

AssumeRole-based federation for IAM principals; used when IAM Identity Center is not in scope

Pick STS AssumeRole when working with classic IAM users or roles; use SSO Portal when the workforce is managed in IAM Identity Center

FAQs

Specific to using AWS Single Sign-On API through Jentic.

Why is there no official OpenAPI spec for AWS Single Sign-On?

AWS does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call AWS Single Sign-On via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the AWS Single Sign-On use?

The SSO Portal accepts an IAM Identity Center bearer access token in the x-amz-sso_bearer_token header. The token is obtained from the sso-oidc CreateToken endpoint after completing the OAuth 2.0 device authorisation flow. Through Jentic, the token is stored in the vault and injected into each request server-side.

Can I exchange the bearer token for AWS API credentials?

Yes. GetRoleCredentials at /federation/credentials returns an AccessKeyId, SecretAccessKey, SessionToken, and expiration for the chosen (account_id, role_name) pair. Those credentials can then sign requests to any other AWS API.

What are the rate limits for the AWS Single Sign-On?

The SSO Portal applies standard AWS throttling — typical limits are a few requests per second per token for List operations and a slightly higher cap for GetRoleCredentials. Throttled calls return TooManyRequestsException; retry with exponential backoff.

How do I list every account a user can access through Jentic?

Through Jentic, search for 'list aws sso accounts', load the ListAccounts schema, and execute with the bearer token managed in the vault. Jentic returns the accountList array containing accountId, accountName, and emailAddress for each assigned account.

Is AWS Single Sign-On free?

IAM Identity Center is offered at no additional charge — you pay only for the underlying AWS resources accessed via the federated roles. SSO connections to external SaaS applications are also included.