If you are on AWS and you are not using the (unfortunately named) Copilot CLI[0], you're opting in to the full complexity of AWS. Copilot fortunately makes mos

If you are on AWS and you are not using the (unfortunately named) Copilot CLI[0], you're opting in to the full complexity of AWS. Copilot fortunately makes most common scenarios waaaay easier to build, setup, and deploy including building staged environments following best practices for AWS (separate accounts; I know, in and of itself kind of a pain in the ass). It encodes the most common types of application backend deployments into simple patterns and makes it pretty easy to build full and deploy full application stacks (Route 53 -> CloudFront -> S3 (static FE) -> ALB + SGs + TGs -> ECS cluster (backend APIs) -> DBs) With the Copilot CLI, I find the experience on AWS significantly better and in some ways, more well-rounded than on GCP. GCP's Firebase tooling and CLI comes close, but alas, Firebase does not have the same level of extensibility that Copilot offers by allowing you to include both CDK and CloudFormation as extension points which then allows you to use Copilot to manage a good chunk of your AWS infra with a single, easy to use CLI. For simple apps, I prefer Firebase on GCP. For more complex apps, I think Copilot on AWS is really, really good. One caveat: ECS is much slower to roll nodes over to new versions compared to Cloud Run. Best I could achieve on it was ~180s for a Blue/Green rollover whereas Cloud Run does this in seconds. TL;DR: if you are not an enterprise and you are on AWS, your life will assuredly be better with Copilot instead of CDK, CloudFormation, or almost any other solution for deploying to AWS. [0] https://aws.github.io/copilot-cli/ https://aws.github.io/copilot-cli/