How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Amazon PrivateLink VPC Endpoints API

VPC endpoints (consumer side)

Amazon PrivateLink VPC Endpoints API is one of 4 APIs that Amazon PrivateLink publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include VPC Endpoints. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a getting-started guide, pricing, authentication docs, and rate-limit docs.

This API exposes 4 operations across 4 paths, and defines 6 schemas. It is described by OpenAPI 3.2.0, at version 2016-11-15.

Requests are made against a single base URL, https://ec2.{region}.amazonaws.com.

4 operations 4 paths 6 schemas 1 GET3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2016-11-15
Base URL
https://ec2.amazonaws.com
Authentication
API Key
License
Resource Areas
1

Authentication & Security 1

Amazon PrivateLink VPC Endpoints API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (sigv4). By default, every request must be authenticated.

  • sigv4 — AWS Signature Version 4

Paths & Operations 4

Across 4 paths, the API surfaces 4 operations — 1 GET, 3 POST. Each is listed below with its method, path, parameters, and response codes.

VPC Endpoints 4

VPC endpoints (consumer side)

POST
/?Action=CreateVpcEndpoint
Amazon PrivateLink Create VPC Endpoint
CreateVpcEndpoint body → 200
GET
/?Action=DescribeVpcEndpoints
Amazon PrivateLink Describe VPC Endpoints
DescribeVpcEndpoints 3 params → 200
POST
/?Action=ModifyVpcEndpoint
Amazon PrivateLink Modify VPC Endpoint
ModifyVpcEndpoint body → 200
POST
/?Action=DeleteVpcEndpoints
Amazon PrivateLink Delete VPC Endpoints
DeleteVpcEndpoints body → 200

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are VpcEndpoint (9 properties), CreateVpcEndpointRequest (7 properties), ModifyVpcEndpointRequest (3 properties), DescribeVpcEndpointsResult (2 properties). Each schema is shown below with its type and property counts.

ModifyVpcEndpointRequest
object
3 properties 1 required
DeleteVpcEndpointsRequest
object
1 property 1 required
CreateVpcEndpointResult
object
1 property
DescribeVpcEndpointsResult
object
2 properties
VpcEndpoint
object
9 properties
CreateVpcEndpointRequest
object
7 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

amazon-privatelink-vpc-endpoints-api-openapi.yml Raw ↑

Other APIs Amazon PrivateLink publishes across the network.

Amazon PrivateLink Endpoint Connections API
Amazon PrivateLink Endpoint Services API
Amazon PrivateLink Principals API
Where this information came from

This is an independent, third-party profile of Amazon PrivateLink VPC Endpoints API, 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.