Amazon ECS Managed Daemons now support non-critical daemons
Amazon ECS now allows configuration of non-critical managed daemons on ECS managed instances, ensuring mission-critical application tasks continue uninterrupted even when daemons fail, stop, or become unhealthy.
Amazon Elastic Container Service (Amazon ECS) now supports non-critical managed daemons on ECS managed instances. Configuring daemons as non-critical ensures mission-critical application tasks continue running uninterrupted, even if the daemon fails, stops, or becomes unhealthy. If a non-critical daemon task fails, stops, or becomes unhealthy, the container instance remains active, existing application tasks keep running without interruption, and ECS continues placing new application tasks without blocking instance registration. This means tasks start immediately, whether the daemon starts or fails. Amazon ECS issues an EventBridge event when a daemon task fails to start and records service action logs for both critical and non-critical daemons, providing full visibility into daemon health. To get started, create or update a daemon with the critical parameter set to false using the AWS console, CLI, CloudFormation, or AWS SDK. Non-critical daemons are available in all AWS regions where Amazon ECS managed daemons are supported. For more information, see the documentation page.
Why it matters
This update affects users running mission-critical container applications. By ensuring that daemon failures do not impact application tasks, it improves system stability and reliability.