AWS IoT Rules Engine Now Supports Calling Lambda Function from Rule SQL
You can now call a lambda function in the SQL statement of your rule by calling it in the SELECT statement to enrich IoT message data with external services like weather, geo-location, and maps. You can also call a lambda function from the WHERE clause to evaluate a condition with context from external services. For example, you can evaluate if the reported device position lies inside or outside a geographic area by calling an external geo-fencing endpoint like HERE maps (sample) and then triggering an SNS Action if it lies outside the area.
You can now call a lambda function in the SQL statement of your rule by calling it in the SELECT statement to enrich IoT message data with external services like weather, geo-location, and maps. You can also call a lambda function from the WHERE clause to evaluate a condition with context from external services. For example, you can evaluate if the reported device position lies inside or outside a geographic area by calling an external geo-fencing endpoint like HERE maps (sample) and then triggering an SNS Action if it lies outside the area.
AWS IoT is a managed cloud service that lets connected devices easily and securely interact with cloud applications and other devices. IoT Rules Engine, a component of AWS IoT, evaluates inbound messages published into AWS IoT and transforms and delivers them to another device or a cloud service, based on business rules you define. A rule can apply to data from one or many devices, can take one or many actions in parallel, and route messages to AWS endpoints including AWS Lambda, Amazon Kinesis, Amazon S3, Amazon Machine Learning, Amazon DynamoDB, Amazon CloudWatch, and Amazon Elasticsearch Service with built-in Kibana integration. External endpoints can be reached using AWS Lambda, Amazon Kinesis, and Amazon Simple Notification Service (SNS).
To learn more about Amazon Rules Engine and to get started request, visit the product pages.