AWS Highly Available Blog Backend - Enterprise Edition
AWS • Cloud Architecture • SRE · Actif · Cloud Architect • DevOps · Labs AWS → migration (2026)
Migration du backend Express (backend-init) vers AWS multi-AZ : ECS Fargate, Aurora, ElastiCache, S3/CloudFront, WAF, Terraform, OIDC CI/CD, chaos et FinOps - plateforme Cloud production-ready.
Problème
Un backend VPS prouve le métier ; il ne prouve pas HA multi-AZ, IAM, IaC cloud, scaling géré ni recovery chronométré. Sans migration disciplinée, les labs AWS restent théoriques.
Solution
- ECS Fargate multi-AZ derrière ALB + Auto Scaling + rolling deploy
- Aurora PostgreSQL Multi-AZ (writer/reader, PITR) + ElastiCache Redis HA
- S3 privé + CloudFront + presigned URLs pour médias
- VPC segments + SG/NACL + endpoints + Flow Logs
- WAF managed rules + rate-based + TLS ACM
- Secrets Manager / KMS + IAM roles + GitHub OIDC
- Terraform modules staging/prod + pipeline fail-closed
- Obs CloudWatch/OTel + chaos + DR + FinOps documentés
Stack
Express, TypeScript, OpenTelemetry, Aurora PostgreSQL, ElastiCache Redis, S3, AWS ECS Fargate, ECR, ALB, CloudFront, Route 53, WAF, VPC, Secrets Manager, KMS, CloudWatch, X-Ray, Terraform, GitHub Actions OIDC, k6, Trivy