#DeveloperGuide
Amazon ECS Managed Daemons now support non-critical daemons

https://docs.aws.amazon.com/AmazonECS/latest/developerguide/Welcome.html (Amazon ECS) now support non-critical Managed Daemons for https://aws.amazon.com/ecs/managed-instances/. You can configure a daemon as...

#AWS #AmazonEcs #AwsFargate
Amazon ECS Managed Daemons now support non-critical daemons
https://docs.aws.amazon.com/AmazonECS/latest/developerguide/Welcome.html (Amazon ECS) now support non-critical Managed Daemons for https://aws.amazon.com/ecs/managed-instances/. You can configure a daemon as non-critical so that your mission-critical application tasks continue running uninterrupted, even when a daemon fails, stops, or becomes unhealthy. Amazon ECS Managed Daemons lets you centrally deploy and manage software agents independently of application deployments to ensure consistent coverage and compliance across your container infrastructure. For some mission-critical applications, uninterrupted execution of application tasks may matter more than auxiliary daemon functionality like logging or metrics collection. With this launch, you can now configure a managed daemon as non-critical so that its failure does not cause your application tasks to churn. When a non-critical daemon task fails, stops, or becomes unhealthy, the container instance remains active, your existing application tasks continue running uninterrupted, ECS continues placing new application tasks on it, and instance registration is never blocked, so your tasks launch immediately even when the daemon fails to start. Amazon ECS emits an EventBridge event when a daemon task fails to start and records service action logs for both critical and non-critical daemons, giving you full observability into daemon health. To get started, you can use AWS Console, CLI, CloudFormation, or AWS SDKs to create a non-critical daemon by setting the critical parameter to false when creating or updating a daemon. Non-critical daemons are available in all AWS Regions where Amazon ECS Managed Daemons are supported. To learn more, refer to our https://docs.aws.amazon.com/AmazonECS/latest/developerguide/managed-daemons.html#managed-daemons-criticality page.
aws.amazon.com
September 4, 2026 at 12:05 AM
AWS IoT Core now supports native InfluxDB routing for time-series data

https://aws.amazon.com/iot-core/ now supports https://docs.aws.amazon.com/iot/latest/developerguide/influxdb-rule-action.html that routes time-series data from your Internet of Thin...

#AWS #AwsIotCore #AmazonTimestream #AwsIot
AWS IoT Core now supports native InfluxDB routing for time-series data
https://aws.amazon.com/iot-core/ now supports https://docs.aws.amazon.com/iot/latest/developerguide/influxdb-rule-action.html that routes time-series data from your Internet of Things (IoT) devices directly to https://www.influxdata.com/products/timestream-for-influxdb/ databases, without writing custom device-side code or using intermediate cloud services. AWS IoT Core is a fully managed service that securely connects billions of IoT devices to the AWS cloud, and routes IoT device data to AWS and third-party services. The new InfluxDB rule action automatically converts time-series data from your device to InfluxDB’s line protocol format and writes it to either an https://docs.aws.amazon.com/timestream/latest/developerguide/influxdb3.html managed or a self-hosted InfluxDB cluster. The new rule action also supports the following two batching modes to help you optimize cost and throughput: device-side batching, where your devices send pre-batched payloads to AWS IoT Core; and server-side batching, where IoT rules engine aggregates individual messages before writing to InfluxDB. For example, a life sciences company can batch thousands of telemetry readings from scientific instruments at millisecond granularity and write directly to InfluxDB for monitoring, without building a custom data pipeline. To get started, connect your IoT devices to AWS IoT Core and define an InfluxDB rule action specifying the destination database, along with authentication and batching parameters. The InfluxDB rule action is available in all AWS Global Regions where Amazon Timestream for InfluxDB is available. To learn more, visit the AWS IoT Core https://docs.aws.amazon.com/iot/latest/developerguide/influxdb-rule-action.html.
aws.amazon.com
August 25, 2026 at 10:05 PM
MSK Replicator now supports OAuth 2.0 (SASL/OAUTHBEARER) authentication for replication from external Apache Kafka clusters to Amazon MSK

