AWS IoT Core
AWS managed IoT service for securely connecting, managing, and ingesting data from millions of IoT devices using MQTT, HTTP, and WebSockets, with rules-based data routing to AWS services.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
X.509 certificates per device + IAM for management API. MQTT with TLS. IoT policies control device permissions. SOC2, FedRAMP, ISO27001. Device provisioning requires careful certificate management.
⚡ Reliability
Best When
You're building an IoT solution on AWS and need enterprise-grade device management, secure communication, and native integration with AWS analytics and storage services.
Avoid When
You need a simple MQTT broker, multi-cloud device management, or your IoT platform is already Azure or Google Cloud.
Use Cases
- • Registering and managing IoT device fleets via Thing Registry API
- • Publishing commands to devices via MQTT or HTTP from agent workflows
- • Reading device shadow state (desired vs reported) for device status queries
- • Configuring IoT rules to route sensor data to DynamoDB, S3, or Lambda
- • Remote device configuration and OTA firmware update orchestration
Not For
- • Teams not in the AWS ecosystem
- • Simple MQTT brokers without device management (use HiveMQ or Mosquitto)
- • Extremely cost-sensitive deployments with millions of messages/day
Interface
Authentication
Devices authenticate via X.509 mutual TLS certificates. AWS IoT policies control what each device can publish/subscribe to. Human/service access uses IAM SigV4. Custom authorizers for non-standard auth.
Pricing
Per-message and per-operation pricing. Costs scale with device fleet size and message frequency. Data transfer to other AWS services incurs additional costs.
Agent Metadata
Known Gotchas
- ⚠ Certificate provisioning requires careful lifecycle management — lost certificates cannot be recovered
- ⚠ Device Shadow has a 400KB size limit — large state objects must be chunked
- ⚠ MQTT topic names must not start with $ (reserved for system topics) — topic naming collisions cause silent failures
- ⚠ IoT Rules Engine processes messages asynchronously — agents cannot rely on immediate routing
- ⚠ Thing types and attributes are schemaless — agents should validate data shape before publishing
- ⚠ Cross-region IoT requires separate endpoints and Thing registries — no global registry
Alternatives
Full Evaluation Report
Detailed scoring breakdown, competitive positioning, security analysis, and improvement recommendations for AWS IoT Core.
Scores are editorial opinions as of 2026-03-06.