Files
Alexander PetricandClaude Opus 5.5 f183bd43fb chore: retire the standalone lsp and multiplayer images from examples, drop lsp/Dockerfile (#11341)
* chore: retire the standalone lsp and multiplayer images from examples, drop lsp/Dockerfile

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

* chore: drop the unbuilt DockerfileMultiplayer, document running the LSP from windmill-extra

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

* fix(examples): ecs terraform destroys cleanly and gives private instances no public ip

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

* fix(examples): give windmill-extra on ecs a WINDMILL_BASE_URL for multiplayer auth, address review

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

* fix(examples): make the ecs example upgrade cleanly from the standalone lsp/multiplayer stack

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

* fix(examples): name the extra target group by prefix so create_before_destroy can replace it

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

* docs(examples): note the brief editor-socket gap when upgrading the ecs example

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

* docs(examples): the debugger stays off after the ecs upgrade unless enabled

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-09-25 17:13:06 +02:00
..

windmill-cloudformation

Cloudformation Template for Windmill on AWS EKS

Overview

This CloudFormation template automatically deploys Windmill on AWS EKS. The deployment includes:

  • An EKS cluster with configurable node types and sizes
  • An RDS PostgreSQL database for Windmill data
  • AWS Load Balancer Controller for handling ingress traffic
  • Proper network configuration with VPC, subnets, and security groups
  • A fully automated installation of Windmill via Helm

Parameters

The template accepts various parameters to customize your deployment:

  • NodeInstanceType: EC2 instance type for EKS worker nodes (t3.small to r5.2xlarge)
  • NodeGroupSize: Number of EKS worker nodes
  • RdsInstanceClass: RDS instance class for the PostgreSQL database (db.t3.micro to db.r5.2xlarge)
  • DBPassword: Password for the PostgreSQL database
  • WorkerReplicas: Number of Windmill worker replicas
  • NativeWorkerReplicas: Number of Windmill native worker replicas
  • Enterprise: Enable Windmill Enterprise features (requires license key)

Customization

To modify the Helm chart configuration or update the template, refer to the official Windmill Helm chart repository: https://github.com/windmill-labs/windmill-helm-charts

Documentation

For more information about Windmill's Helm chart deployment options, see: https://www.windmill.dev/docs/advanced/self_host#helm-chart

For detailed information about setting up RDS for Windmill on AWS: https://www.windmill.dev/docs/advanced/self_host/aws_ecs#create-a-rds-database

Deployment

  1. Upload the CloudFormation template to your AWS account
  2. Fill in the required parameters
  3. Deploy the stack
  4. Access Windmill using the URL provided in the Outputs section of the stack

After deployment, you can access Windmill via the LoadBalancer URL shown in the CloudFormation stack outputs.