Amazon EKS
Amazon Elastic Kubernetes Service (Amazon EKS) is a managed Kubernetes service that makes it easy to run Kubernetes on AWS without needing to install, operate, and maintain your own Kubernetes control plane or nodes. Amazon EKS runs upstream Kubernetes and is certified Kubernetes conformant, so you can use existing tools and plugins from partners and the Kubernetes community.
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 EKS the way a machine reads it — 117 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 EKS scores 59.3/100 (developing), with a separate agent-readiness read of 39/100 (agent aware). 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 EKS
Each block below is one kind of artifact we hold for Amazon EKS. 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 EKS Addons API
Operations for managing EKS add-ons
Amazon EKS Clusters API
Operations for managing EKS clusters
Amazon EKS Fargate Profiles API
Operations for managing EKS Fargate profiles
Amazon EKS Node Groups API
Operations for managing EKS managed node groups
Open 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 EKS API
OPEN COLLECTIONPricing 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 Eks 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 Eks 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.
Managed Control Plane
AWS manages the Kubernetes control plane across multiple Availability Zones with automatic upgrades.
EKS Auto Mode
Automates cluster infrastructure management for compute, storage, and networking with machine learning optimization.
EKS Hybrid Nodes
Connect on-premises and edge infrastructure to EKS clusters for unified management.
Fargate Integration
Run Kubernetes pods on serverless compute without managing EC2 node groups.
Managed Node Groups
Automate provisioning and lifecycle management of EC2 nodes for Kubernetes clusters.
EKS Anywhere
Deploy and manage Kubernetes clusters on customer-managed infrastructure including on-premises.
Add-Ons Management
Manage operational software add-ons like VPC CNI, CoreDNS, and kube-proxy through EKS.
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 Eks 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 EKS API Rules
SPECTRALAmazon EKS API Rules
SPECTRALJSON Schema 30
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 EKS Cluster
JSON SCHEMAAddon
JSON SCHEMACluster
JSON SCHEMACreateAddonRequest
JSON SCHEMACreateAddonResponse
JSON SCHEMACreateClusterRequest
JSON SCHEMACreateClusterResponse
JSON SCHEMACreateFargateProfileRequest
JSON SCHEMACreateFargateProfileResponse
JSON SCHEMACreateNodegroupRequest
JSON SCHEMACreateNodegroupResponse
JSON SCHEMADeleteAddonResponse
JSON SCHEMADeleteClusterResponse
JSON SCHEMADeleteFargateProfileResponse
JSON SCHEMADeleteNodegroupResponse
JSON SCHEMADescribeAddonResponse
JSON SCHEMADescribeClusterResponse
JSON SCHEMADescribeFargateProfileResponse
JSON SCHEMADescribeNodegroupResponse
JSON SCHEMAFargateProfile
JSON SCHEMAFargateProfileSelector
JSON SCHEMAKubernetesNetworkConfigResponse
JSON SCHEMAListAddonsResponse
JSON SCHEMAListClustersResponse
JSON SCHEMAListFargateProfilesResponse
JSON SCHEMAListNodegroupsResponse
JSON SCHEMALogging
JSON SCHEMANodegroupScalingConfig
JSON SCHEMANodegroup
JSON SCHEMAVpcConfigResponse
JSON SCHEMAScroll within the panel for all 30 ·
JSON Structure 30
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 Eks Cluster Structure
JSON STRUCTUREEks Openapi Addon Structure
JSON STRUCTUREEks Openapi Cluster Structure
JSON STRUCTUREEks Openapi Create Addon Request Structure
JSON STRUCTUREEks Openapi Create Addon Response Structure
JSON STRUCTUREEks Openapi Create Cluster Request Structure
JSON STRUCTUREEks Openapi Create Cluster Response Structure
JSON STRUCTUREEks Openapi Create Fargate Profile Request Structure
JSON STRUCTUREEks Openapi Create Fargate Profile Response Structure
JSON STRUCTUREEks Openapi Create Nodegroup Request Structure
JSON STRUCTUREEks Openapi Create Nodegroup Response Structure
JSON STRUCTUREEks Openapi Delete Addon Response Structure
JSON STRUCTUREEks Openapi Delete Cluster Response Structure
JSON STRUCTUREEks Openapi Delete Fargate Profile Response Structure
JSON STRUCTUREEks Openapi Delete Nodegroup Response Structure
JSON STRUCTUREEks Openapi Describe Addon Response Structure
JSON STRUCTUREEks Openapi Describe Cluster Response Structure
JSON STRUCTUREEks Openapi Describe Fargate Profile Response Structure
JSON STRUCTUREEks Openapi Describe Nodegroup Response Structure
JSON STRUCTUREEks Openapi Fargate Profile Selector Structure
JSON STRUCTUREEks Openapi Fargate Profile Structure
JSON STRUCTUREEks Openapi Kubernetes Network Config Response Structure
JSON STRUCTUREEks Openapi List Addons Response Structure
JSON STRUCTUREEks Openapi List Clusters Response Structure
JSON STRUCTUREEks Openapi List Fargate Profiles Response Structure
JSON STRUCTUREEks Openapi List Nodegroups Response Structure
JSON STRUCTUREEks Openapi Logging Structure
JSON STRUCTUREEks Openapi Nodegroup Scaling Config Structure
JSON STRUCTUREEks Openapi Nodegroup Structure
JSON STRUCTUREEks Openapi Vpc Config Response Structure
JSON STRUCTUREScroll within the panel for all 30 ·
Examples 30
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.
Amazon Eks Cluster Example
EXAMPLEEks Openapi Addon Example
EXAMPLEEks Openapi Cluster Example
EXAMPLEEks Openapi Logging Example
EXAMPLEScroll within the panel for all 30 ·
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 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.
Generative AI Applications
Scale production-grade AI deployments with GPU nodes for distributed training and inference.
Microservices Architecture
Deploy and manage containerized microservices with Kubernetes-native service discovery and scaling.
Internal Developer Platforms
Standardized Kubernetes environments combining open source with AWS managed services.
Hybrid Cloud Applications
Unified Kubernetes management across AWS cloud and on-premises infrastructure.
Data Processing Platforms
Scalable batch processing and streaming data workloads using Spark, Flink, or Ray.
Resources
Every other property we hold for Amazon EKS — 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 2
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 5
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 1
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/amazon-eks · machine-readable index on apis.io