Jentic publishes the only available OpenAPI specification for Amazon Cognito Sync, keeping it validated and agent-ready. Amazon Cognito Sync stores and synchronizes user-scoped key-value data across a user's devices and the cloud. Each user has datasets containing string records that are merged on conflict and pushed to all signed-in devices via Amazon SNS push notifications. It is a legacy service - AWS now recommends AWS AppSync for new cross-device sync work - but it remains useful for apps already on Cognito Identity that need lightweight per-user state.
17 endpointsJentic publishes the only available OpenAPI specification for Amazon Data Lifecycle Manager, keeping it validated and agent-ready. Amazon Data Lifecycle Manager (DLM) automates the creation, retention, and deletion of Amazon EBS snapshots and AMI backups through declarative lifecycle policies. The API exposes a small surface - create, get, update, and delete policies, plus tag operations - that is purpose-built for treating backup schedules as code. Use it when an agent needs to enforce backup posture across many accounts or to programmatically rotate retention windows as compliance requirements change.
8 endpointsJentic publishes the only available OpenAPI specification for Amazon DocumentDB, keeping it validated and agent-ready. Amazon DocumentDB is a managed document database with MongoDB compatibility, designed to run document workloads at scale on AWS. The API covers the full control plane: clusters, instances, parameter groups, snapshots, subnet groups, global clusters, event subscriptions, and pending-maintenance actions. Use it when an agent needs to provision DocumentDB clusters, restore from a snapshot, scale instances, or manage cross-region global clusters without going through the AWS console.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Famazonaws.com" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Famazonaws.com" | 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.