Swftbox validates its GCP-to-AWS migration and lays a Terraform IaC foundation

Swftbox had moved its cloud platform from Google Cloud Platform to AWS but needed an independent engineering review to confirm the migration was sound before scaling on it. The platform spans multiple production workloads — a fleet of active application repositories deploying to a mix of Amazon ECS clusters, S3 + CloudFront front ends, and Lambda utility services in me-central-1. Two problems stood in the way of confidence. Nobody had checked the post-migration estate against best practices, so anti-patterns could be hiding anywhere. And the application infrastructure lived in the console rather than as reproducible Infrastructure-as-Code, making environments hard to reason about and deployments hard to make reliable.

VeUP came at it three ways. First, the audit: VeUP Engineering went through the migrated AWS workloads against best practices and laid out exactly how to fix each anti-pattern it found. Second, the modernization picture: a high-level target architecture mapping each active repository to its correct AWS runtime — Amazon ECS, S3 + CloudFront, or AWS Lambda. Third, the codebase: guidelines and modules for rebuilding the migrated workloads as Terraform IaC, organized per-repository across dev/QA/prod state, on top of Swftbox’s existing AWS network stack. The audit then fed a follow-on modernization roadmap: migrating CI/CD from GitLab CI to GitHub Actions; a reusable AWS Secrets Manager module wired into the pipelines; and deployment-reliability enhancements — end-to-end visibility from Amazon ECR through Amazon ECS, post-deploy ECS health checks, and circuit-breaker auto-rollback to the last known-good task definition. Pipeline deploys use AWS OIDC (keyless, role-assumed; no static keys).