Amazon RDS
Amazon Relational Database Service (RDS) makes it easy to set up, operate, and scale a relational database in the cloud, providing cost-efficient and resizable capacity while automating time-consuming administration tasks such as hardware provisioning, database setup, patching, and backups.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Amazon RDS the way a machine reads it — 75 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Amazon RDS scores 60.3/100 (strong), with a separate agent-readiness read of 24/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-10 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Amazon RDS's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/amazon-rds/"
title="Amazon RDS on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/amazon-rds.svg"
alt="Amazon RDS Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/amazon-rds/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/amazon-rds/"
title="Amazon RDS on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/amazon-rds/card.svg"
alt="Amazon RDS Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Amazon RDS
Each block below is one kind of artifact we hold for Amazon RDS. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 4
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Amazon RDS DB Clusters API
Operations for creating and managing Aurora database clusters
Amazon RDS DB Engine Versions API
Operations for describing available database engine versions
Amazon RDS DB Instances API
Operations for creating, managing, and deleting RDS database instances
Amazon RDS DB Snapshots API
Operations for creating and managing database snapshots
Postman Collections 1
A runnable collection turns the contract into something a developer can execute in seconds. We profile them because the fastest way to trust an API is to make a real call against it.
Ready-to-run Postman collections for exercising this provider's APIs.
Amazon RDS API
POSTMANOpen Collections 6
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONAmazon RDS DB Clusters API
OPEN COLLECTIONAmazon RDS DB Clusters DB Engine Versions API
OPEN COLLECTIONAmazon RDS DB Clusters DB Instances API
OPEN COLLECTIONAmazon RDS DB Clusters DB Snapshots API
OPEN COLLECTIONAmazon RDS API
OPEN COLLECTIONArazzo Workflows 16
Real integrations are rarely a single call. Arazzo describes the multi-step sequences — auth, then create, then confirm — so both a human and an agent can follow the choreography, not just the endpoints.
Multi-step API workflows described with the Arazzo specification.
Amazon RDS Add an Aurora Replica Instance
Confirm a cluster is available, add a reader instance, and poll until it joins.
ARAZZOAmazon RDS Clean Up a DB Snapshot
Confirm a manual snapshot is available, delete it, then verify removal.
ARAZZOAmazon RDS Snapshot and Rebuild a DB Instance
Snapshot a source instance, wait for it, then build a fresh matching instance.
ARAZZOAmazon RDS Convert Instance to Multi-AZ
Enable Multi-AZ on a DB instance immediately and poll until stable.
ARAZZOAmazon RDS Delete an Aurora DB Cluster
Snapshot member instances, delete them, then delete the Aurora cluster.
ARAZZOAmazon RDS Enable Backup Retention
Set an instance backup retention period immediately and poll until stable.
ARAZZOAmazon RDS Modify a DB Instance Class
Resize a DB instance class immediately and poll until it stabilizes.
ARAZZOAmazon RDS Provision an Aurora DB Cluster
Create an Aurora DB cluster and poll until it reports the available status.
ARAZZOAmazon RDS Provision a DB Instance
Create a DB instance and poll until it reports the available status.
ARAZZOAmazon RDS Reboot a DB Instance
Reboot a DB instance with optional failover and poll until it recovers.
ARAZZOAmazon RDS Rotate Master Password
Reset the master user password immediately and poll until the instance stabilizes.
ARAZZOAmazon RDS Scale DB Instance Storage
Increase allocated storage immediately and poll until the instance stabilizes.
ARAZZOAmazon RDS Snapshot a DB Instance
Create a manual DB snapshot and poll until it reports the available status.
ARAZZOAmazon RDS Snapshot Then Delete a DB Instance
Take a final manual snapshot, wait for it, then safely delete the instance.
ARAZZOAmazon RDS Upgrade DB Engine Version
Resolve a target engine version, upgrade the instance, and poll until stable.
ARAZZOAmazon RDS Verify Engine Support Then Provision
Validate the engine version is offered, then provision an instance and wait.
ARAZZOScroll within the panel for all 16 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Amazon Rds Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Amazon Rds Finops
FINOPSSemantic Vocabularies 2
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Amazon Rds Context
JSON-LDAmazon Rds Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Amazon RDS API Rules
SPECTRALAmazon RDS API Rules
SPECTRALJSON Schema 12
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Amazon RDS DB Instance
JSON SCHEMACreateDBClusterResponse
JSON SCHEMACreateDBInstanceResponse
JSON SCHEMACreateDBSnapshotResponse
JSON SCHEMADBCluster
JSON SCHEMADBInstance
JSON SCHEMADBSnapshot
JSON SCHEMADescribeDBClustersResponse
JSON SCHEMADescribeDBInstancesResponse
JSON SCHEMADescribeDBSnapshotsResponse
JSON SCHEMAModifyDBInstanceResponse
JSON SCHEMATag
JSON SCHEMAScroll within the panel for all 12 ·
JSON Structure 12
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Amazon Rds Instance Structure
JSON STRUCTUREAmazon Rds Openapi Create Db Cluster Response Structure
JSON STRUCTUREAmazon Rds Openapi Create Db Instance Response Structure
JSON STRUCTUREAmazon Rds Openapi Create Db Snapshot Response Structure
JSON STRUCTUREAmazon Rds Openapi Db Cluster Structure
JSON STRUCTUREAmazon Rds Openapi Db Instance Structure
JSON STRUCTUREAmazon Rds Openapi Db Snapshot Structure
JSON STRUCTUREAmazon Rds Openapi Modify Db Instance Response Structure
JSON STRUCTUREAmazon Rds Openapi Tag Structure
JSON STRUCTUREScroll within the panel for all 12 ·
Examples 12
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Amazon Rds Instance Example
EXAMPLEScroll within the panel for all 12 ·
Security Posture 4
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Amazon RDS — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 5
Portal, sign-up, and the first successful call
Documentation 12
Reference material describing how the API behaves
Scroll within the panel for all 12 ·
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 31
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 31 ·
Build 14
SDKs, sample code, and the tooling you integrate with
Scroll within the panel for all 14 ·
Access & Security 6
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 4
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/amazon-rds · machine-readable index on apis.io
This is an independent, third-party profile of Amazon RDS, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.