菜单
Guidance for deploying FeatBit on AWS, including ECS Fargate, EKS (Kubernetes), and Terraform. Use when user asks about deploying or running FeatBit on AWS. Do not use for Docker Compose deployments or Kubernetes deployments on non-AWS clouds.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Expert guidance for instrumenting FeatBit experiments and A/B tests — recording flag-evaluation exposures and metric events so the experimentation engine can analyze variant performance. Use when user asks about "experimentation", "A/B test", "AB test", "AB testing", "split test", "multivariate test", "variant test", "control vs treatment", "experiment instrumentation", "flag exposure", "track-service", "track event", "metric event", "conversion tracking", "experiment analysis", "sendToExperiment", or wires variant traffic into a FeatBit experiment. Pairs with featbit-sdks-* (flag evaluation) and featbit-evaluation-insights-api (custom-platform SDKs). Do not use for general flag-management API operations — see featbit-rest-api.
Expert guidance for integrating FeatBit Node.js Server SDK. Use when user asks about "Node.js SDK", "Node server SDK", "FeatBit Node", or mentions server-side TypeScript/JavaScript with FeatBit. Do not use for browser JavaScript, React, React Native, Python, Java, Go, or .NET questions.
Expert guidance for deploying FeatBit with Docker Compose across three tiers - Standalone (PostgreSQL only), Standard (PostgreSQL/MongoDB + Redis), and Professional (+ ClickHouse + Kafka). Use when user mentions "docker-compose", "deploy with Docker", "standalone vs standard vs pro", works with docker-compose.yml files, or asks about container configuration, environment variables, or production Docker setup. Do not use for Kubernetes, Helm, AWS ECS/EKS, or cloud-provider-specific deployments.
FeatBit documentation router that provides likely relevant docs.featbit.co URLs when other FeatBit skills cannot fully answer. Use when user asks about FeatBit features, concepts, deployment, SDKs, API, integrations, or architecture and the response should point to official documentation for deeper detail. Do not use when another FeatBit skill already provides a complete answer.
Expert guidance for using the FeatBit REST API to manage projects, environments, and feature flags programmatically. Use when user asks about "FeatBit API", "REST API", "create project API", "create environment API", "create feature flag API", "API authentication", "OpenAPI key", or needs to automate FeatBit operations via HTTP endpoints. Do not use for SDK integration, deployment configuration, or flag evaluation questions.
Expert guidance for using FeatBit's Flag Evaluation REST API and Track Insights REST API to build custom SDKs for platforms without an official FeatBit SDK. Use when user asks about "evaluation API", "flag evaluation endpoint", "evaluate feature flags via HTTP", "track insights", "insight tracking API", "build custom SDK", "Kotlin SDK", "Android SDK", "iOS SDK", "Swift SDK", "Unity SDK", "embedded SDK", "mobile feature flags", "sendToExperiment", or needs to call FeatBit evaluation server directly. Do not use for management API operations (projects, environments, flag CRUD) — use featbit-rest-api for those. Do not use when an official SDK exists for the target language.
| name | featbit-deployment-aws |
| description | Guidance for deploying FeatBit on AWS, including ECS Fargate, EKS (Kubernetes), and Terraform. Use when user asks about deploying or running FeatBit on AWS. Do not use for Docker Compose deployments or Kubernetes deployments on non-AWS clouds. |
| license | MIT |
| metadata | {"version":"1.0.0","category":"deployment"} |
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
