Amazon DocumentDB with MongoDB compatibility

Name: Amazon DocumentDB with MongoDB compatibility API
Brand: Amazon DocumentDB with MongoDB compatibility
Availability: InStock

★ Only Publicly Available OpenAPI DocumentStorageDatabasehmac106 EndpointsREST

For Agents

Provision and operate Amazon DocumentDB clusters and instances, manage snapshots and parameter groups, and control global clusters for MongoDB-compatible workloads.

Quickstart

Get started with Amazon DocumentDB with MongoDB compatibility in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"create a DocumentDB cluster"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Amazon DocumentDB with MongoDB compatibility API.

Provision clusters and primary or replica instances with CreateDBCluster and CreateDBInstance sized for the workload

Snapshot and restore clusters with CreateDBClusterSnapshot, RestoreDBClusterFromSnapshot, and RestoreDBClusterToPointInTime

Manage tunable engine parameters via DBClusterParameterGroup operations and ModifyDBClusterParameterGroup

Operate cross-region global clusters using CreateGlobalCluster, ModifyGlobalCluster, and RemoveFromGlobalCluster

GET STARTED

Start building with Amazon DocumentDB with MongoDB compatibility API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Amazon DocumentDB with MongoDB compatibility, keeping it validated and agent-ready.

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.

Use Cases

Patterns agents use Amazon DocumentDB with MongoDB compatibility API for, with concrete tasks.

★ Provision a Production DocumentDB Cluster

Spin up a multi-AZ DocumentDB cluster with one writer and two reader instances by calling CreateDBCluster, then CreateDBInstance for each member. Attach a DBClusterParameterGroup tuned for the workload and a DBSubnetGroup that spans at least two Availability Zones for fault tolerance.

Call CreateDBCluster with Engine docdb and a DBSubnetGroupName, then CreateDBInstance three times bound to that cluster identifier and verify with DescribeDBClusters.

Disaster Recovery via Point-in-Time Restore

Recover a DocumentDB cluster to any second within the backup retention window using RestoreDBClusterToPointInTime. The new cluster is provisioned from continuous backups without manual snapshot juggling, giving a clean recovery path after accidental data loss.

Call RestoreDBClusterToPointInTime with SourceDBClusterIdentifier, DBClusterIdentifier of the new cluster, and RestoreToTime set to the desired timestamp.

Run a Cross-Region Global Cluster

Create a DocumentDB global cluster spanning two AWS regions for low-latency reads in a secondary region and faster regional failover. CreateGlobalCluster anchors the topology, ModifyGlobalCluster adds secondary clusters, and RemoveFromGlobalCluster detaches a region during decommissioning.

Call CreateGlobalCluster with the primary cluster identifier, then ModifyGlobalCluster to add a secondary cluster ARN in another region.

Agent-Driven DocumentDB Lifecycle Management

An AI agent connected via Jentic can react to a runbook event — provision a new cluster for a stage environment, snapshot a production cluster before a deploy, or scale instance class during a load test. Jentic returns the matching DocumentDB operation and schema so the agent can sequence calls and check status without bespoke SDK code.

Search Jentic for 'create a DocumentDB cluster', load CreateDBCluster, execute it with the requested DBClusterIdentifier, Engine docdb, and DBSubnetGroupName, then poll DescribeDBClusters.

Key Endpoints

106 endpoints — jentic publishes the only available openapi specification for amazon documentdb, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/#Action=CreateDBCluster

Create a DocumentDB cluster

POST

/#Action=CreateDBInstance

Add an instance to a cluster

POST

/#Action=CreateDBClusterSnapshot

Snapshot a cluster

POST

/#Action=DeleteDBCluster

Delete a cluster

POST

/#Action=CopyDBClusterSnapshot

Copy a cluster snapshot

POST

/#Action=CreateGlobalCluster

Create a cross-region global cluster

POST

/#Action=ApplyPendingMaintenanceAction

Apply a pending maintenance action

POST

/#Action=CreateDBCluster

Create a DocumentDB cluster

POST

/#Action=CreateDBInstance

Add an instance to a cluster

POST

/#Action=CreateDBClusterSnapshot

Snapshot a cluster

POST

/#Action=DeleteDBCluster

Delete a cluster

POST

/#Action=CopyDBClusterSnapshot

Copy a cluster snapshot

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

AWS access keys for DocumentDB are stored encrypted in the Jentic vault. Jentic signs each DocumentDB request with SigV4 at execution time and the agent only sees scoped, short-lived access — raw access keys never enter the agent's context.

Intent-based discovery

Agents search by intent (e.g., 'create a DocumentDB cluster' or 'restore from a snapshot') and Jentic returns the matching DocumentDB operation with its input schema, so the agent can call the right endpoint without browsing AWS documentation.

Time to first call

Direct DocumentDB integration: 1-3 days for SigV4 signing, RDS-style query/form encoding, and lifecycle polling. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

AWS Database Migration Service

Migrates data from MongoDB and other databases into DocumentDB.

Choose DMS when the agent needs to move data into or out of a DocumentDB cluster from another engine.

Alternative

Amazon DynamoDB Accelerator (DAX)

Caches DynamoDB reads rather than running document workloads.

Choose DAX when the underlying store is DynamoDB and the goal is read caching, not document database management.

Complementary

AWS Backup

Centralised backup that can manage DocumentDB cluster snapshots.

Choose AWS Backup when the agent needs unified backup policies across DocumentDB and other services.

FAQs

Specific to using Amazon DocumentDB with MongoDB compatibility API through Jentic.

Why is there no official OpenAPI spec for Amazon DocumentDB?

AWS does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Amazon DocumentDB 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 Amazon DocumentDB API use?

DocumentDB uses AWS Signature Version 4 (HMAC) signing with an AWS access key ID and secret access key. Through Jentic, those credentials live encrypted in the Jentic vault and are injected into signed requests at execution time, so the agent never sees the raw secret access key.

Can I run a global cluster across regions through this API?

Yes. Use CreateGlobalCluster to define the topology, then ModifyGlobalCluster to attach secondary clusters in other regions. Reads and writes follow standard global cluster semantics, and RemoveFromGlobalCluster detaches a region for maintenance.

What are the rate limits for the Amazon DocumentDB API?

DocumentDB shares standard AWS service quotas, which are managed per account and region rather than published as fixed per-second limits in the spec. Cluster and instance counts are also gated by RDS-style account quotas; ThrottlingException responses should trigger backoff.

How do I provision a DocumentDB cluster through Jentic?

Search Jentic for 'create a DocumentDB cluster', load CreateDBCluster, then execute it with DBClusterIdentifier, Engine docdb, MasterUsername, MasterUserPassword, and DBSubnetGroupName. Run pip install jentic and use the async search and execute pattern.

Does this API run database queries, or only manage clusters?

Only manages clusters and instances. Application queries connect via the MongoDB wire protocol to the cluster endpoint returned by DescribeDBClusters and use a MongoDB driver — DocumentDB's data plane is not exposed through this REST API.