Guides FeatBit deployment on AWS via ECS Fargate with Terraform, EKS Kubernetes, and high availability configurations for multiple services.
npx claudepluginhub joshuarweaver/cascade-code-devops-misc-1 --plugin featbit-featbit-skillsThis skill uses the workspace's default tool permissions.
**Option 1 — ECS Fargate + Terraform (recommended baseline)**
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
Option 1 — ECS Fargate + Terraform (recommended baseline) The official featbit-terraform-aws project provides a ready-to-use Terraform setup for deploying FeatBit on AWS ECS Fargate with ALB, Aurora PostgreSQL, and ElastiCache. This is the recommended starting point for most AWS deployments.
Option 2 — AWS Kubernetes (EKS) For teams already running Kubernetes on AWS, use the Helm chart approach instead. See the featbit-deployment-kubernetes skill for full guidance.
A: Yes. All four FeatBit services (ui, api-server, evaluation-server, data-analytics-server) are stateless and support multiple concurrent instances. Place an ALB in front of each service first, then increase the task count.
Note the distinction: running multiple tasks in the same AZ improves fault tolerance (a crashed task is replaced while others keep serving traffic), but it is not true High Availability. For HA, tasks must span multiple subnets in different AZs so the service survives an entire AZ (Availability Zone) going down.
Not all services are equally critical — evaluation-server and api-server have direct user impact if they go down and should be scaled first. ui only affects the portal. data-analytics-server only affects analytics; flags keep working without it.
references/ecs-high-availability.md