Not familiar enough about GCP internal, but AWS prices are way higher than what's quoted in the article. You'll get billed for bandwidth, should you want any logs of your control plane you'll pay them at a premium so high* it will dwarf the cluster price and machine price combined. And for ~$70/month, you get the cluster API, not the EC2 compute required for worker nodes.
* Because vended logs to s3 are not supported (https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/AWS..., https://github.com/aws/containers-roadmap/issues/1141)
In Cheap self-hosted Kubernetes on Hetzner cloud (2025)aws
containers-roadmap
Shell2018–2026
aws / containers-roadmap
containers-roadmap
This is the public roadmap for AWS container services (ECS, ECR, Fargate, and EKS).
32Distinct people
35Mentions
0Explicit recommenders
5.4KGitHub stars
What to know before exploring
What it is
This is the public roadmap for AWS container services (ECS, ECR, Fargate, and EKS).
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year35 dated mentions
Observed mentions: 2018-12-12 11:04:40 UTC to 2026-07-21 19:57:17 UTC.
* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 3 | 3 | 0 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 8 | 1 | 7 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 10 | 0 | 10 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 4 | 1 | 3 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 6 | 0 | 6 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 1 | 0 | 1 |
From the project README
An excerpt from the repository, fetched Nov 13, 2026.
Read the project’s introduction
Containers Roadmap
This is the public roadmap for AWS container services (ECS, ECR, Fargate, and EKS).
Introduction
This is the public roadmap for AWS Container services.
Knowing about our upcoming products and priorities helps our customers plan. This repository contains information about what we are working on and allows all AWS customers to give direct feedback.
See the roadmap »
Other AWS Public Roadmaps
AWS Proton
CloudFormation coverage
AWS Elastic Beanstalk
Amazon EC2 Spot Instances integrations
AWS Controllers for Kubernetes (ACK)
AWS CDK
AWS App Runner
Developer Preview Programs
We now have information for developer preview programs within this repository. Issues tagged Developer Preview on the public roadmap are active preview programs.
Current Programs
There's more to come! Stay tuned!
Past Programs
EKS on ARM - EKS on AWS Graviton2 is generally available
ECS Multiple Target Groups - Support for multiple target groups on ECS is generally available
Firelens - Support for custom log routing is generally available
EKS Windows - Support for Windows on EKS is generally available
Security disclosures
If you think you’ve found a potential security issue, please do not post it in the Issues. Instead, please follow the instructions here or email AWS security directly.
FAQs
Q: Why did you build this?
A: We know that our customers are making decisions and plans based on what we are developing, and we want to provide our customers the insights they need to plan.
Q: Why are there no dates on your roadmap?
A: Because job zero is security and operational stability, we can't provide specific target dates for features. The roadmap is subject to change at any time, and roadmap issues in this repository do not guarantee a feature will be launched as proposed.
Q: What do the roadmap categories mean?
Just shipped - obvious, right?
Coming soon - coming up. Think a couple of months out, give or take.
We're working on it - in progress, but further out. We might still be working through the implementation details, or scoping stuff out.
Researching - We're thinking about it. This might mean we're still designing, or thinking through how this might work. This is a great phase to send how you want to see something implemented! We'd love to see your usecase or design ideas here.
Q: Is everything on the roadmap?
A: The majority of our development work for Amazon ECS, Fargate, ECR, EKS and other AWS-sponsored OSS projects are included on this roadmap. Of course, there will be technologies we are very excited about that we are going to launch without notice to surprise and delight our customers.
Q: How can I provide feedback or ask for more information?
A: Please open an issue!
Q: How can I request a feature be added to the roadmap?
A: Please open an issue! You can read about how to contribute here. Community submitted issues will be tagged "Proposed" and will be reviewed by the team.
Q: Will you accept a pull request?
A: We haven't worked out how pull requests should work for a public roadmap page, but we will take all PRs very seriously and review for inclusion. Read about contributing.
License
This library is licensed under the Creative Commons Attribution-ShareAlike 4.0 International License.
To learn more about the services, head here: http://aws.amazon.com/containers
Read the full README on GitHubWhat Hacker News says
35 sourcesIIRC it's not in the spec because administration of resources is out of scope. For example, perhaps you offer a public repository and you want folks to sign up for an account before they can push? Or you want to have an approval process before new repositories are created?
Regardless it's a huge pain that ECR doesn't support this. Everybody I know of who has used ECR has run into this.
There's a long standing issue open which I've been subscribed to for years now: https://github.com/aws/containers-roadmap/issues/853
In Using S3 as a Container RegistryThanks for showing up and answering questions. Congratulations on the release.
What kind of plans for support of Rust's evolving async ecosystem?
Any particular reason why the public roadmap does not show the columns similar to "Researching", "We're Working On It" like the other similar public AWS Roadmaps? See example for Containers: https://github.com/aws/containers-roadmap/projects/1
Would be nice to have fully working examples on Github, for most common scenarios across most AWS services. This is something that historically
AWS SDKs have been inconsistent on. Just a request not really a question :-)
In General Availability of the AWS SDK for RustDeploying Fargate with CDK has to have been the most pleasant developer experience I have ever had with any product so far.
If image caching becomes a reality with Fargate I can't imagine a need to ever use anything else
https://github.com/aws/containers-roadmap/issues/696
In Kubernetes SidecarContainers feature is mergedI'm waiting for Podman to hit AWS ECR/ECS. Until then it's just an interesting topic.
https://github.com/aws/containers-roadmap/issues/626
In Podman Desktop 1.0Until podman could be used with AWS ECR/ECS it's pretty much moot in my case: https://github.com/aws/containers-roadmap/issues/626
In How to use Podman inside of a container (2021)In late 2021 we had EKS nodes shit the bed for no apparent reason. Max out CPU and couldn't SSH in. They'd get recreated eventually by EC2 (multiple hours) despite being tainted in k8s pretty quickly. We ran with N+2 nodes to deal with it.
After dutifully updating EKS releases and AMIs it seems to have fixed itself last year.
EKS seems to be fine generally, but it would be nice if they didn't release new AMIs with missing commits?? [1] and especially [2]
[1] https://github.com/aws/containers-roadmap/issues/319
[2] https://github.com/awslabs/amazon-eks-ami/issues/278#issueco...
In Comparing K3s with vanilla KubernetesThis is really cool. Upon further Googling, readers may be interested in https://kubernetes.io/blog/2017/12/using-ebpf-in-kubernetes/
If you can go beyond Kubernetes, I think that'd give Odigos more staying power.
Naturally some integrations are out of your hands, AWS Fargate being one (https://github.com/aws/containers-roadmap/issues/1027). However, if you could get integrations up and running with the likes of Fargate, Fly.io, Render.com etc. That'd be amazing.
In Launch HN: Odigos (YC W23) – Instant distributed tracing for Kubernetes clustersThis is still a thing, Fargate pull times are super slow: https://github.com/aws/containers-roadmap/issues/696. We run all of our workloads on fargate, and it's really annoying when you're trying to iterate on something and you have to sit there waiting on "Provisioning..." for 1-2 minutes every time you launch a task. I don't think the control plane is that slow, as EC2 based ECS launches tasks really fast if the images are already cached on the machine.
In We clone a running VM in 2 secondsUsing Fargate for on-demand provisioning remains slow for us (> 60sec).
Without Docker image caching support (1) and working within a VPC (2), it easily takes 2+ minutes.
(1) https://github.com/aws/containers-roadmap/issues/696
(2) https://stackoverflow.com/a/67398011
In Benchmarking Container Scaling on AWS> It’s sometimes said this Alpine stuff is a premature optimization, but in most cases it’s not even an optimization.
I do use Debian Slim over Alpine without thinking but image size does matter in a lot of cases once you leave your dev box or start to use Kubernetes.
For example if you're using AWS Fargate images aren't cached[0]. That means every time you deploy your app a new pod is going to get created and it has to wait for your image to download.
Fargate already has a 30-40ish second spin up time inherit to the platform. Having to wait X seconds or even minutes more to download your app's image delays things quite a lot, especially if you have something like a pre-sync hook running to do something like running a database migration. Now every deploy pays this penalty twice.
[0]: https://github.com/aws/containers-roadmap/issues/696
In Anti-patterns when building container imagesThe big issue with ECS+Fargate is the lack of CPU bursting capability. This means that if you want to run a small service that doesn't consume much, you have two options:
1. Use a 0.25cpu + 0.5gb ram configuration and accept that your responses are now 4 times slower because the 25% time is strictly enforced.
2. Use a 1cpu + 2gb ram (costing 4 times more) even though it is very under-utilized.
AWS is definitely in no rush to fix this, as they keep saying they are aware of the issue and "thinking about it". No commitment or solution on sight though:
https://github.com/aws/containers-roadmap/issues/163
In AWS Lambda Cold Start TimesFUSE is not support by AWS Lambda, so we can't mount JuiceFS in Lambda.
We can have a SDK to access JuiceFS from Lambda, similar to S3 SDK, when you need to use JuiceFS outside of Lambda.
Same to Fargate, we can not mount JuiceFS in Farget because of lacking FUSE permission, people are asking for it[1].
https://github.com/aws/containers-roadmap/issues/412
In A distributed Posix file system built on top of Redis and S3It depends on the AWS product.
For the container systems e.g. ECS, EKS, Fargate they have an open roadmap where they drive much of the direction from the community:
https://github.com/aws/containers-roadmap
For others it's completely closed off. At my last company we spent tens of millions a year with AWS and they never listened to us. The account managers have zero pull.
In Amazon RDS on Graviton2 ProcessorsShowing the 15 most recent of 35 sources. Enable JavaScript to search and browse every indexed mention.