Amazon PrivateLink
AWS PrivateLink provides private connectivity between virtual private clouds (VPCs), AWS services, and your on-premises networks without exposing your traffic to the public internet. It makes it easy to connect services across different accounts and VPCs to simplify your network architecture while maintaining security and compliance.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Amazon PrivateLink the way a machine reads it — 82 machine-readable artifacts across 4 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 PrivateLink scores 65.3/100 (strong), with a separate agent-readiness read of 55/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 PrivateLink
Each block below is one kind of artifact we hold for Amazon PrivateLink. 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 PrivateLink Endpoint Connections API
Endpoint connection management
Amazon PrivateLink Endpoint Services API
VPC endpoint services (provider side)
Amazon PrivateLink Principals API
Endpoint service principal management
Amazon PrivateLink VPC Endpoints API
VPC endpoints (consumer side)
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 Privatelink 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.
Features 8
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.
Private VPC Endpoints
Connect to AWS services and endpoint services without using public IP addresses or internet gateways.
VPC Endpoint Services
Expose services running in your VPC to other VPCs and accounts using Network Load Balancers.
Interface Endpoints
Elastic network interfaces with private IP addresses that serve as entry points for supported services.
Gateway Endpoints
Route table targets for S3 and DynamoDB traffic without using internet gateways.
Cross-Account Connectivity
Enable service consumers in other AWS accounts to access your endpoint services privately.
Acceptance Control
Control which service consumers can connect to your endpoint service with acceptance required settings.
Private DNS
Configure private DNS names for interface endpoints to simplify connectivity without code changes.
Endpoint Policies
Control access to services through endpoint policy documents for fine-grained access control.
Scroll within the panel for all 8 ·
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 Privatelink 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 PrivateLink API Rules
SPECTRALAmazon PrivateLink API Rules
SPECTRALJSON Schema 18
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.
AcceptVpcEndpointConnectionsRequest
JSON SCHEMACreateVpcEndpointRequest
JSON SCHEMACreateVpcEndpointResult
JSON SCHEMACreateVpcEndpointServiceConfigurationRequest
JSON SCHEMACreateVpcEndpointServiceConfigurationResult
JSON SCHEMADeleteVpcEndpointsRequest
JSON SCHEMADescribeVpcEndpointConnectionsResult
JSON SCHEMADescribeVpcEndpointServicesResult
JSON SCHEMADescribeVpcEndpointsResult
JSON SCHEMAModifyVpcEndpointRequest
JSON SCHEMAModifyVpcEndpointServiceConfigurationRequest
JSON SCHEMAModifyVpcEndpointServicePermissionsRequest
JSON SCHEMARejectVpcEndpointConnectionsRequest
JSON SCHEMAServiceConfiguration
JSON SCHEMAServiceDetail
JSON SCHEMAVpcEndpointConnection
JSON SCHEMAVpcEndpoint
JSON SCHEMAScroll within the panel for all 18 ·
JSON Structure 18
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 Privatelink Create Vpc Endpoint Request Structure
JSON STRUCTUREAmazon Privatelink Create Vpc Endpoint Result Structure
JSON STRUCTUREAmazon Privatelink Modify Vpc Endpoint Request Structure
JSON STRUCTUREAmazon Privatelink Service Configuration Structure
JSON STRUCTUREAmazon Privatelink Service Detail Structure
JSON STRUCTUREAmazon Privatelink Vpc Endpoint Connection Structure
JSON STRUCTUREAmazon Privatelink Vpc Endpoint Structure
JSON STRUCTUREScroll within the panel for all 18 ·
Examples 18
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.
Scroll within the panel for all 18 ·
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.
SaaS Service Delivery
Deliver SaaS services to customers privately without internet exposure using PrivateLink.
Microservices Private Connectivity
Enable microservices in different VPCs or accounts to communicate privately.
Regulatory Compliance
Meet compliance requirements by keeping data transfer off the public internet.
Third-Party Service Integration
Connect to marketplace services and partner APIs without public internet routing.
On-Premises Private Access
Access AWS services from on-premises networks via VPN or Direct Connect without public endpoints.
Resources
Every other property we hold for Amazon PrivateLink — 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 3
Portal, sign-up, and the first successful call
Documentation 19
Reference material describing how the API behaves
Scroll within the panel for all 19 ·
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 21
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 21 ·
Build 19
SDKs, sample code, and the tooling you integrate with
Scroll within the panel for all 19 ·
Access & Security 4
Authentication, authorization, and security posture
Operate 2
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-privatelink · machine-readable index on apis.io