AWS RDS Data API

Name: AWS RDS Data API
Brand: AWS RDS Data API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentStorageDatabasehmac6 EndpointsREST

For Agents

Run SQL and parameterized batch statements against Aurora Serverless and Aurora DSQL clusters over HTTPS without managing connections.

Install Jentic One Beta

Connect the AWS RDS Data API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AWS RDS Data API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

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.

Capabilities

What an agent can do with AWS RDS Data API.

Execute a single SQL statement with named parameters via Execute against an Aurora cluster

Run a parameterized statement across many parameter sets in one call using BatchExecute

Open a transaction with BeginTransaction and thread the transactionId through subsequent calls

GET STARTED

Start building with AWS RDS Data API

Explore with Jentic

View OpenAPI Document

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.

Use Cases

Patterns agents use AWS RDS Data API for, with concrete tasks.

★ Serverless SQL from Lambda

Call SQL from AWS Lambda or any HTTPS-capable client without VPC attachment, NAT, or a connection pool. ExecuteStatement (POST /Execute) takes resourceArn, secretArn, database, sql, and named parameters and returns columnMetadata plus records. The credentials live in Secrets Manager, so the function only needs IAM permissions for rds-data:ExecuteStatement and secretsmanager:GetSecretValue.

Call POST /Execute with resourceArn of the Aurora cluster, secretArn of the credentials secret, database 'app', sql 'SELECT id,email FROM users WHERE id = :id', and parameters [{name:'id',value:{longValue:42}}]

Batch Inserts and Imports

Bulk-load data without paying the per-statement HTTP overhead by using BatchExecute. The API accepts a single sql template and an array of parameterSets and runs the same statement once per set inside one call. Useful for syncing webhook payloads, ETL row inserts, or migration top-ups into Aurora Serverless.

Call POST /BatchExecute with sql 'INSERT INTO events(id, payload) VALUES(:id, :payload)' and parameterSets containing one entry per event

Multi-Statement Transactions

Run several SQL statements atomically over HTTPS by opening a transaction with BeginTransaction, threading the returned transactionId into each Execute call, and committing or rolling back at the end. Common for handling money movement, idempotent upserts, or multi-table writes from a stateless service.

Call POST /BeginTransaction to obtain transactionId, run two Execute calls with that transactionId for INSERT and UPDATE, then POST /CommitTransaction with the same transactionId

AI Agent Database Tool via Jentic

An agent that needs to read or write SQL data uses Jentic to discover the RDS Data API, load Execute, and run parameterized statements against Aurora. Jentic stores the AWS access key in its vault and signs requests with SigV4; the database credentials themselves stay in Secrets Manager and are referenced by ARN, so secrets never enter the agent context.

Use Jentic to search 'execute sql against aurora serverless', load Execute, and execute it with resourceArn, secretArn, database, and parameterized sql

Key Endpoints

6 endpoints — jentic publishes the only available openapi specification for the aws rds data api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/Execute

Execute a single SQL statement with named parameters

POST

/BatchExecute

Run a parameterized statement across many parameter sets

POST

/BeginTransaction

Open a transaction and return a transactionId

POST

/CommitTransaction

Commit an open transaction

POST

/RollbackTransaction

Roll back an open transaction

POST

/ExecuteSql

Legacy SQL execution endpoint

POST

/Execute

Execute a single SQL statement with named parameters

POST

/BatchExecute

Run a parameterized statement across many parameter sets

POST

/BeginTransaction

Open a transaction and return a transactionId

POST

/CommitTransaction

Commit an open transaction

POST

/RollbackTransaction

Roll back an open transaction

Why Jentic?

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

Credential isolation

AWS access keys are encrypted in the Jentic vault. SigV4 signatures are produced per request, and database credentials remain in Secrets Manager (referenced by ARN), so neither AWS secrets nor DB passwords enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'execute sql against aurora serverless') and Jentic returns Execute with its parameter schema (resourceArn, secretArn, database, sql, parameters).

Time to first call

Direct integration: half a day to a day for SDK setup, IAM scoping for rds-data and secretsmanager, SigV4 signing, and parameter typing. Through Jentic: under 30 minutes.

FAQs

Specific to using AWS RDS Data API through Jentic.

Why is there no official OpenAPI spec for the AWS RDS Data API?

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

The API uses AWS SigV4 HMAC request signing for the HTTPS call, plus a Secrets Manager secretArn parameter that holds the database username and password. Through Jentic, AWS credentials are stored in the vault and SigV4 signatures are produced per request.

Which databases does the RDS Data API support?

The Data API supports Aurora Serverless v1 and v2 for PostgreSQL and MySQL, and Aurora DSQL. It does not work against provisioned Aurora clusters running classic engines or other RDS engines like Oracle, SQL Server, or MariaDB.

Can I run multi-statement transactions?

Yes. POST /BeginTransaction returns a transactionId; pass that transactionId into each POST /Execute call and finish with POST /CommitTransaction or POST /RollbackTransaction. Transactions time out after a few minutes of inactivity.

What are the rate limits for the RDS Data API?

The Data API enforces per-account, per-region quotas on simultaneous connections and result-set size (around 1 MB). Throttled requests return BadRequestException or 429 with a throttling message; back off and retry, and use BatchExecute to reduce per-row request volume.

How do I run a parameterized query through Jentic?

Search Jentic for 'execute sql against aurora serverless', load Execute, and execute it with resourceArn, secretArn, database, sql containing named placeholders, and parameters. Install with pip install jentic; AWS credentials come from the Jentic vault.

AWS RDS Data API

Connect the AWS RDS Data API to your agent

Capabilities

Start building with AWS RDS Data API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs