Is there no AWS equivalent to GCP cloud run (cloud run costs blew AWS away in this example)?

Question

I just tested Elastic Beanstalk which seemed like the closest thing (just deploy docker) but then when I set it to scale from 0 to 5 instances, it correctly scales to 0 and then never scales back up from 0. ie. It properly shuts down pre-production and staging environments on weekends and nights but then would never turn on again unlike GCP cloud run.

The savings on GCP cloud run (because things shut down to 0) vs. AWS is insanely huge. Comparing my previous company (25 people), GCP costs were 50 bucks for the month and currently because nothing turns off, we are seeing 600 for approximately equivalent stuff.

As we scale and grow(more and more services), I see this only getting worse and worse with more and more services that can't scale back to 0 when not in use :(. Even at Twitter, staging and testing environments, we want scaled to 0 when not in use automatically to save TONS of money.

For startups, AWS seems like a very bad cost model these days unless using lambdas which is only functions. They have no lambdas equivalent for services like cloud run? or do they?

I hope I am wrong here and someone knows something as once we scale up with more services, our costs are going to just get worse with 3 environments, I do not want 3x the cost since many of these should spin down automatically and back up automatically.

EDIT: Devops just tried AWS EKS to set it to min instance count=0 but then just got timeouts as it never spun up instances. It seems it scales to 0 fine but can't scale out of 0 like cloud run :(. That is odd as many documents claim AWS EKS scales to 0 but IMHO, you can't say that if you can't scale back out of 0 to 1, 2, 3 under load. I am very confused then and wondering if configuration is wrong?

Answer 1

App Runner is near one to one with cloud run but there is a github issue request scale to 0. It is basically the same service so thanks to Adi Dembark above!!!