# Install on AWS ECS

> **Sentinel v2 (beta):** This page documents Sentinel v2, a beta rewrite that may change before the stable release. It does not apply to Sentinel v1, the current stable version: see the [Sentinel v1 documentation](/docs/sentinel.md).

A guide for running Sentinel v2 on Amazon Elastic Container Service (ECS) will be added later in the beta, together with a CloudFormation template for v2.

<Callout type="warning" title="The v1 CloudFormation template doesn't work with v2">

The ALTCHA CloudFormation template (`altcha-sentinel-deploy-aws`) deploys Sentinel v1. Don't point its `ImageURI` at a v2 image: v2 reads a configuration file that the template has no way to provide, listens on different ports, and runs as a different user than the template's EFS volume expects.

Until the ECS guide is available, run Sentinel v2 with one of these:

- [Install with Docker](/docs/sentinel/v2/install/docker/): a single container, for example on an EC2 instance.
- [Install with Docker Compose](/docs/sentinel/v2/install/docker-compose/): one instance, or two replicas with PostgreSQL and Valkey, on one host.
- [Install on Kubernetes](/docs/sentinel/v2/install/kubernetes/): plain manifests that also work on Amazon EKS.

The requirements on [Install Sentinel](/docs/sentinel/v2/install/) apply on AWS too. Behind an Application Load Balancer, list the load balancer's subnets in `trusted_proxies` and keep `idle_timeout` above its 60-second keep-alive; see [Listeners & reverse proxy](/docs/sentinel/v2/configure/listeners/).
