AWS IoT Events actions now support AWS Lambda, SQS, Kinesis Firehose, and IoT Events as targets
Share
Services
When using [AWS IoT Events](/iot-events/), you now have the option to define actions to invoke AWS Lambda functions, publish messages to the Amazon Simple Queue Service (SQS) queue or an Amazon Kinesis Data Firehose delivery stream, and republish messages to IoT Events. Previously, you could only define actions to publish messages to SNS and MQTT. These expanded actions make it easier to build monitoring applications that help you quickly understand the state of your devices by providing more options to process messages created by IoT Events.
You can define a Lambda action to invoke a specific Lambda function with the message payload. The Lambda function receives the message payload as an input parameter and can further process the information in the message. Similarly, you can define an SQS action to send the message payload to a SQS queue that other services could read from. You can send the message payload to a Firehose delivery stream to display alerts in applications such as real-time dashboards. Finally, by defining IoT Events as an action, you send the message payload as an input to another detector model which can help simplify complex detector models into a hierarchy of simple ones.
These new actions are available in [all regions where AWS IoT Events](/about-aws/global-infrastructure/regional-product-services/) is available. To get started, open the [IoT Events console](https://console.aws.amazon.com/iotevents) and select a state for a detector model. Add an event to the state, and select from the [list of available actions](https://docs.aws.amazon.com/iotevents/latest/developerguide/iotevents-with-others.html).
What else is happening at Amazon Web Services?
Amazon AppStream 2.0 users can now save their user preferences between streaming sessions
December 13th, 2024
Services
Share
AWS Elemental MediaConnect Gateway now supports source-specific multicast
December 13th, 2024
Services
Share
Amazon EC2 instances support bandwidth configurations for VPC and EBS
December 13th, 2024
Services
Share
AWS announces new AWS Direct Connect location in Osaka, Japan
December 13th, 2024
Services
Share
Amazon DynamoDB announces support for FIPS 140-3 interface VPC and Streams endpoints
December 13th, 2024
Services
Share