AWS
Microservices
intermediate
Fargate Services + API Gateway — AWS Architecture Template
API Gateway routing to Fargate microservices, each owning its own datastore, with no servers to manage.
Why this architecture works
- Fargate removes node management entirely — each task gets right-sized, isolated compute
- API Gateway centralises throttling, API keys, and request validation in front of all services
- Database-per-service (DynamoDB for orders, RDS for catalog) prevents shared-schema coupling
- Secrets are injected at task launch from Secrets Manager, never baked into container images
- Internal ALB keeps service-to-service traffic private inside the VPC
What's inside (9 resources)
API Gateway
aws-api-gateway
Internal ALB
aws-alb
ECS Cluster
aws-ecs
Orders Service
aws-fargate
Catalog Service
aws-fargate
Orders Table
aws-dynamodb
Catalog DB
aws-rds
Service Secrets
aws-secrets-manager
Service Metrics
aws-cloudwatch
From template to running infrastructure
- Open this template in the CloudForge visual designer (free account, no credit card).
- Customize resources, names, and connections on the drag-and-drop canvas — or ask Vani, the AI architect, to adapt it.
- Generate production-ready Terraform or CloudFormation in one click.
- Review the plan diff and security scan, then deploy with human approval.