Update ECS agent version
See original GitHub issueWe should update our Cluster class to use the latest ECS agent AMI.
http://docs.aws.amazon.com/AmazonECS/latest/developerguide/container_agent_versions.html
We should also decide on our policy here - we have two choices:
- Have the framework automatically pick the latest
- Plan to manually update the agent version sometime after AWS releases and after we’ve been able to do our own validation
Separately, we could decide whether we want to allow overriding the agent version via config so that taking a new framework version doesn’t force rebuilding the cluster VMs.
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Updating the Amazon ECS container agent
To update the Amazon ECS agent version from versions before v1.0.0 on your Amazon ECS-optimized AMI, we recommend that you terminate your current...
Read more >Manually updating the Amazon ECS container agent (for non ...
Agent updates do not apply to Windows container instances. We recommend that you launch new container instances to update the agent version in...
Read more >Releases · aws/amazon-ecs-agent - GitHub
1.65.0 · Feature - ECS Agent changes to support task scale in protection feature. · Enhancement - Update service connect config validator to...
Read more >Check for ECS Container Instance Agent Version - Trend Micro
06 On the selected container instance page, select the Details tab, and check the Agent version attribute value to determine the ECS container ......
Read more >Updates the Amazon ECS container agent on a specified... - R
Updating the Amazon ECS container agent does not interrupt running tasks or services on the ... version = 123, versionInfo = list( agentVersion...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

I think it will be critical that we are precise in how we reason about versioning for this library and the distinction that it is itself not a SaaS/PaaS but is a component which is adopted in a versioned way in SaaS apps is really consequential (and in fact, creates many more constraints on our solution than if this was only actually deployed as a SaaS and consumed through a single “head” version all the time).
i’m sort of with you on the library distinction … a little less so on policy, esp. depending on how we dogfood. you can have the last word, however, i think the slope is a little more slippery. i know we think we’ve drawn the line at fabric, not framework, however, i think over time, we’ll have P apps critical to running P.
On Tue, Nov 7, 2017 at 3:12 PM, Luke Hoban notifications@github.com wrote: