Right this moment, we’re saying managed daemon assist for Amazon Elastic Container Service (Amazon ECS) Managed Situations. This new functionality extends the managed situations expertise we launched in September 2025, by giving platform engineers unbiased management over software program brokers corresponding to monitoring, logging, and tracing instruments, with out requiring coordination with utility improvement groups, whereas additionally bettering reliability by guaranteeing each occasion constantly runs required daemons and enabling complete host-level monitoring.
When operating containerized workloads at scale, platform engineers handle a variety of obligations, from scaling and patching infrastructure to protecting functions operating reliably and sustaining the operational brokers that assist these functions. Till now, many of those considerations have been tightly coupled. Updating a monitoring agent meant coordinating with utility groups, modifying activity definitions, and redeploying total functions, a big operational burden if you’re managing tons of or 1000’s of companies.
Decoupled lifecycle administration for daemons
Amazon ECS now introduces a devoted managed daemons assemble that permits platform groups to centrally handle operational tooling. This separation of considerations permits platform engineers to independently deploy and replace monitoring, logging, and tracing brokers to infrastructure, whereas imposing constant use of required instruments throughout all situations, with out requiring utility groups to redeploy their companies. Daemons are assured to begin earlier than utility duties and drain final, guaranteeing that logging, tracing, and monitoring are all the time obtainable when your utility wants them.
Platform engineers can deploy managed daemons throughout a number of capability suppliers, or goal particular capability suppliers, giving them flexibility in how they roll out brokers throughout their infrastructure. Useful resource administration can be centralized, permitting groups to outline daemon CPU and reminiscence parameters individually from utility configurations without having to rebuild AMIs or replace activity definitions, whereas optimizing useful resource utilization since every occasion runs precisely one daemon copy shared throughout a number of utility duties.
Let’s attempt it out
To take ECS Managed Daemons for a spin, I made a decision to begin with the Amazon CloudWatch Agent as my first managed daemon. I had beforehand arrange an Amazon ECS cluster with a Managed Occasion capability supplier utilizing the documentation.
From the Amazon Elastic Container Service console, I seen a brand new Daemon activity definitions possibility within the navigation pane, the place I can outline my managed daemons.

I selected Create new daemon activity definition to get began. For this instance, I configured the CloudWatch Agent with 1 vCPU and 0.5 GB of reminiscence. Within the Daemon activity definition household area, I entered a reputation I’d acknowledge later.
For the Job execution position, I chosen ecsTaskExecutionRole from the dropdown. Below the Container part, I gave my container a descriptive identify and pasted within the picture URI: public.ecr.aws/cloudwatch-agent/cloudwatch-agent:newest together with a couple of further particulars.
After reviewing all the things, I selected Create.
As soon as my daemon activity definition was created, I navigated to the Clusters web page, chosen my beforehand created cluster and located the brand new Daemons tab.

Right here I can merely click on the Create daemon button and full the shape to configure my daemon.

Below Daemon configuration, I chosen my newly created daemon activity definition household after which assigned my daemon a reputation. For Surroundings configuration, I chosen the ECS Managed Situations capability supplier I had arrange earlier. After confirming my settings, I selected Create.
Now ECS mechanically ensures the daemon activity launches first on each provisioned ECS managed occasion in my chosen capability supplier. To see this in motion, I deployed a pattern nginx internet service as a check workload. As soon as my workload was deployed, I might see within the console that ECS Managed Daemons had mechanically deployed the CloudWatch Agent daemon alongside my utility, with no handbook intervention required.
After I later up to date my daemon, ECS dealt with the rolling deployment mechanically by provisioning new situations with the up to date daemon, beginning the daemon first, then migrating utility duties to the brand new situations earlier than terminating the outdated ones. This “begin earlier than cease” strategy ensures steady daemon protection: your logging, monitoring, and tracing brokers stay operational all through the replace with no gaps in information assortment. The drain proportion I configured managed the tempo of this substitute, giving me full management over addon updates with none utility downtime.
The way it works
The managed daemon expertise introduces a brand new daemon activity definition that’s separate from activity definitions, with its personal parameters and validation scheme. A brand new daemon_bridge community mode allows daemons to speak with utility duties whereas remaining remoted from utility networking configurations.
Managed daemons assist superior host-level entry capabilities which are important for operational tooling. Platform engineers can configure daemon duties as privileged containers, add further Linux capabilities, and mount paths from the underlying host filesystem. These capabilities are notably worthwhile for monitoring and safety brokers that require deep visibility into host-level metrics, processes, and system calls.
When a daemon is deployed, ECS launches precisely one daemon course of per container occasion earlier than putting utility duties. This ensures that operational tooling is in place earlier than your utility begins receiving visitors. ECS additionally helps rolling deployments with automated rollbacks, so you may replace brokers with confidence.
Now obtainable
Managed daemon assist for Amazon ECS Managed Situations is accessible as we speak in all AWS Areas. To get began, go to the Amazon ECS console or evaluate the Amazon ECS documentation. You may as well discover the brand new managed daemons Utility Programming Interface (APIs) by visiting this web site.
There isn’t any further price to make use of managed daemons. You pay just for the usual compute assets consumed by your daemon duties.

