G2

Atharva P.

Cloud BI Engineer

Enterprise (> 1000 emp.)

7/30/2026

"AWS IoT Events Simplified Stateful IoT Alerting at Scale"

4/5

What do you like best about AWS IoT Events?

We previously used AWS IoT Events for stateful event detection and alerting. Since AWS has announced the end of support for the service, we’ve migrated to event-driven architectures built on AWS IoT Core, Amazon EventBridge, AWS Lambda, Amazon CloudWatch Alarms, and Amazon Managed Service for Apache Flink, depending on the workload.

AWS IoT Events made it easy to detect stateful conditions from streaming IoT telemetry. With Detector Models, Inputs, Alarms, and Actions, we could build fairly complex event-processing workflows without having to write a custom event engine.

The service also scaled well for high-volume telemetry and integrated naturally with SNS, Lambda, and IoT Core, which made it especially useful for industrial monitoring and predictive alerting. Review collected by and hosted on G2.com.

What do you dislike about AWS IoT Events?

The service required learning its detector model concepts, and debugging complex state transitions could be challenging. Since AWS announced its retirement, long-term investment in the platform was no longer practical. Review collected by and hosted on G2.com.

What problems is AWS IoT Events solving and how is that benefiting you?

IoT Events detected equipment failures before they became production incidents.

Example: Temperature, vibration, and pressure readings streamed from manufacturing equipment into IoT Core. Detector Models identified abnormal operating patterns over time instead of reacting to single sensor readings. When thresholds persisted, the service triggered Lambda functions and SNS notifications for maintenance teams, reducing equipment downtime. Review collected by and hosted on G2.com.