On canary deployments, if you can wait a bit to make a decision, CodeDeploy should have canary deployments available soon-ish: https://github.com/aws/containers-roadmap/issues/229
In The Service Mesh: What Engineers Need to Knowaws
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 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 12:45:45 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
8 sourcesCan I easily SSH into or otherwise interactively get a shell into a Fargate container? I think this is a minimum debuggability requirment for these kinds of services.
https://github.com/aws/containers-roadmap/issues/187 sounds like the answer is "no"?
In AWS Fargate Deep DiveEKS has its own share of problems, and in several cases they can't be mitigated due to the limitations that EKS imposes. For example:
- Service cluster IP range is not definable, making it difficult to integrate with an existing network topology [1]
- Limited choice of CNIs, e.g. Calico can not be used
- No accessible etcd snapshots for recovery
I tend to avoid EKS and prefer to create most clusters by using kubeadm as the foundation.
[1] https://github.com/aws/containers-roadmap/issues/216
In How Far Out Is AWS Fargate?Sweet. Now add support for multiple ports on a single service[1] and this load balancer might actually become useful.
[1]: https://github.com/aws/containers-roadmap/issues/104
In New AWS UDP Load Balancing for Network Load BalancerPrinicples from AWS Container Services Organization
3 points · Open discussionApart from pricing and the potential to overcommit resources on EC2-ECS, there are a couple of other differences.
One is your options for doing forensics on Fargate. AWS manage the underlying host so you give up the option of Doing host level investigations. It’s not necessarily worse as you can fill this gap in other ways.
Logging is currently only via CloudWatch logs so if you want to get logs into something like Splunk you’ll have to run something that can pick up these logs. You’ll have that issue to solve if you want logs from some other AWS services like Lambda to go to the same place. The bigger issue for us is that you can’t add additional metadata to log events without building that into your application or getting tricky with log group names. On EC2 we’ve been using fluentd to add additional context to each log event like the i
Read the rest
nstance it came from, the AZ, etc. Support for additional log drivers on Fargate is on the public roadmap[1][2] so there will hopefully be some more options soon.
[1] Fargate Log driver support v1 https://github.com/aws/containers-roadmap/issues/9
[2] Fargate log driver support v2 https://github.com/aws/containers-roadmap/issues/10
AWS employee here. I don't think there is anything fundamental that makes Kubernetes avoid autoscaling issues. Just like with ECS if you don't setup the right horizontal pod autoscaling settings in Kubernetes you can easily end up with under or over scheduling of your Kubernetes pods. Ultimately no matter whether you use ECS or EKS you will need to do some finetuning and testing to make sure your autoscaling setup matches with your real world traffic patterns.
AWS is committed to improving both ECS and EKS. You can see our public roadmap with many in progress improvements for both container orchestration platforms here: https://github.com/aws/containers-roadmap/projects/1
Feel free to add your own additional suggestions, or vote on existing items to help us prioritize what we should work on faster!
In When AWS Autoscale Doesn’tAWS employee here.
This is a feature that is currently on our public roadmap for container services, in the "Researching" category: https://github.com/aws/containers-roadmap/issues/76
Feel free to drop a thumbs up on the roadmap item to show your support and boost its priority on the roadmap, or leave a comment to let us know more about your needs.
In When AWS Autoscale Doesn’t