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 endpointsJentic 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 endpointsStep 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 | shStep 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.
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.