copilot-cli VS apprunner-roadmap

AWS Copilot CLI is an open source command line interface for running containers on AWS App Runner, Amazon Elastic Container Service (ECS), and AWS Fargate.

sudo curl -Lo /usr/local/bin/copilot https://github.com/aws/copilot-cli/releases/latest/download/copilot-linux && sudo chmod +x /usr/local/bin/copilot

Check out AWS Copilot CLI: https://aws.github.io/copilot-cli/

This is by far the best way to deploy compute into AWS in containerized workloads.

The abstraction you want is Jobs: ttps://aws.github.io/copilot-cli/docs/concepts/jobs/

Building this any other way on AWS would require provisioning multiple artifacts. The Copilot Jobs abstraction basically encapsulates the provisioning of those artifacts into one repeatable pattern.

AWS Copilot CLI is a tool that lets you deploy production-ready, scalable services on AWS from a Dockerfile in one command.

and here is the copilot page if you are interested https://aws.github.io/copilot-cli/

For larger high availability required things, AWS ECS with RDS, ElastiCache, CloudFront, S3, etc.. Really like Copilot for deployment/env/secret/sidecar management (probably needs a rename now): https://aws.github.io/copilot-cli/

We are spending about 60% less. Workload has actually lessened since AWS is so much more stable. Getting to a similar DX as Heroku was quite the lift, but once it's done, it's done. These days we generally only have outages when we screw something up ourselves. I recommend https://github.com/aws/copilot-cli for starting out on ECS.

I'd recommend checking out AWS Copilot (https://aws.github.io/copilot-cli/)

Examples for products in this category are: Google Cloud Run, AWS App Runner, Azure Container Apps. Each has different scalability, cost, and integration trade-offs.

The deployment failed, and there were no logs available to help me debug the issue. There's an open issue on GitHub that has been around for over a year, but there doesn't seem to be a solution in sight.

If you're looking for something simple, that you can onboard to relatively quickly, that doesn't require a lot of oversight, consider App Runner, https://aws.amazon.com/apprunner/. EKS and Kubernetes are extremely powerful and flexible, but they come a fair amount of complexity. If you don't care about the orchestrator (or running your application in another cloud), try App Runner.

The reader will learn how to create a web application firewall with AWS WAF and AWS App Runner as a web application. AWS App Runner is an AWS service that deploys web applications or API using Amazon ECR or GitHub only. While AWS WAF (Web Application Firewall) is an AWS service that can protect the web application.

Yes, exactly. That's the problem. I found the issue here.

I wonder what the aversion is to using a plain old server / vps. It's really not that difficult to deploy nowadays [0][1][2][3] and I'd rather get an $8 bill every month as insurance than ever worry about shit like OP just went through. It'll probably be more performant anyway due to cold starts and "edge" still having to hit us-east-1 for data.. cache your static files with Cloud Flare/Front. People are always surprised by how much traffic a single VPS can take[4] and believe it all has to be serverless to be web scale. I believe HN still runs on a single core or something.

There's a ton of places to get cloud credits as well, too many to link, so just Bing™ it

[0] https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_...

[1] https://aws.amazon.com/apprunner/

[2] https://cloud.google.com/run

[3] https://render.com/

[4] https://news.ycombinator.com/item?id=34676186

AWS AppRunner could do more or less everything. You'd have to build a container image yourself, since AppRunner does not have C++ support for the "Code-based" service, but building a container really isn't more complex than installing that bare metal server. (Really, pick an OS, install dependencies, copy your code, start a service. That is all.)

App Runner