Amazon MSK Replicator now supports OAuth 2.0 (SASL/OAUTHBEARER) authentication for data replication from external Apache Kafka clusters - inc...

#AWS #AmazonMsk
MSK Replicator now supports OAuth 2.0 (SASL/OAUTHBEARER) authentication for replication from external Apache Kafka clusters to Amazon MSK
Amazon MSK Replicator now supports OAuth 2.0 (SASL/OAUTHBEARER) authentication for data replication from external Apache Kafka clusters - including on-premises, self-managed on AWS, or other cloud providers - to https://docs.aws.amazon.com/msk/latest/developerguide/msk-provisioned.html. With this capability, external Apache Kafka clusters configured with OAuth/OIDC authentication can now use MSK Replicator to migrate workloads to Amazon MSK, support disaster recovery by using MSK-based clusters as a failover or backup target and enable data distribution across hybrid and multi-cloud environments. MSK Replicator is a feature of Amazon MSK that automates data replication between Kafka clusters, eliminating the need to manage custom replication infrastructure or configure open-source tools. Previously, MSK Replicator supported SASL/SCRAM and mTLS authentication for connecting to external Apache Kafka clusters. With this launch, you can now also use OAuth 2.0 authentication with MSK Replicator to replicate data from external Kafka clusters to Amazon MSK. Unlike self-managed replication tools, MSK Replicator lets you retain your original Kafka topic names during replication while automatically avoiding infinite replication loops. It also synchronizes consumer group offsets bidirectionally, enabling you to move producers and consumers across clusters independently, in any order, without coordination constraints or the risk of data loss. This new capability is supported in all AWS Regions where MSK Replicator is available. Visit the MSK Replicator https://docs.aws.amazon.com/msk/latest/developerguide/msk-replicator.html, https://aws.amazon.com/msk/features/msk-replicator/, https://aws.amazon.com/msk/pricing/, and this https://aws.amazon.com/blogs/big-data/migrate-third-party-and-self-managed-apache-kafka-clusters-to-amazon-msk-express-brokers-with-amazon-msk-replicator/ to learn more.
aws.amazon.com
August 25, 2026 at 6:05 PM
Amazon ECS now automatically detects and repairs container instances with impaired agent connectivity

https://docs.aws.amazon.com/AmazonECS/latest/developerguide/Welcome.html (Amazon ECS) now automatically detects and repairs container instances, enabling customers to reduce und...

#AWS #AmazonEcs
Amazon ECS now automatically detects and repairs container instances with impaired agent connectivity
https://docs.aws.amazon.com/AmazonECS/latest/developerguide/Welcome.html (Amazon ECS) now automatically detects and repairs container instances, enabling customers to reduce undetected workload failures and improve application availability without manual intervention. With this launch, Amazon ECS continuously monitors agent connectivity across container instances. Infrastructure events such as EBS volume degradation, host thermal events, or network connectivity failures can sever the ECS agent's connection to the ECS control plane. Amazon ECS now surfaces a new type of container instance health change event (AGENT_CONNECTIVITY) for all compute options: AWS Fargate, Amazon ECS Managed Instances, and Amazon ECS on EC2. For ECS Managed Instances and AWS Fargate, ECS automatically performs recovery - automatically draining running tasks and launching replacement capacity while deregistering impaired instances. Customers running workloads on Amazon ECS on EC2, can use this health change event to drive instance replacement workflows. This capability is available at no additional cost in all AWS Commercial and AWS GovCloud (US) https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/. To learn more, see https://docs.aws.amazon.com/AmazonECS/latest/developerguide/container-instance-health.html.
aws.amazon.com
August 25, 2026 at 12:05 AM
August 24, 2026 at 3:52 AM
August 24, 2026 at 1:52 AM