amazon-ecs-agent

Amazon Elastic Container Service Agent

Systems & Infrastructure DevOps & Cloud

Explore on GitHub Read Hacker News discussions

9Distinct people

10Mentions

0Explicit recommenders

2.2KGitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

Amazon Elastic Container Service Agent

GitHub

Where it is used

No documented product use has been verified yet.

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, 8:59:20 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 year10 dated mentions

Observed mentions: 2014-12-12 21:37:17 UTC to 2020-03-19 16:11:58 UTC.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges

UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Submissions	Comments
2014	2014-01-01 00:00:00 UTC	2015-01-01 00:00:00 UTC	1	1	0
2015	2015-01-01 00:00:00 UTC	2016-01-01 00:00:00 UTC	3	0	3
2016	2016-01-01 00:00:00 UTC	2017-01-01 00:00:00 UTC	3	0	3
2017	2017-01-01 00:00:00 UTC	2018-01-01 00:00:00 UTC	2	0	2
2018	2018-01-01 00:00:00 UTC	2019-01-01 00:00:00 UTC	0	0	0
2019	2019-01-01 00:00:00 UTC	2020-01-01 00:00:00 UTC	0	0	0
2020	2020-01-01 00:00:00 UTC	2021-01-01 00:00:00 UTC	1	0	1

What Hacker News says

2 sources

clarkdave·Sep 3, 2017

Some container engines don't support the --init flag, such as Amazon ECS[0], so there is still a place for dumb-init and tini for the time being. [0] https://github.com/aws/amazon-ecs-agent/issues/852

In Perl as PID 1 under Docker

NathanKP·Feb 23, 2017

(AWS employee here) First of all I can assure you that Amazon is 100% committed to containers. Amazon's compute strategy is aimed at three levels of abstraction: instances, containers, lambda. All three are equally important to Amazon. With regard to ECS feature set relative to K8, the thing to understand is that AWS follows a startup-like strategy of launching an MVP and then letting customer feedback drive roadmap from there. AWS is definitely not half hearted about ECS. Rather AWS is constantly working with customers to define a roadmap for further development on ECS. To me the most exciting thing about ECS is the open source work being done around ECS, for Blox (a framework for building out custom container scheduling logic), and the ECS agent itself: https://github.com/blox/blox https://github.com/aws/amazon-ecs-agent With these ECS

Read the rest

components you can open issues or even PR's just like any other open source project. Additionally another cool thing we are doing is sharing feature proposals for public comment. You can check out an Amazon employee's public fork of the ECS agent to see a preview of coming roadmap, and we are actively soliciting feedback on proposals such as this one: https://github.com/aaithal/amazon-ecs-agent/blob/f4d80440db0... If you have any questions about ECS, feedback, or concerns feel free to reach out to me directly (peckn@amazon.com) and I'd be happy to chat!

In Docker in Production: An Update