Guides deploying FeatBit feature flag platform on AWS using ECS Fargate with Terraform, or EKS (Kubernetes). Includes high-availability advice for multi-AZ setups.
How this skill is triggered — by the user, by Claude, or both
Slash command
/featbit-featbit-skills:featbit-deployment-awsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Option 1 — ECS Fargate + Terraform (recommended baseline)**
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
npx claudepluginhub joshuarweaver/cascade-code-devops-misc-1 --plugin featbit-featbit-skillsDeploys FeatBit to Kubernetes using Helm Charts with two architecture tiers (Standard and Professional), multiple service exposure methods, external databases, and auto-scaling.
Deploys and operates containerized workloads on ECS, Fargate, and ECR. Covers task definitions, service scaling, blue/green deployments, ECS Exec debugging, and ECR lifecycle policies. Use when deploying, debugging, or optimizing containers on AWS.
Implements feature flags for controlled rollouts, A/B testing, canary deployments, and kill switches. Use for gradual feature deployment and lifecycle management.