Amazon DataZone
Amazon DataZone is a data management service that helps you catalog, discover, govern, share, and analyze your data across your organization and beyond. It enables data producers and consumers to collaborate, with built-in governance, data catalog capabilities, and a business data catalog to organize and share data across your AWS environment. DataZone provides domain-based governance, project workspaces, subscription-based access control, and integration with AWS analytics services.
Reference-quality API operations across every facet — a rich contract, published governance, transparent operations, and machine-readable commercial terms.
API Evangelist profiles Amazon DataZone the way a machine reads it — 79 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 DataZone scores 71.7/100 (exemplar), with a separate agent-readiness read of 48/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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Amazon DataZone
Each block below is one kind of artifact we hold for Amazon DataZone. 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 DataZone Assets API
Operations for managing data assets in the catalog
Amazon DataZone Domains API
Operations for managing DataZone domains
Amazon DataZone Environments API
Operations for managing data environments
Amazon DataZone Listings API
Operations for managing asset listings in the catalog
Amazon DataZone Projects API
Operations for managing projects within a domain
Amazon DataZone Subscriptions API
Operations for managing data subscriptions
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 DataZone API
POSTMANOpen Collections 1
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).
Amazon DataZone API
OPEN COLLECTIONArazzo Workflows 12
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 DataZone Audit Domain Subscriptions
List pending subscription requests and active subscriptions to audit data access.
ARAZZOAmazon DataZone Bootstrap Domain and Project
Create a domain, wait for it to be AVAILABLE, then create a project inside it.
ARAZZOAmazon DataZone Catalog a Data Asset
Create a data asset in a project and read it back to confirm cataloging.
ARAZZOAmazon DataZone Discover and Subscribe
Search catalog listings, then raise a subscription request for the first match.
ARAZZOAmazon DataZone Onboard Data Workspace
Create a project, catalog an asset, and provision an environment in one workspace flow.
ARAZZOAmazon DataZone Provision Environment
Create a project environment and poll the environment list until it is ACTIVE.
ARAZZOAmazon DataZone Publish Data Product
Create a project, catalog an asset in it, then search the catalog for the listing.
ARAZZOAmazon DataZone Rename Project
Read a project, update its description, then read it back to confirm the change.
ARAZZOAmazon DataZone Request and Track Subscription
Create a subscription request, then poll the request list until it leaves PENDING.
ARAZZOAmazon DataZone Teardown Domain
List projects in a domain and branch to delete the domain only when it is empty.
ARAZZOAmazon DataZone Teardown Project
Confirm a project exists, delete it, then verify the delete via a 404 read-back.
ARAZZOScroll within the panel for all 12 ·
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 six things the Kin Score reads for commercial clarity.
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 Datazone 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 Datazone Finops
FINOPSFeatures 7
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.
Business Data Catalog
Central catalog where data producers publish assets and data consumers can discover, understand, and request access to data products.
Domain-Based Governance
Organize data assets, users, and governance policies within domains that reflect your organizational structure and data ownership.
Subscription Workflow
Built-in request/approval workflow for data consumers to request access to data assets with business justification and audit trail.
Project Workspaces
Isolated project containers within domains where teams organize their data assets, environments, and members.
Analytics Environment Provisioning
Automatically provision data access environments with Athena, Glue, Redshift, or other tools when subscriptions are approved.
Glue Data Catalog Integration
Automatically discover and import tables from AWS Glue Data Catalog into DataZone for cataloging and governance.
Data Lineage
Track data lineage across assets to understand data origins, transformations, and dependencies for trust and compliance.
Scroll within the panel for all 7 ·
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 Datazone 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 DataZone API Rules
SPECTRALAmazon DataZone 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.
Asset
JSON SCHEMACreate Asset Request
JSON SCHEMACreate Domain Request
JSON SCHEMACreate Environment Request
JSON SCHEMACreate Project Request
JSON SCHEMADomain
JSON SCHEMAEnvironment
JSON SCHEMAError
JSON SCHEMAList Domains Response
JSON SCHEMAList Projects Response
JSON SCHEMAProject
JSON SCHEMASubscription Request
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.
Asset Structure
JSON STRUCTURECreate Asset Request Structure
JSON STRUCTURECreate Domain Request Structure
JSON STRUCTURECreate Environment Request Structure
JSON STRUCTURECreate Project Request Structure
JSON STRUCTUREDomain Structure
JSON STRUCTUREEnvironment Structure
JSON STRUCTUREError Structure
JSON STRUCTUREList Domains Response Structure
JSON STRUCTUREList Projects Response Structure
JSON STRUCTUREProject Structure
JSON STRUCTURESubscription Request 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.
Asset Example
EXAMPLECreate Asset Request Example
EXAMPLEDomain Example
EXAMPLEEnvironment Example
EXAMPLEError Example
EXAMPLEProject Example
EXAMPLESubscription Request 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.
Use Cases 5
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.
Enterprise Data Marketplace
Build an internal data marketplace where business units publish their data products for discovery and consumption by other teams.
Data Access Governance
Implement governed data access with approval workflows ensuring data consumers have proper authorization and business justification.
Cross-Account Data Sharing
Share data assets across AWS accounts within an organization using DataZone's subscription and access management capabilities.
Self-Service Analytics
Enable analysts to discover and access data independently through the DataZone catalog with automatic environment provisioning.
Regulatory Data Compliance
Maintain audit trails of data access, govern sensitive data assets, and enforce data residency policies through domain governance.
Resources
Every other property we hold for Amazon DataZone — 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 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 14
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 14 ·
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 3
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
← All providers · Data indexed from github.com/api-evangelist/amazon-datazone · machine-readable index on apis.io