AWS Migration Guides
This section contains the working documents for the migration from Docker Compose on EC2 to AWS ECS.
Documents
- 01 AWS ECS Migration and CI/CD Plan
- 02 AWS ECS Runtime Inventory
- 03 AWS ECS Shape Decision
- 04 AWS ECS Environment and Secrets Map
- 05 AWS Staging Infrastructure Plan
- 06 AWS ECS Deploy and Rollback Runbook
- 07 AWS ECS Networking and Service Discovery Map
- 08 AWS Infrastructure and IaC Decision
- 09 AWS Terraform State Ownership and Project Layout
- 10 AWS Terraform Backend and Bootstrap Plan
- 11 AWS Production Rebuild and Coexistence Plan
- 12 AWS Database Connectivity and VPC Peering Plan
- 13 AWS Staging Terraform Implementation Blueprint
- 14 AWS Staging Terraform Resource Checklist
- 15 AWS Staging Terraform Apply Order and Outputs
- 16 AWS ECS Bootstrap Plan and Todo
- 17 AWS ECS Staging Rollout Sequence and Migration Order
- 18 AWS ECS Staging Blockers and Functional Cluster Path
- 19 AWS ECS Anisette Account Bootstrap Runbook
- 20 AWS Staging Migrations Runbook
How To Use This Section
Start with 01 as the main migration plan, then use 02 to 05 as supporting reference documents, finish with 06 for the operational rollout runbook, use 07 for networking and service discovery details, use 08 for the infrastructure and IaC decision, use 09 for Terraform ownership and state layout, use 10 for backend and bootstrap details, use 11 for production coexistence during the rebuild, use 12 for the database connectivity path, use 13 for the staging implementation blueprint, use 14 for the staging Terraform resource checklist, use 15 for the staging apply order and outputs, use 16 for the end-of-day bootstrap handoff, use 17 for the staging rollout sequence and migration order, use 18 for the current blocker summary and recovery path, and use 19 for the Anisette account bootstrap step.
The runtime inventory records the current Compose services, ports, mounts, and configuration sources.
The migration plan maps those services into ECS tasks, service discovery, staging infrastructure, and CI/CD flow. Use 20 for the repeatable staging schema migration procedure.