EKS
Clusters backed by real k3s sidecars (EKS_K3S_IMAGE, default rancher/k3s). Nodegroups, addons, Fargate profiles, access entries.
Quick start
import boto3
eks = boto3.client("eks", endpoint_url="http://localhost:4566",
region_name="us-east-1",
aws_access_key_id="test", aws_secret_access_key="test")
eks.create_cluster(name="c", roleArn="arn:aws:iam::000000000000:role/r",
resourcesVpcConfig={"subnetIds":["subnet-1"]}, version="1.28")
Supported operations
11 operations exposed by this service as of MiniStack 1.4.6. Extracted directly from the handler dispatch in the source module.
CreateCluster
CreateNodegroup
DeleteCluster
DeleteNodegroup
DescribeCluster
DescribeNodegroup
ListClusters
ListNodegroups
ListTagsForResource
TagResource
UntagResource
CloudFormation
The CloudFormation engine provisions these resource types via this service:
AWS::EKS::Cluster
AWS::EKS::Nodegroup
See CloudFormation engine for intrinsic support and lifecycle details.
Known limitations
- The k3s cluster is real — kubectl works — but the control plane is k3s, not EKS-specific.
- Fargate profiles, access entries, and addons are metadata-only.
Source
ministack/services/eks.py
Read the source to verify the ops list above — dispatch tables and handler functions are the ground truth.