Skip to content

AWS Provider

Coming Soon The AWS provider is scaffolded and ksail cluster init is available, but ksail cluster create is not yet functional. Full provisioner support is landing in a follow-up release.

The AWS provider will create managed Amazon EKS clusters via eksctl once full provisioner support lands. Today, it is available for scaffolding configuration via ksail cluster init and is the only provider available for the EKS distribution.

  1. AWS account — with permissions to create EKS clusters, IAM roles, EC2 instances, and VPCs
  2. AWS credentials — configured via aws configure, environment variables, or an instance profile:
    Terminal window
    export AWS_ACCESS_KEY_ID=your-access-key
    export AWS_SECRET_ACCESS_KEY=your-secret-key
    export AWS_REGION=us-east-1
    KSail defaults to reading the AWS region from AWS_REGION. If you also use other AWS tooling that expects AWS_DEFAULT_REGION, you may set both variables to the same value.
  3. Docker — required locally for the ksail CLI
# yaml-language-server: $schema=https://raw.githubusercontent.com/devantler-tech/ksail/main/schemas/ksail-config.schema.json
apiVersion: ksail.io/v1alpha1
kind: Cluster
metadata:
name: eks-default
spec:
cluster:
distribution: EKS
provider: AWS

All cluster-specific metadata (region, version, nodegroups, addons) lives in eks.yaml — not in ksail.yaml. See the EKS distribution guide for the full eks.yaml configuration reference.

PropertyValue
Supported distributionEKS
Infrastructure typeCloud (managed AWS)
Local registries❌ Not supported
Local mirrors❌ Not supported (use external URLs)
CNIAmazon VPC CNI (provided by default)
CSIAmazon EBS CSI Driver (provided by default)
LoadBalancer supportBuilt-in (AWS-managed)
AWS Load Balancer Controller🚧 Optional / not installed by KSail
  • Cloud provider — local Docker containers (mirrors, registries) are inaccessible from the cluster
  • Only one distribution is supported: EKS