ACKF logoACKF
Internet of Things (IoT)

AWS IoT Core

View on GitHub

AWS IoT Core

A managed cloud service that provides a device gateway, message broker, device registry, device shadow, and rules engine to connect, authenticate, and route data from connected devices to AWS services. It operates as a regional message ingestion and control plane supporting MQTT, HTTP, and MQTT over WebSockets and an extensible rules engine for routing or transforming messages. It typically sits at the edge of an AWS backend to accept telemetry and commands from devices and forward them to analytics, storage, or serverless processing.

🗂 Resource Category

Internet of Things • Application Integration

🧠 Exam Memory Hook

Think: "Many devices + MQTT/HTTP broker + rules engine = AWS IoT Core"

📖 Ownership

Classification: AWS Managed Service

AWS responsibilities: AWS operates and manages the underlying service platform including the device gateway, message broker, rules engine, registry, shadow service, control plane APIs, service endpoints, and the infrastructure that hosts these managed components; AWS is responsible for the availability of the managed service platform and patching of the underlying AWS infrastructure and managed runtime components.

Customer responsibilities: The customer configures device identities, certificates, AWS IoT policies, rules engine actions, message routing, retention and transformation logic, device shadow document structure, integration targets (for example Lambda, Kinesis, S3), monitoring, logging, and operational alerting; the customer also secures device credentials, rotates keys/certificates, manages device firmware and application lifecycle, and enforces access control using IAM and IoT policies.

Patching responsibilities: AWS patches and maintains the physical infrastructure and the managed service platform that implements AWS IoT Core; hypervisor patching is performed by AWS as part of infrastructure management; guest operating system patching is not applicable to the AWS-managed IoT Core control plane; the customer is responsible for patching device operating systems, firmware, application runtimes, libraries, and dependencies on their IoT devices, and for updating any customer-managed components such as on-premises gateways or Greengrass cores.

🏗 Typical Architecture

💡 Top 5 Features

  • Managed device gateway and message broker that supports MQTT, HTTP, and MQTT over WebSockets.
  • Rules engine that filters, transforms, and routes device messages to AWS service targets and HTTPS endpoints.
  • Device Registry for storing device identities and metadata at scale.
  • Device Shadow service for storing and synchronizing a device’s reported and desired state.
  • Support for X.509 certificate based mutual TLS authentication and fine-grained IoT policies for authorization.

✅ Top 5 Use Cases

  • Ingest telemetry from large fleets of sensors and route messages to streaming or serverless back ends for processing.
  • Maintain and synchronize device state and command delivery using device shadow documents for remote control scenarios.
  • Filter and transform device data at the edge of AWS and route it to analytics services such as Kinesis or S3.
  • Implement secure device authentication and per-device authorization using certificates and IoT policies.
  • Bridge device events to AWS Lambda functions for real-time event-driven processing and backend integration.

🏗 Architecture Placement

AWS IoT Core typically sits between physically deployed devices and AWS backend services as the device-facing message gateway and control plane; devices initiate MQTT or HTTP connections to the regional IoT endpoint, and AWS IoT Core routes or forwards messages to configured targets (for example Lambda, Kinesis, S3, or DynamoDB) using the rules engine. It stores device metadata and shadow documents and integrates with IAM and IoT policies for authorization. Depending on requirements, edge compute components (for example AWS IoT Greengrass) or VPC-based services may be used alongside IoT Core.

🎯 Commonly Used With

- AWS Lambda
- Amazon Kinesis Data Streams
- Amazon S3
- Amazon DynamoDB
- AWS IoT Greengrass

🌍 5 Real-World Examples

  • A logistics operator ingests GPS telemetry from vehicle trackers to AWS IoT Core, routes location streams to Kinesis for real-time tracking, and stores historical traces in S3 for analytics.
  • A manufacturing plant connects vibration sensors to AWS IoT Core and triggers Lambda-based anomaly detection when telemetry matches predefined patterns to reduce unplanned downtime.
  • A utilities company collects smart meter readings via AWS IoT Core and routes aggregated data to DynamoDB and S3 for billing and long-term storage.
  • A healthcare device vendor securely authenticates patient monitoring devices with X.509 certificates through AWS IoT Core and uses device shadows to maintain desired sampling configurations.
  • A retail chain forwards POS device events from edge terminals to AWS IoT Core, where rules route transaction data to serverless consumers for real-time processing and auditing.

🎓 AWS Exam Clues

  • Choose AWS IoT Core when the requirement includes many devices connecting over MQTT/HTTP and a managed message broker is needed.
  • Use the rules engine when device telemetry must be routed or transformed to multiple AWS services without custom intermediary servers.
  • Device shadow support is a key indicator when the architecture requires cloud-side desired/reported state synchronization for devices.
  • Per-device certificate authentication and IoT policy-based authorization indicate IoT Core is the service for secure device connectivity.
  • Consider AWS IoT Greengrass or on-premises gateways when local processing, local resource access, or intermittent cloud connectivity is required alongside IoT Core.

📝 Quick Revision

AWS IoT Core is a regional managed message gateway and control plane for connecting, authenticating, and routing data from devices using MQTT/HTTP and device shadows. Use it when you need secure device connectivity, per-device identity, and routing to AWS services; plan for credential lifecycle, device firmware patching, and backend scaling and monitoring.

🏷 Keywords

MQTT • HTTP • WebSockets • Device Gateway • Message Broker • Device Registry • Device Shadow • Rules Engine • X.509 Certificates • IoT policies • Fleet Provisioning • AWS IoT Core Endpoint