Amazon Cloud WAN
Amazon Cloud WAN is a managed wide area networking service that simplifies building, managing, and monitoring global WANs by connecting branch offices, data centers, and Amazon VPCs through a central dashboard with network policy automation and unified monitoring.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Amazon Cloud WAN the way a machine reads it — 41 machine-readable artifacts across 2 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 Cloud WAN scores 57.1/100 (developing), 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 Cloud WAN
Each block below is one kind of artifact we hold for Amazon Cloud WAN. 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 2
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 Cloud WAN API
API for building and managing global wide area networks, connecting branch offices, data centers, and VPCs with centralized control, monitoring, and network policy automation.
Amazon Cloud WAN Core Networks API
Operations for managing Cloud WAN core networks
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-cloud-wan-mcp.yml
MCP SERVERFeatures 5
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.
Centralized WAN Management
Build and manage global wide area networks through a single centralized dashboard.
Network Policy Automation
Automate management and security tasks across your entire WAN infrastructure.
Unified Monitoring
Monitor on-premises and AWS network health and performance from one view.
Network Segmentation
Isolate sensitive traffic from standard data flows with segmentation policies.
Global Connectivity
Connect branch offices, data centers, and VPCs with minimal configuration globally.
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 Cloud Wan 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 Cloud WAN API Rules
SPECTRALAmazon Cloud WAN API Rules
SPECTRALJSON Schema 6
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.
CoreNetwork
JSON SCHEMACreateCoreNetworkRequest
JSON SCHEMACreateCoreNetworkResponse
JSON SCHEMADeleteCoreNetworkResponse
JSON SCHEMAGetCoreNetworkResponse
JSON SCHEMAListCoreNetworksResponse
JSON SCHEMAJSON Structure 6
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.
Cloud Wan Core Network Structure
JSON STRUCTURECloud Wan Create Core Network Request Structure
JSON STRUCTURECloud Wan Create Core Network Response Structure
JSON STRUCTURECloud Wan Delete Core Network Response Structure
JSON STRUCTURECloud Wan Get Core Network Response Structure
JSON STRUCTURECloud Wan List Core Networks Response Structure
JSON STRUCTUREExamples 6
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.
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 3
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.
Global Enterprise WAN
Build globally distributed corporate WANs using AWS infrastructure.
Hybrid Network Extension
Extend on-premises corporate WANs into AWS cloud environments seamlessly.
Network Centralization
Centralize network configuration, monitoring, and automation across all locations.
Integrations 4
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
AWS Transit Gateway
Connect VPCs and on-premises networks through Transit Gateway attachments.
AWS Direct Connect
Dedicated network connections from on-premises to AWS.
Amazon VPC
Connect VPCs across regions into the global WAN.
AWS IAM
Control access to Cloud WAN resources with IAM policies.
Resources
Every other property we hold for Amazon Cloud WAN — 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 1
Reference material describing how the API behaves
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
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 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/amazon-cloud-wan · machine-readable index on apis.io