AWS APIs
148 APIs6,711 Endpoints16 Categories
Categories
API Catalog(9 of 148)
Amazon CloudDirectory
Amazon Cloud Directory is a fully managed, hierarchical and graph-based directory store that scales to hundreds of millions of objects. The API lets you define one or more schemas with object facets and typed-link facets, create directories from those schemas, attach and detach objects in parent-child or graph relationships, build indexes for fast lookup, and run BatchRead and BatchWrite for high-throughput composite operations. Common uses include device registries, organisational hierarchies, course catalogs, network topologies, and policy graphs that need richer relationships than a flat user directory.
66 endpointsAmazon Cognito Identity
Jentic publishes the only available OpenAPI specification for Amazon Cognito Identity, keeping it validated and agent-ready. Amazon Cognito Identity (Federated Identities) issues scoped, temporary AWS credentials to mobile and web clients so applications can call AWS services without embedding long-lived secrets. Identity pools federate users from public providers like Apple, Google, Facebook, SAML, and OpenID Connect, or from unauthenticated guests, and map them to IAM roles for fine-grained access. The service uniquely identifies devices and maintains stable identity IDs across sign-ins for the lifetime of the application.
23 endpointsAmazon WorkLink
Jentic publishes the only available OpenAPI specification for Amazon WorkLink, keeping it validated and agent-ready. Amazon WorkLink was a managed service that provided secure access to internal websites and web apps from iOS and Android phones without VPN clients or app distribution. The API manages fleets, associates internal domains, configures audit streams, registers website certificate authorities, attaches SAML identity providers, and lists devices. The 33 operations include Associate/Disassociate verbs for domains, certificate authorities, and authorization providers, and the standard fleet CRUD plus device listing. Note: AWS ended Amazon WorkLink on April 30, 2024 — this spec is provided for legacy automation maintenance only.
33 endpointsAWS Resource Access Manager
Jentic publishes the only available OpenAPI specification for AWS Resource Access Manager (RAM), keeping it validated and agent-ready. RAM lets you share AWS resources across accounts and AWS Organizations: subnets, Transit Gateways, Route 53 Resolver rules, Capacity Reservations, License Manager configurations, and dozens more. The 34-operation API covers creating and updating resource shares, managing principal and resource associations, accepting or rejecting invitations, and authoring customer managed permissions. It is the control plane for centralized resource sharing in multi-account AWS estates.
34 endpointsAWS Security Token Service
Jentic publishes the only available OpenAPI specification for AWS Security Token Service, keeping it validated and agent-ready. AWS Security Token Service (STS) issues temporary, limited-privilege credentials for IAM users and federated identities. It supports role assumption, SAML federation, web identity federation (OIDC), and short-lived session tokens used to call other AWS APIs. STS exposes 8 core actions covering AssumeRole, AssumeRoleWithSAML, AssumeRoleWithWebIdentity, GetSessionToken, GetFederationToken, GetCallerIdentity, GetAccessKeyInfo, and DecodeAuthorizationMessage, with both GET and POST variants for each.
16 endpointsAWS Single Sign-On
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.
4 endpointsAWS Single Sign-On Admin
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.
37 endpointsAWS SSO Identity Store
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.
19 endpointsAWS SSO OIDC
Jentic publishes the only available OpenAPI specification for AWS SSO OIDC, keeping it validated and agent-ready. AWS IAM Identity Center OIDC implements the OAuth 2.0 Device Authorization Grant flow so that CLIs and native applications can sign users into IAM Identity Center without an embedded browser. The three operations let a tool register itself as an OIDC client, start a device authorisation, and exchange the resulting device code for an access token. The issued bearer token is then consumed by the IAM Identity Center Portal to list accounts and roles.
3 endpointsConnect Your Agent
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.