AWS SSO Identity Store
Browse all Amazonaws APIs★ Only Publicly Available OpenAPI DocumentIdentity AuthDirectory Serviceshmac19 EndpointsREST
For Agents
Create, update, and remove users, groups, and group memberships in the AWS IAM Identity Center directory used for single sign-on across AWS accounts and applications.
Use for: I need to create a new user in IAM Identity Center for a contractor, Add an existing user to the engineers group, Find a user by their primary email address, List all groups in the Identity Store instance
Not supported: Does not handle permission set assignment, sign-in flows, or external IdP federation — use for IAM Identity Center user, group, and membership management only.
Jentic publishes the only available OpenAPI specification for AWS SSO Identity Store, keeping it validated and agent-ready. The Identity Store service backs AWS IAM Identity Center (formerly AWS SSO) and is the directory of users and groups that can be assigned permissions across AWS accounts and applications. The API covers full lifecycle management of users, groups, and group memberships across 19 operations and is the canonical place to programmatically manage identities for SSO-enabled AWS accounts.
Install Jentic One Beta
Connect the AWS SSO Identity Store to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AWS SSO Identity Store, 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 SSO Identity Store API.
Create and delete users in the IAM Identity Center directory
Create and delete groups and update group attributes
Add and remove users from groups via group membership records
Look up users and groups by attribute (email, display name, external ID)
List all users, groups, and memberships in an Identity Store instance
Update user attributes such as name, emails, addresses, and phone numbers
Check whether a specific user is a member of a specific group
Use Cases
Patterns agents use AWS SSO Identity Store API for, with concrete tasks.
★ Automated User Provisioning
Provision and deprovision SSO users programmatically when employees join or leave the organisation. CreateUser writes the user to the Identity Store, CreateGroupMembership adds them to the right groups, and DeleteUser removes them when they offboard. The whole flow runs from an HRIS or ticket system without operator clicks in the AWS console.
Call CreateUser with UserName, DisplayName, Emails, and Name attributes, then CreateGroupMembership for each group the new hire should belong to
Group-Based Access Audit
Audit who has access to what by listing every group and walking its memberships. ListGroups, ListGroupMemberships, and DescribeUser together produce a full picture of the directory state. This is useful for periodic access reviews and for automated drift detection against an HR system of record.
Call ListGroups for the IdentityStoreId, then for each group call ListGroupMemberships and resolve each MemberId via DescribeUser
External Identity Reconciliation
Reconcile identities created elsewhere — for example by an external IdP or HRIS — with the Identity Store. GetUserId and GetGroupId resolve users and groups by AlternateIdentifier, including external IDs and unique attributes, so reconciliation logic can detect duplicates and merge or update without creating drift.
Call GetUserId with AlternateIdentifier set to UniqueAttribute on attribute path emails.value to resolve an SSO user from an email
AI Agent Identity Operations
Through Jentic, an AI agent can act as an identity operator — onboarding users, adjusting group memberships in response to ticket approvals, and answering 'who has access to X' questions in natural language. The 19 Identity Store operations are exposed as Jentic tools so the agent picks the right one from intent.
Search Jentic for 'add user to aws sso group', load the CreateGroupMembership schema, and execute it with IdentityStoreId, GroupId, and a MemberId reference to the user
Key Endpoints
19 endpoints — jentic publishes the only available openapi specification for aws sso identity store, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/
CreateUser — create a new user in the Identity Store
POST
/
DeleteUser — delete a user
POST
/
CreateGroup — create a new group
POST
/
DeleteGroup — delete a group
POST
/
CreateGroupMembership — add a user to a group
POST
/
DeleteGroupMembership — remove a user from a group
POST
/
GetUserId — resolve a user by AlternateIdentifier
POST
/
ListGroupMemberships — list members of a group
POST
/
CreateUser — create a new user in the Identity Store
POST
/
DeleteUser — delete a user
POST
/
CreateGroup — create a new group
POST
/
DeleteGroup — delete a group
POST
/
CreateGroupMembership — add a user to a group
POST
/
DeleteGroupMembership — remove a user from a group
POST
/
GetUserId — resolve a user by AlternateIdentifier
POST
/
ListGroupMemberships — list members of a group
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
AWS access keys for Identity Store are stored encrypted in the Jentic vault. Agents never see the raw credentials — Jentic signs each request with SigV4 server-side.
Intent-based discovery
Agents search Jentic with intents like 'create aws sso user' or 'add user to group' and get the matching Identity Store operation back with its input schema.
Time to first call
Direct integration: 1 day to wire up the AWS SDK and IAM policies for identity operations. Through Jentic: under 30 minutes.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using AWS SSO Identity Store API through Jentic.
Why is there no official OpenAPI spec for AWS SSO Identity Store?
AWS does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call AWS SSO Identity Store 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 SSO Identity Store API use?
The API uses AWS Signature Version 4 (HMAC) request signing with an AWS access key ID and secret access key. Through Jentic, AWS credentials are stored encrypted in the vault and the agent never holds raw access keys.
Can I add a user to a group with the Identity Store API?
Yes. Call CreateGroupMembership with the IdentityStoreId, the GroupId, and a MemberId object containing the UserId. To remove the membership later, call DeleteGroupMembership with the returned MembershipId.
What are the rate limits for the AWS SSO Identity Store API?
AWS applies per-account, per-region request quotas to Identity Store operations and these vary by call. List operations have higher throughput than mutation operations like CreateUser. Check AWS Service Quotas for current limits in your region.
How do I create a user through Jentic?
Search Jentic for 'create aws sso user', load the CreateUser schema, and execute with IdentityStoreId, UserName, DisplayName, Name, and Emails. The response returns the new UserId, which can be used immediately in CreateGroupMembership calls.
Does this API support SCIM for IdP synchronisation?
The Identity Store control-plane API is separate from the SCIM endpoint exposed by IAM Identity Center for IdP sync. Use this API for direct programmatic management when SCIM is not in use, or to read users and groups regardless of how they were provisioned.
GET STARTED