Skip to main content
Runlayer’s ECS Terraform module provisions the application services and supporting AWS infrastructure in your account. The standard configuration creates a VPC, load balancer, Aurora PostgreSQL, ElastiCache Redis, Secrets Manager secrets, and ECS Fargate services. Optional GPU features also use EC2. You own the AWS account, Terraform state, configuration, upgrades, and recovery. Runlayer provides application artifacts, onboarding credentials, and support. See Shared Responsibility.

​
Deployment path

Follow these pages in order:
  1. Collect Runlayer-provided inputs and review egress requirements.
  2. Complete ECS prerequisites: tools, AWS identity, state storage, domain, and Bedrock access.
  3. Choose networking and private connectivity, database and service configuration, and any optional features required at launch.
  4. Follow the deployment guide: configure, initialize, validate, plan, apply, and verify.
  5. Use Updates and the module changelog for subsequent releases.

​
Artifacts and versions

Module and application versions are separate. The module changelog lists the application default for each release. The Terraform inputs reference documents configuration; it is not the installation sequence. Runlayer grants S3 download and ECR pull access during onboarding. Confirm access for the deployment identity and runtime image-pull identity before starting.

​
Plan capacity and cost

Use the AWS Pricing Calculator with your region, service replica counts, Aurora ACUs, Redis sizing, NAT gateways, logs, data transfer, and optional GPU capacity. Feature selection and availability requirements materially change the cost; the default configuration is not a fixed-price deployment. For Kubernetes on EKS or GKE, see Kubernetes.