Not something I use today, but the numbers make it the cheapest AWS ingestion path for MQTT devices.
Use it when
- Devices can use MQTT and X.509 identities.
Don't use it when
- Devices only speak HTTP. Use an HTTP API → SQS → batched Lambda.
Pricing
In my IoT example (5,000 devices, one message a minute), IoT Core → SQS → batched Lambda → Postgres ≈ $215–230 a month vs about $1,014–1,109 for API Gateway REST → SNS → Lambda.
Provisioning
Official Pulumi package · Official Terraform provider
Instead, consider
- API Gateway HTTP-only devices (HTTP API, not REST).
Worked examples
Where it fits
- Device and IoT data: Pick 01.
Cheapest AWS front door if devices speak MQTT.
Last reviewed by Nicolas Dao