aws / aws/containers-roadmap

[ECS] [Bottlerocket]: Smarter Agent Version detection on ECS

Open
#1,088 0 comments 2 reactions 0 assignees View on GitHub
ECS Proposed
Dominant language
Shell
Stars
5.4k
Forks
334
PR merge metrics
No merged PRs in 30d

Description

### Community Note

* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment

**Tell us about your request**
What do you want us to build?

Currently there is no way of updating Bottlerocket's ECS Agent, we need to wait for the Bottlerocket team to release a new version in order to get a newer version of the ECS Agent.

This is causing the Bottlerocket based instances to be marked as

` This container instance is not running the latest version of the Amazon ECS container agent.`

This may cause some systems to be in an non-complainant status depending on company policies.

I am suggesting a smarter way in which the agent is flagged as not in the latest version or in the latest version depending on the update possibilities of the underlying OS.

**Which service(s) is this request for?**
Fargate, ECS

**Are you currently working around this issue?**
There is currently no workaround for this.

**Additional context**

Example:

Bottlerocket version `1.0.1` is currently running `1.43.0` and latest ECS Agent version is `1.44.4`

**Attachments**
If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look. (Remember to remove any personally-identifiable information.)

Contributor guide

Open the contributing guide

Research direction

Start by reviewing how ECS determines whether an agent is current and how Bottlerocket version 1.0.1 reports its ECS Agent version 1.43.0 against the latest 1.44.4. Confirm the update possibilities of the underlying OS and define the version-status behavior so Bottlerocket instances are not marked noncompliant solely because their agent cannot be updated independently.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
cloud
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.