Integrations/AWS IoT Core suite
shippedCloud data pipeline

AWS IoT Core suite

A device-to-dashboard AWS pipeline running in production for a smart gas-metering fleet since December 2022.

What it is

Device telemetry enters AWS IoT Core Topics, where the Rules Engine routes it to IoT Analytics, S3, and Athena. QuickSight serves the BI team while IoT Events and SNS carry operational alarms. This chain has run in production for a smart gas-metering fleet since December 2022.

MQTT over TLSRules Engine routingS3 + Athena data lakeQuickSight BIIoT Events + SNSlive since Dec 2022
AWS IoT Core suite
How it works

The data path, including the hand-offs that usually cause trouble.

01

Connect & authenticate

Devices publish MQTT to IoT Core Topics with renewable credentials provisioned by InfiIoT. Unknown devices do not enter trusted streams.

02

Route

The Rules Engine filters and routes every message: a hot path to the InfiIoT twin core for live dashboards, a cold path to S3 and IoT Analytics for history.

03

Analyze

Athena queries the data lake and QuickSight serves the BI team, while InfiIoT dashboards stay real-time for operators.

04

Act

IoT Events detects state changes and sends them through SNS and InfiIoT's alert channels. The same path supports billing events, valve control, and operational alarms.

Top use cases

Where teams use this integration.

For the utility COO

Prepaid billing without meter readers

Gas meters bill through the cloud pipeline, and non-payment can trigger remote valve control. The process does not add another field visit.

For the head of analytics

Place telemetry in the existing data lake

Telemetry lands in S3 and Athena beside existing data, and the BI team continues to use QuickSight.

For the CIO

IoT on the cloud contract you already have

The pipeline runs in your AWS account and regions under your IAM policies. Procurement and security teams can reuse agreements already in place.

Want this wired into your stack?

Bring the source system, target system, and security constraints. An engineer will map the interface and the unresolved questions.

Connected-product assessment

Bring one product. Leave with a clear next step.

Use 30 minutes to test the fit around one product and one blocked decision. If there is a fit, we will outline the two-week Product Blueprint.

30-minute fit callOne productNo prepared deck