> ## Documentation Index
> Fetch the complete documentation index at: https://ravion-b90c0359-mintlify-710044b6.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.
# How to deploy Django to AWS
> Deploy a Django application on ECS Fargate behind an Application Load Balancer to your AWS account with Ravion, including PostgreSQL, autoscaling, and CI/CD.
Deploy Django with Gunicorn on ECS Fargate behind an Application Load Balancer.
## Prerequisites
* A Git repository containing your application and its production build command.
* A Ravion account with your AWS account connected. Start free at [Ravion signup](https://app.ravion.com/signup).
* The Ravion CLI installed and authenticated. See [CLI installation](/cli/installation).
The examples use `my-org/my-app` as a placeholder. Replace it with your repository before applying the config.
1. Before any other action, read and follow [https://www.ravion.com/docs/start-here#agent-workflow](https://www.ravion.com/docs/start-here#agent-workflow) as the mandatory agent workflow.
2. Use [https://www.ravion.com/docs/deploy/aws/django](https://www.ravion.com/docs/deploy/aws/django) as the framework-specific source of truth.
3. Confirm this repository contains Django and locate the project root in a monorepo.
4. Inspect `pyproject.toml`, `requirements.txt`, Django settings, and Docker files to detect the real WSGI/ASGI module, migrations, Gunicorn or Uvicorn command, port, and health path; never use `runserver`.
5. Generate `ravion.yaml` with `rvn-aws-network` + `rvn-ecs-cluster` + `rvn-ecs-web` + `rvn-rds`, real repository values, and a documented Secrets Manager step for `DATABASE_URL`.
6. Ask the user for AWS account IDs, repository slugs, project IDs, Django module paths, or database credentials before proceeding; do not guess.
## Configure the deployment
Django's production documentation recommends a WSGI server instead of `runserver`.
This example uses [Railpack](https://railpack.com) for the build. Use `build_source: dockerfile` instead when you need a custom Dockerfile. Railpack detects Django from the application files and dependencies.
Railpack detects Django from its dependencies or `manage.py`. Its default start command runs `python manage.py migrate` and then Gunicorn with the detected application module. Migrations run on every boot by default, which can race when multiple ECS tasks start; move migrations to a separate release step for multi-task deployments. Set `RAILPACK_DJANGO_APP_NAME` when the WSGI module is not the detected default. Ravion injects `PORT` automatically from `container_port`.
```yaml ravion.yaml theme={null}
project:
givenId: django-app
name: Django app
environments:
- givenId: production
name: Production
moduleInstances:
- givenId: network
name: Network
type: rvn-aws-network
version: 1.0.0
input:
aws_account_id: ravion-prod
aws_region: us-east-1
name: django-production
- givenId: cluster
name: ECS cluster
type: rvn-ecs-cluster
version: 1.0.0
input:
network:
moduleGivenIdRef: network
name: django-production
- givenId: database
name: PostgreSQL database
type: rvn-rds
version: 1.0.0
input:
network:
moduleGivenIdRef: network
name: django-production-db
db_name: django
username: django
engine_major_version: "15"
- givenId: web
name: Django web service
type: rvn-ecs-web
version: 1.0.0
input:
cluster:
moduleGivenIdRef: cluster
name: django-production-web
build_source: railpack
source_repo: my-org/my-django-app
container_port: 8000
fargate_size:
vcpu: 0.5
memory_gb: 1
```
Run migrations as a deployment step, set `ALLOWED_HOSTS` and `SECRET_KEY` as runtime values, and use `DATABASE_URL` for your database connection. Populate that secret from the RDS outputs before applying the service.
## Apply and connect your domain
```bash theme={null}
ravion project create --given-id django-app --name "Django app"
ravion project config apply django-app --file ravion.yaml --dry-run
ravion project config apply django-app --file ravion.yaml
```
Follow [custom domains](/guides/custom-domains) to connect your domain to the Application Load Balancer.
## Next steps
Point a domain at your deployed service and manage its certificate.
Preview and apply Ravion configuration from source control.
Add approvals, migrations, and deployment automation.
Inspect deploy output and production health in Ravion.