AWS APIs

148 APIs6,711 Endpoints16 Categories

API Catalog(12 of 148)

Amazon Cognito Sync

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 endpoints

Amazon Data Lifecycle Manager

Jentic 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 endpoints

Amazon DocumentDB with MongoDB compatibility

Jentic 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.

106 endpoints

Amazon DynamoDB Accelerator (DAX)

Jentic publishes the only available OpenAPI specification for Amazon DynamoDB Accelerator (DAX), keeping it validated and agent-ready. Amazon DynamoDB Accelerator (DAX) is a managed in-memory caching service that sits in front of Amazon DynamoDB to deliver sub-millisecond read latency for cached items. The DAX control plane API lets you provision and operate clusters, manage parameter groups and subnet groups, scale replication factor, describe events, and tag resources. It is intended for read-heavy workloads where DynamoDB latency or cost-per-read becomes a bottleneck and a write-through cache makes economic sense.

21 endpoints

Amazon Elastic Block Store

Jentic publishes the only available OpenAPI specification for the Amazon EBS direct APIs, keeping them validated and agent-ready. The EBS direct APIs let backup vendors and applications create EBS snapshots, write data blocks directly into a snapshot, read snapshot blocks, and compute the differences between two snapshots. They are designed for incremental backup and disaster recovery flows that need block-level access without spinning up an EC2 instance to mount a volume. Use them when an agent needs to ingest snapshot data, restore from on-premises backups into the cloud, or efficiently track changed blocks between snapshots.

6 endpoints

Amazon Import/Export Snowball

Jentic publishes the only available OpenAPI specification for Amazon Import/Export Snowball, keeping it validated and agent-ready. The Snow Family management API lets organisations create and track jobs that move large volumes of data between on-premises sites and Amazon S3 using physical Snowball, Snowball Edge, and Snowcone devices. Agents can create addresses, request jobs and clusters, fetch job manifests and unlock codes, generate return shipping labels, and manage long-term pricing arrangements. The 26 operations cover addresses, jobs, clusters, manifests, return shipping, and Snow device pricing.

26 endpoints

Amazon QLDB Session

Jentic publishes the only available OpenAPI specification for Amazon QLDB Session, keeping it validated and agent-ready. QLDB Session is the low-level transactional protocol behind Amazon Quantum Ledger Database. It exposes a single SendCommand operation that multiplexes session start, transaction begin, PartiQL statement execution, fetch-page, commit, and end-session commands over one signed request channel. Most applications use the QLDB driver or shell on top of this API; direct use is appropriate when building a custom QLDB client, language binding, or agent transport layer.

1 endpoints

Amazon SimpleDB

Jentic publishes the only available OpenAPI specification for Amazon SimpleDB, keeping it validated and agent-ready. Amazon SimpleDB is a schemaless, automatically indexed key-value data store that exposes domain, item, and attribute primitives over a query API. Agents can create domains, put and get attributes on items, run select-style queries, and perform batched mutations without managing servers, indexes, or replication. SimpleDB targets small-to-medium structured datasets where simplicity and elasticity matter more than transactional joins.

20 endpoints

AWS Backup

AWS Backup is a unified, policy-based backup service for AWS resources, including EBS volumes, EC2 instances, RDS and Aurora databases, DynamoDB tables, EFS, FSx, S3, and Storage Gateway. The API lets you define backup plans with schedules and retention rules, group resources via selections and tags, store recovery points in encrypted backup vaults with vault locks for immutability, restore on demand, and run audit frameworks with reports for compliance evidence. It also supports legal holds that block deletion of designated recovery points.

72 endpoints

AWS Database Migration Service

Jentic publishes the only available OpenAPI specification for AWS Database Migration Service, keeping it validated and agent-ready. AWS Database Migration Service (DMS) moves data between databases — homogeneous (Oracle to Oracle) or heterogeneous (Oracle to PostgreSQL) — with optional ongoing change-data-capture replication. The API covers the full migration lifecycle: replication instances, source and target endpoints, replication tasks, table mappings, premigration assessments, and Fleet Advisor inventory. Use it when an agent needs to orchestrate a migration plan, kick off a replication task, or pull assessment results back into a runbook.

69 endpoints

AWS Elemental MediaStore

Jentic publishes the only available OpenAPI specification for AWS Elemental MediaStore, keeping it validated and agent-ready. MediaStore is a low-latency object store optimized for media workflows — live origin storage, ingest from encoders, and delivery to packagers. Containers are the top-level namespace; each container has a unique data endpoint and supports container policies, CORS policies, lifecycle policies, and metric policies. The service is designed for high-throughput sequential reads and writes typical of streaming workloads rather than archival use cases.

21 endpoints

AWS RDS Data API

Jentic publishes the only available OpenAPI specification for the AWS RDS Data API, keeping it validated and agent-ready. The RDS Data API runs SQL against Aurora Serverless and Aurora DSQL clusters over HTTPS without persistent database connections or VPC connectivity, using IAM and Secrets Manager for authentication. Six operations cover single-statement execution, batch parameterized execution, transaction begin and commit and rollback, and a legacy ExecuteSql endpoint. It is the right fit for serverless functions, mobile clients, and AI agents that need ad-hoc SQL access without managing a connection pool.

6 endpoints

Connect Your Agent

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 | sh

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 instance

Jentic 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.