Amazon Aurora
Amazon Aurora is a MySQL and PostgreSQL-compatible relational database built for the cloud that combines the performance and availability of traditional enterprise databases with the simplicity and cost-effectiveness of open source databases.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Amazon Aurora the way a machine reads it — 203 machine-readable artifacts across 6 APIs, 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 Aurora scores 39.9/100 (thin), with a separate agent-readiness read of 60/100 (agent ready). 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.
How we profile Amazon Aurora
Each block below is one kind of artifact we hold for Amazon Aurora. 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 6
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 Aurora DB Cluster Endpoints API
Operations for managing Aurora cluster endpoints
Amazon Aurora DB Cluster Parameter Groups API
Operations for managing Aurora cluster parameter groups
Amazon Aurora DB Cluster Snapshots API
Operations for managing Aurora cluster snapshots
Amazon Aurora DB Clusters API
Operations for managing Aurora DB clusters
Amazon Aurora DB Instances API
Operations for managing Aurora DB instances within clusters
Amazon Aurora Global Clusters API
Operations for managing Aurora Global Databases
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
amazon-aurora-mcp.yml
MCP SERVERFeatures 10
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Scroll within the panel for all 10 ·
Semantic Vocabularies 1
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 Aurora 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 Aurora API Rules
SPECTRALAmazon Aurora API Rules
SPECTRALJSON Schema 55
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 Aurora DB Cluster
JSON SCHEMACreateDBClusterEndpointInput
JSON SCHEMACreateDBClusterEndpointOutput
JSON SCHEMACreateDBClusterInput
JSON SCHEMACreateDBClusterOutput
JSON SCHEMACreateDBClusterParameterGroupInput
JSON SCHEMACreateDBClusterParameterGroupOutput
JSON SCHEMACreateDBClusterSnapshotInput
JSON SCHEMACreateDBClusterSnapshotOutput
JSON SCHEMACreateDBInstanceInput
JSON SCHEMACreateDBInstanceOutput
JSON SCHEMACreateGlobalClusterInput
JSON SCHEMACreateGlobalClusterOutput
JSON SCHEMADBClusterEndpoint
JSON SCHEMADBClusterMember
JSON SCHEMADBClusterParameterGroup
JSON SCHEMADBCluster
JSON SCHEMADBClusterSnapshot
JSON SCHEMADBInstance
JSON SCHEMADeleteDBClusterInput
JSON SCHEMADeleteDBClusterOutput
JSON SCHEMADeleteDBClusterSnapshotInput
JSON SCHEMADeleteDBClusterSnapshotOutput
JSON SCHEMADeleteDBInstanceInput
JSON SCHEMADeleteDBInstanceOutput
JSON SCHEMADeleteGlobalClusterInput
JSON SCHEMADeleteGlobalClusterOutput
JSON SCHEMADescribeDBClusterEndpointsInput
JSON SCHEMADescribeDBClusterEndpointsOutput
JSON SCHEMADescribeDBClusterParameterGroupsInput
JSON SCHEMADescribeDBClusterParameterGroupsOutput
JSON SCHEMADescribeDBClusterSnapshotsInput
JSON SCHEMADescribeDBClusterSnapshotsOutput
JSON SCHEMADescribeDBClustersInput
JSON SCHEMADescribeDBClustersOutput
JSON SCHEMADescribeDBInstancesInput
JSON SCHEMADescribeDBInstancesOutput
JSON SCHEMADescribeGlobalClustersInput
JSON SCHEMADescribeGlobalClustersOutput
JSON SCHEMAEndpoint
JSON SCHEMAFilter
JSON SCHEMAGlobalClusterMember
JSON SCHEMAGlobalCluster
JSON SCHEMAModifyDBClusterInput
JSON SCHEMAModifyDBClusterOutput
JSON SCHEMARebootDBClusterInput
JSON SCHEMARebootDBClusterOutput
JSON SCHEMARestoreDBClusterFromSnapshotInput
JSON SCHEMARestoreDBClusterFromSnapshotOutput
JSON SCHEMAStartDBClusterInput
JSON SCHEMAStartDBClusterOutput
JSON SCHEMAStopDBClusterInput
JSON SCHEMAStopDBClusterOutput
JSON SCHEMATag
JSON SCHEMAVpcSecurityGroupMembership
JSON SCHEMAScroll within the panel for all 55 ·
JSON Structure 54
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.
Aurora Create Db Cluster Endpoint Input Structure
JSON STRUCTUREAurora Create Db Cluster Endpoint Output Structure
JSON STRUCTUREAurora Create Db Cluster Input Structure
JSON STRUCTUREAurora Create Db Cluster Output Structure
JSON STRUCTUREAurora Create Db Cluster Parameter Group Input Structure
JSON STRUCTUREAurora Create Db Cluster Snapshot Input Structure
JSON STRUCTUREAurora Create Db Cluster Snapshot Output Structure
JSON STRUCTUREAurora Create Db Instance Input Structure
JSON STRUCTUREAurora Create Db Instance Output Structure
JSON STRUCTUREAurora Create Global Cluster Input Structure
JSON STRUCTUREAurora Create Global Cluster Output Structure
JSON STRUCTUREAurora Db Cluster Endpoint Structure
JSON STRUCTUREAurora Db Cluster Member Structure
JSON STRUCTUREAurora Db Cluster Parameter Group Structure
JSON STRUCTUREAurora Db Cluster Snapshot Structure
JSON STRUCTUREAurora Db Cluster Structure
JSON STRUCTUREAurora Db Instance Structure
JSON STRUCTUREAurora Delete Db Cluster Input Structure
JSON STRUCTUREAurora Delete Db Cluster Output Structure
JSON STRUCTUREAurora Delete Db Cluster Snapshot Input Structure
JSON STRUCTUREAurora Delete Db Cluster Snapshot Output Structure
JSON STRUCTUREAurora Delete Db Instance Input Structure
JSON STRUCTUREAurora Delete Db Instance Output Structure
JSON STRUCTUREAurora Delete Global Cluster Input Structure
JSON STRUCTUREAurora Delete Global Cluster Output Structure
JSON STRUCTUREAurora Describe Db Cluster Endpoints Input Structure
JSON STRUCTUREAurora Describe Db Cluster Endpoints Output Structure
JSON STRUCTUREAurora Describe Db Cluster Snapshots Input Structure
JSON STRUCTUREAurora Describe Db Cluster Snapshots Output Structure
JSON STRUCTUREAurora Describe Db Clusters Input Structure
JSON STRUCTUREAurora Describe Db Clusters Output Structure
JSON STRUCTUREAurora Describe Db Instances Input Structure
JSON STRUCTUREAurora Describe Db Instances Output Structure
JSON STRUCTUREAurora Describe Global Clusters Input Structure
JSON STRUCTUREAurora Describe Global Clusters Output Structure
JSON STRUCTUREAurora Endpoint Structure
JSON STRUCTUREAurora Filter Structure
JSON STRUCTUREAurora Global Cluster Member Structure
JSON STRUCTUREAurora Global Cluster Structure
JSON STRUCTUREAurora Modify Db Cluster Input Structure
JSON STRUCTUREAurora Modify Db Cluster Output Structure
JSON STRUCTUREAurora Reboot Db Cluster Input Structure
JSON STRUCTUREAurora Reboot Db Cluster Output Structure
JSON STRUCTUREAurora Restore Db Cluster From Snapshot Input Structure
JSON STRUCTUREAurora Restore Db Cluster From Snapshot Output Structure
JSON STRUCTUREAurora Start Db Cluster Input Structure
JSON STRUCTUREAurora Start Db Cluster Output Structure
JSON STRUCTUREAurora Stop Db Cluster Input Structure
JSON STRUCTUREAurora Stop Db Cluster Output Structure
JSON STRUCTUREAurora Tag Structure
JSON STRUCTUREAurora Vpc Security Group Membership Structure
JSON STRUCTUREScroll within the panel for all 54 ·
Examples 54
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.
Aurora Db Cluster Example
EXAMPLEAurora Db Instance Example
EXAMPLEAurora Endpoint Example
EXAMPLEAurora Filter Example
EXAMPLEAurora Tag Example
EXAMPLEScroll within the panel for all 54 ·
Security Posture 3
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.
Use Cases 6
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Integrations 10
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Scroll within the panel for all 10 ·
Resources
Every other property we hold for Amazon Aurora — 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.
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
← All providers · Data indexed from github.com/api-evangelist/amazon-aurora · machine-readable index on apis.io