> ## 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.
# Deploy to AWS
> Step-by-step guides for deploying popular application frameworks to your own AWS account with Ravion, including ECS Fargate, S3, and CloudFront setups.
Use these quickstarts to deploy framework applications to AWS with Ravion. Choose a static site deployment with S3 and CloudFront or a server deployment with ECS Fargate behind an Application Load Balancer. [Railpack](https://railpack.com) can build supported application stacks without a custom Dockerfile.
## 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](https://www.ravion.com/docs/deploy/aws) as the framework-specific source of truth.
3. Inspect this repository to identify its framework, application root, and whether it needs static hosting or an ECS server. Search monorepo workspaces rather than assuming the repository root.
4. Read the matching framework guide linked on this page, then inspect package manifests, framework config, Dockerfiles, and scripts to determine the real build command, output directory, start command, port, and health path.
5. Generate `ravion.yaml` from that guide's module set with real AWS account, region, repository, branch, and runtime values substituted. Use Secrets Manager and an RDS module where the framework requires a database.
6. Ask the user for any AWS account ID, repository slug, project ID, database credential, command, path, or port before proceeding; do not guess.
## Static sites: S3 and CloudFront
Deploy an Angular production build to S3 and CloudFront.
Deploy an Astro static build to S3 and CloudFront.
Deploy a Docusaurus documentation site to S3 and CloudFront.
Deploy Gatsby's generated site to S3 and CloudFront.
Deploy a React single-page app to S3 and CloudFront.
Deploy a Solid single-page app to S3 and CloudFront.
Deploy SvelteKit statically or with a Node server.
Deploy a Vike static site to S3 and CloudFront.
Deploy a Vite single-page app to S3 and CloudFront.
Deploy a Vue application to S3 and CloudFront.
## Server applications: ECS Fargate and ALB
Run Backstage on ECS Fargate behind an Application Load Balancer.
Run a Bun HTTP server on ECS Fargate.
Run Django with Gunicorn on ECS Fargate.
Run FastAPI with Uvicorn on ECS Fargate.
Run Flask with Gunicorn on ECS Fargate.
Run Hasura on ECS Fargate with PostgreSQL on RDS.
Run a Hono Node.js server on ECS Fargate.
Run Laravel with FrankenPHP on ECS Fargate and PostgreSQL on RDS.
Run NestJS on ECS Fargate behind an Application Load Balancer.
Run Next.js SSR on ECS Fargate behind an Application Load Balancer.
Run a Node.js or Express server on ECS Fargate.
Run a Nuxt server-rendered app on ECS Fargate.
Run Ruby on Rails with Puma on ECS Fargate and PostgreSQL on RDS.
Run RedwoodJS on ECS Fargate with PostgreSQL on RDS.
Run a Remix app on ECS Fargate behind an ALB.
Run Strapi on ECS Fargate with PostgreSQL on RDS.
Run TanStack Start on ECS Fargate behind an ALB.
Each example uses module versions from the current Ravion standard library. Replace the
placeholder repository and AWS account values with your own before applying a file.