PRODUCTION CLOUD

AWS ECS production deployment

RAIQL 1.0 adds the first provider-specific production cloud adapter without storing cloud credentials or secret values in source.

Declare AWS ECS

USE STACK
  BACKEND NEXTJS,
  DATABASE POSTGRESQL,
  CLOUD AWS;

ENVIRONMENT development, staging, production;
SECRET DATABASE_URL, RAIQL_JWT_SECRET;

DEPLOY AWS ECS;

The compiler generates an ECS/Fargate task-definition bundle, service template, Secrets Manager mapping, execution-role policy and deployment metadata.

Prepare, don't leak

Generated AWS files contain placeholders for account, region, ECR repository, cluster, service, networking and image tag. Secret values are never copied from RAIQL source or local profiles into the deployment bundle.

CLI deployment plan

terminal

raiql deploy --env production --target aws-ecs

The command regenerates the application and writes a non-secret plan under .raiql/deploy/production/. RAIQL 1.0 intentionally performs no remote AWS mutation; your operator or CI/CD pipeline registers the task definition and updates the ECS service.

Managed production database

For PostgreSQL applications the ECS bundle expects DATABASE_URL to come from Secrets Manager. Production deployments should use managed PostgreSQL such as Amazon RDS rather than the local development Docker database.

Continue exploring RAIQLOpen the playground →