Amazon ECS Managed Daemons now support inter-task visibility and communication

Amazon Web Services has enhanced its Elastic Container Service (ECS) Managed Daemons with new inter-task visibility and communication capabilities. The update introduces two configuration options in daemon task definitions: pidMode, which allows daemons to access all processes running on an instance, and ipcMode, which enables daemons to share Inter-Process Communication (IPC) namespaces with other containers. When set to "shared," these modes grant daemons broader system access, while the default "none" setting maintains isolation between daemon and application containers. The enhancement addresses a specific operational challenge for platform teams deploying monitoring and security infrastructure. Previously, organizations had to embed tracing, profiling, and security agents as sidecars within individual application task definitions. Now, these agents can run as standalone ECS daemons with guaranteed single-instance deployment per managed instance and startup prioritization before application tasks launch. This architectural change allows platform teams to manage agent deployments and updates independently from application workloads while ensuring consistent coverage across all running services. The feature is immediately available across all AWS regions at no additional cost and can be configured through the AWS Console, CLI, CloudFormation, or AWS SDKs. Organizations using ECS Managed Instances capacity providers can implement the new daemon configurations by updating their task definitions and daemon services.