AWS IoT Core’s Rules Engine now supports batching of device logs while routing logs from IoT devices to Amazon CloudWatch Logs

AWS IoT Core announces General Availability of the capability to send device logs from Internet of Things (IoT) devices to Amazon CloudWatch Logs in batches, enabling you to optimize the cost of using CloudWatch Log Action in IoT Rules.

AWS IoT Core is a fully managed service that you can use to connect billions of IoT devices to AWS cloud without provisioning and managing cloud infrastructure. Rules Engine is a feature of AWS IoT Core through which you can filter, decode, and process IoT device data, and route that data to 20 AWS services (including CloudWatch Logs) and to any number of customer-defined HTTP APIs.

To get started, use the AWS IoT Core console, Command Line Interface (CLI) or SDKs to connect your IoT devices to AWS IoT Core, define IoT Rules to process and filter the device data, and create a CloudWatch Log Action to route the device logs to CloudWatch Logs. Additionally, you must batch device logs in your IoT device before routing the logs to AWS IoT Core. If your IoT device logs are batched, you can select the batching option in AWS IoT Core console, CLI or SDKs to deliver those batches to CloudWatch Logs.

Batching of CloudWatch Logs Actions is available in all AWS Regions including AWS GovCloud (US) Regions where AWS IoT Core is available. These Regions are US East (N. Virginia), US East (Ohio), US West (N. California), US West (Oregon), Asia Pacific (Hong Kong), Asia Pacific (Mumbai), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Canada (Central), Europe (Frankfurt), Europe (Ireland), Europe (London), Europe (Paris), Europe (Stockholm), Middle East (Bahrain), Middle East (UAE), South America (Sao Paulo), and AWS GovCloud (US-East) and AWS GovCloud (US-West). For more information, For more information, see Upload device-side logs to Amazon CloudWatch in the AWS IoT Developer Guide.