Amazon Elastic Kubernetes Service

Name: Amazon Elastic Kubernetes Service API
Brand: Amazon Elastic Kubernetes Service
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCloud InfrastructureContainer OrchestrationapiKey35 EndpointsREST

For Agents

Quickstart

Get started with Amazon Elastic Kubernetes Service in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"provision an EKS Kubernetes cluster"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Amazon Elastic Kubernetes Service API.

Create and delete EKS clusters with custom VPC, logging, and Kubernetes version configuration

Provision managed node groups with autoscaling settings, instance types, and AMI release versions

Attach Fargate profiles to run pods on serverless compute without managing EC2 nodes

Install, update, and remove EKS add-ons such as VPC CNI, CoreDNS, and kube-proxy

GET STARTED

Start building with Amazon Elastic Kubernetes Service API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Amazon Elastic Kubernetes Service, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Amazon Elastic Kubernetes Service, keeping it validated and agent-ready. Amazon EKS is a managed Kubernetes service that runs upstream Kubernetes on AWS without requiring teams to operate the control plane themselves. The API covers cluster lifecycle management, managed node groups, Fargate profiles, EKS add-ons, and identity provider configuration. It is designed for platform teams that need to provision, scale, and upgrade Kubernetes clusters across multiple AWS regions while keeping pace with upstream Kubernetes releases.

Use Cases

Patterns agents use Amazon Elastic Kubernetes Service API for, with concrete tasks.

★ Multi-Region Kubernetes Platform Provisioning

Platform engineering teams use the Amazon EKS API to stand up production-grade Kubernetes clusters across multiple AWS regions with consistent network, logging, and encryption configuration. The API drives cluster creation, node group sizing, and Fargate profile attachment so teams can codify cluster topology in pipelines instead of clicking through the console. A typical regional rollout creates one cluster, two node groups, and three Fargate profiles in under thirty minutes when run as an automated workflow.

Create an EKS cluster named prod-eu in eu-west-1 with Kubernetes version 1.28, then attach a managed node group of three t3.large nodes.

Fargate Workload Onboarding

Teams migrating workloads to serverless containers use the EKS API to attach Fargate profiles that select pods by namespace and label. This removes the need to manage EC2 worker nodes for specific workloads while keeping the rest of the cluster on managed node groups. Fargate profile creation typically completes in two to three minutes and supports up to five selector rules per profile.

Create a Fargate profile on cluster prod-eu that selects pods in the batch namespace with label workload=etl.

Add-on Lifecycle Management

EKS add-ons let teams keep cluster components such as VPC CNI, CoreDNS, and kube-proxy on supported, vendor-curated versions. The API handles install, version updates, and removal so cluster operators can roll out coordinated upgrades across many clusters. Add-on updates are non-disruptive when configured with the PRESERVE conflict resolution strategy.

Update the vpc-cni add-on on cluster prod-eu to version v1.15.1-eksbuild.1 with the PRESERVE conflict resolution strategy.

Agent-Driven Cluster Operations via Jentic

AI agents use the EKS API through Jentic to handle routine cluster operations such as listing clusters, checking upgrade readiness, and provisioning new node groups in response to capacity events. Jentic exposes EKS operations as discoverable tools so an agent can search by intent and execute the matching operation without parsing AWS docs. This shortens incident response and capacity planning loops from manual console work to seconds.

Search Jentic for create cluster, load the EKS createCluster schema, and execute it for a new staging cluster in us-east-2.

Key Endpoints

35 endpoints — jentic publishes the only available openapi specification for amazon elastic kubernetes service, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/clusters

Create a new EKS cluster

GET

/clusters

List EKS clusters in the account

DELETE

/clusters/{name}

Delete an EKS cluster

POST

/clusters/{name}/node-groups

Create a managed node group

POST

/clusters/{name}/fargate-profiles

Create a Fargate profile

POST

/clusters/{name}/addons

Install an EKS add-on

POST

/clusters/{name}/identity-provider-configs/associate

Associate an OIDC identity provider

POST

/clusters

Create a new EKS cluster

GET

/clusters

List EKS clusters in the account

DELETE

/clusters/{name}

Delete an EKS cluster

POST

/clusters/{name}/node-groups

Create a managed node group

POST

/clusters/{name}/fargate-profiles

Create a Fargate profile

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

AWS access keys for EKS are stored encrypted in the Jentic vault. Agents receive scoped, short-lived signing access — raw access key IDs and secret access keys never enter the agent's context.

Intent-based discovery

Agents search by intent (for example provision a kubernetes cluster) and Jentic returns matching EKS operations with their input schemas, so the agent can call the right endpoint without browsing AWS docs.

Time to first call

Direct EKS integration: 1-3 days for SigV4 signing, error handling, and pagination. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Amazon EC2

EC2 provides the underlying compute that EKS managed node groups run on

Choose EC2 when you need to inspect or modify the underlying instances, security groups, or VPC subnets that host EKS worker nodes.

Complementary

Amazon EMR on EKS

Runs Spark and other big-data frameworks on existing EKS clusters

Choose EMR on EKS when the workload is Spark or Hive analytics and you want to reuse an EKS cluster as the compute substrate.

Alternative

AWS Lambda

Serverless functions for short-lived event-driven workloads

Choose Lambda when the workload is event-driven, short-lived, and does not need a persistent Kubernetes runtime or custom networking.

FAQs

Specific to using Amazon Elastic Kubernetes Service API through Jentic.

Why is there no official OpenAPI spec for Amazon Elastic Kubernetes Service?

AWS does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Amazon Elastic Kubernetes Service via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Amazon EKS API use?

EKS uses AWS Signature Version 4 request signing (the spec marks the scheme as hmac/apiKey). Through Jentic, AWS access keys are stored encrypted in the vault and signing happens server-side, so raw credentials never enter the agent context.

Can I create managed node groups with the EKS API?

Yes. POST /clusters/{name}/node-groups creates a managed node group with instance type, scaling configuration, AMI type, and Kubernetes labels. The cluster must already exist before you call this endpoint.

What are the rate limits for the Amazon EKS API?

AWS applies per-account, per-region API throttling on EKS. Mutating calls (create cluster, create node group) are limited more aggressively than describe calls. Use exponential backoff on ThrottlingException responses; AWS does not publish exact TPS numbers in the spec.

How do I install an EKS add-on through Jentic?

Search Jentic for install eks addon, load the schema for POST /clusters/{name}/addons, and execute it with the cluster name, addonName (for example vpc-cni), and addonVersion. Jentic returns the createdAt timestamp and add-on ARN once the call succeeds.

Does the EKS API let me run kubectl commands?

No. The EKS API manages the cluster control plane, node groups, and add-ons. Kubernetes object operations (kubectl apply, get pods) go directly to the cluster's Kubernetes API server using the kubeconfig you obtain from describeCluster.