Deploy on AWS

Recommended AWS mapping

• ECR for application and Go-service container images.
• ECS Fargate or EKS for application and worker containers.
• Application Load Balancer for HTTPS routing and health checks.
• RDS for PostgreSQL with PostGIS; use Multi-AZ for production where required.
• ElastiCache for Redis for managed cache/queue/session infrastructure.
• S3 for durable object storage and generated downloads; CloudFront is optional for public assets.
• Secrets Manager / Parameter Store for application secrets.
• CloudWatch for logs, metrics, alarms, and deployment diagnosis.

Deployment sequence

Build an immutable production image, push to ECR, run database migrations as a controlled one-off task, update the application service, update Horizon/worker services, and wait for health checks before completing the release.

Security

Place database and Redis in private subnets, use security groups rather than public ports, terminate TLS at the ALB, and give task roles only the AWS permissions they require.

The repository's AWS workflow is currently retained as a manual/historical recovery path; adapt it to the target account rather than assuming its old resource names are production-ready.