How rondrae/strapi-ecs works
This repository defines AWS infrastructure for an ECS Fargate service reached through a public load balancer, with Aurora PostgreSQL, S3, logging, and IAM support. The documented workflow is to apply the Terraform configuration, run tasks privately, and serve their HTTP endpoint through the ALB; outputs expose service and storage endpoints. The README also documents optional RDS Proxy and an ECR repository. Source excerpts were unavailable, so relationships here are limited to those stated in the README and file names.
Main entry points: ecs.tf ECS Fargate service · aurora.tf Aurora PostgreSQL · outputs.tf Infrastructure outputs · alb.tf Application Load Balancer
Components 13
Inputs and entry
- Terraform inputs
variables.tf - AWS provider setup
main.tf - Application Load Balancer
alb.tf - Infrastructure outputs
outputs.tf
Service runtime
- ECS Fargate service
ecs.tf - Container repository
ecr.tf
Data services
- Aurora PostgreSQL
aurora.tf - RDS Proxy
aurora.tf - Private S3 bucket
s3.tf
Access and operations
- ECS IAM roles
iam.tf - Strapi secrets
strapi_secrets.tf - Network endpoints
endpoints.tf
Other components
- Infrastructure operator
Connections 10
- Infrastructure operator → AWS provider setup: applies configuration
- Terraform inputs → AWS provider setup: configures
- Application Load Balancer → ECS Fargate service: routes HTTP traffic
- ECS Fargate service → Container repository: pulls image
- ECS Fargate service → ECS IAM roles: uses roles
- ECS Fargate service → Aurora PostgreSQL: connects to database
- RDS Proxy → Aurora PostgreSQL: proxies connections
- Application Load Balancer → Infrastructure outputs: exposes DNS
- Private S3 bucket → Infrastructure outputs: exposes bucket
- Aurora PostgreSQL → Infrastructure outputs: exposes endpoints