AWS Single Sign-On Admin
Browse all Amazonaws APIs★ Only Publicly Available OpenAPI DocumentIdentity AuthDirectory ServicesapiKey37 EndpointsREST
For Agents
Configure IAM Identity Center permission sets, account assignments, and policy attachments. Agents can create permission sets, assign access, and attach managed or inline policies.
Use for: I need to create a new permission set in IAM Identity Center, Assign a permission set to a group for a specific AWS account, Attach the AdministratorAccess managed policy to a permission set, Add a customer-managed IAM policy reference to a permission set
Not supported: Does not authenticate end users, manage user directories, or issue session credentials — use only for configuring IAM Identity Center permission sets and account assignments.
Jentic publishes the only available OpenAPI specification for AWS Single Sign-On Admin, keeping it validated and agent-ready. The IAM Identity Center admin API configures who can access which AWS accounts with which roles. Agents can create and manage permission sets, attach AWS-managed and customer-managed IAM policies, define inline policies and permissions boundaries, assign permission sets to principals (users or groups) for specific AWS accounts, and provision those assignments across the organisation. The 37 operations cover permission sets, account assignments, instance access control attributes, inline policies, and managed policy attachments.
Install Jentic One Beta
Connect the AWS Single Sign-On Admin to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AWS Single Sign-On Admin, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: 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 | sh2
Step 2: 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 instanceJentic 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 Admin API.
Create and manage permission sets with CreatePermissionSet, UpdatePermissionSet, DeletePermissionSet
Assign a permission set to a principal in an AWS account using CreateAccountAssignment
Attach AWS-managed or customer-managed IAM policies to a permission set
Define inline policies and permissions boundaries on a permission set
Provision permission set changes to target accounts via ProvisionPermissionSet
Manage attribute-based access control with the InstanceAccessControlAttributeConfiguration operations
Track async assignment work with DescribeAccountAssignmentCreationStatus and ...DeletionStatus
Use Cases
Patterns agents use AWS Single Sign-On Admin API for, with concrete tasks.
★ Standardised Workforce Access Across AWS Accounts
Identity teams define permission sets such as 'ReadOnly', 'BillingAdmin', and 'DeveloperPowerUser' once, then assign them to groups in the directory for each target account. CreateAccountAssignment binds (principalId, principalType=GROUP, accountId, permissionSetArn), and ProvisionPermissionSet pushes the resulting role into the target account.
CreatePermissionSet 'ReadOnly', AttachManagedPolicyToPermissionSet with arn:aws:iam::aws:policy/ReadOnlyAccess, then CreateAccountAssignment for principalType=GROUP, principalId=<group-id>, accountId=<acct>, and ProvisionPermissionSet to roll it out.
Customer-Managed Policy Attachment for Tightly Scoped Access
When AWS-managed policies are too broad, teams reference customer-managed policies stored in the target accounts via AttachCustomerManagedPolicyReferenceToPermissionSet. This keeps policy authoring local to the account while letting a central permission set bind it to many principals.
AttachCustomerManagedPolicyReferenceToPermissionSet with the policy name and path 'finance-readonly'/'/' on the existing 'FinanceReadOnly' permission set, then ProvisionPermissionSet.
Attribute-Based Access Control
ABAC enabled on the IAM Identity Center instance lets the same permission set evaluate differently per user attribute (such as cost centre or team). CreateInstanceAccessControlAttributeConfiguration registers the attribute mapping; permission sets then reference those attributes in policy conditions.
CreateInstanceAccessControlAttributeConfiguration with AccessControlAttributes mapping 'CostCenter' to the user attribute path '${path:enterprise.costCenter}', then DescribeInstanceAccessControlAttributeConfiguration to verify the mapping.
AI Agent Access Provisioning via Jentic
AI agents using Jentic can answer 'who has access to account X?' or 'grant Sarah read-only access to the billing account' by calling sso-admin through Jentic. The agent searches by intent, loads the operation schema, and executes with vault-stored credentials.
Search Jentic for 'create account assignment iam identity center', execute CreateAccountAssignment for the target permission set ARN, then poll DescribeAccountAssignmentCreationStatus until Status=SUCCEEDED.
Key Endpoints
37 endpoints — jentic publishes the only available openapi specification for aws single sign-on admin, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/#X-Amz-Target=SWBExternalService.CreatePermissionSet
Create a new permission set
POST
/#X-Amz-Target=SWBExternalService.CreateAccountAssignment
Assign a permission set to a principal in an account
POST
/#X-Amz-Target=SWBExternalService.AttachManagedPolicyToPermissionSet
Attach an AWS-managed policy to a permission set
POST
/#X-Amz-Target=SWBExternalService.AttachCustomerManagedPolicyReferenceToPermissionSet
Attach a customer-managed policy reference
POST
/#X-Amz-Target=SWBExternalService.DescribePermissionSet
Fetch a permission set by ARN
POST
/#X-Amz-Target=SWBExternalService.DescribeAccountAssignmentCreationStatus
Track async assignment creation
POST
/#X-Amz-Target=SWBExternalService.DeleteAccountAssignment
Remove a permission-set assignment
POST
/#X-Amz-Target=SWBExternalService.CreatePermissionSet
Create a new permission set
POST
/#X-Amz-Target=SWBExternalService.CreateAccountAssignment
Assign a permission set to a principal in an account
POST
/#X-Amz-Target=SWBExternalService.AttachManagedPolicyToPermissionSet
Attach an AWS-managed policy to a permission set
POST
/#X-Amz-Target=SWBExternalService.AttachCustomerManagedPolicyReferenceToPermissionSet
Attach a customer-managed policy reference
POST
/#X-Amz-Target=SWBExternalService.DescribePermissionSet
Fetch a permission set by ARN
POST
/#X-Amz-Target=SWBExternalService.DescribeAccountAssignmentCreationStatus
Track async assignment creation
POST
/#X-Amz-Target=SWBExternalService.DeleteAccountAssignment
Remove a permission-set assignment
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
AWS access keys are stored encrypted in the Jentic vault. Each sso-admin call is signed with SigV4 server-side — the agent never holds the raw credential and policy ARNs flow through the call without leaving Jentic.
Intent-based discovery
Agents search by intent (for example, 'create permission set' or 'assign access to an aws account') and Jentic returns the matching sso-admin operations with input schemas, letting the agent invoke CreatePermissionSet or CreateAccountAssignment directly.
Time to first call
Direct sso-admin integration: 2-3 days for IAM, SigV4 signing, async assignment polling, and policy attachment ordering. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using AWS Single Sign-On Admin API through Jentic.
Why is there no official OpenAPI spec for AWS Single Sign-On Admin?
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 Admin 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 Admin use?
sso-admin uses AWS Signature Version 4 with IAM credentials and permissions on the sso:* and identitystore:* actions. Through Jentic, the AWS access key and secret are stored encrypted in the vault — Jentic signs each call before forwarding it to the regional sso-admin endpoint.
Can I create a permission set with both managed and inline policies?
Yes. CreatePermissionSet creates the empty set, then AttachManagedPolicyToPermissionSet attaches one or more AWS-managed policies and PutInlinePolicyToPermissionSet adds a custom inline policy. Customer-managed policies are referenced through AttachCustomerManagedPolicyReferenceToPermissionSet.
What are the rate limits for the AWS Single Sign-On Admin?
sso-admin applies standard AWS API throttling — most operations are limited to a few requests per second per account per region with brief burst capacity, and account-assignment operations are async. Throttled calls return ThrottlingException; retry with exponential backoff.
How do I assign a permission set to a group through Jentic?
Through Jentic, search for 'create account assignment iam identity center', load the CreateAccountAssignment schema, and execute with InstanceArn, TargetId (account id), TargetType=AWS_ACCOUNT, PermissionSetArn, PrincipalType=GROUP, and PrincipalId. Then poll DescribeAccountAssignmentCreationStatus with the returned RequestId until Status=SUCCEEDED.
Is AWS Single Sign-On Admin free?
IAM Identity Center is offered at no additional charge — you pay only for the underlying AWS resources that the assigned roles access. SSO connections to external SaaS applications are also included.
GET STARTED