> For the complete documentation index, see [llms.txt](https://docs.bindplane.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bindplane.com/deployment/aws.md). # AWS ECS Deploy BDOT Collectors on AWS ECS using Fargate and EC2 launch types with CloudFormation templates. | Feature | Fargate | EC2 | | -------------- | ------------------------------- | --------------------------------------- | | **Management** | Serverless, no EC2 management | Full control over instances | | **Cost** | Pay-per-use | More predictable pricing | | **Best For** | Variable workloads, quick setup | Consistent workloads, cost optimization | ### Prerequisites * AWS CLI v2.x configured * Valid AWS account with appropriate permissions * Bindplane OTel Collector secret key ### Architecture * ECS Cluster with auto-scaling * VPC with public/private subnets * OpAMP protocol for server communication * CloudWatch logging ### Security * VPC isolation with security groups * RDS encryption at rest and in transit * IAM roles with least-privilege access * Private subnets for database and internal services ### Monitoring * CloudWatch logs and metrics * ECS health checks * ALB health checks * Custom health endpoints --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.bindplane.com/deployment/aws.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.