• 1
    What is AWS IoT Cloud?

    The AWS IoT is a cloud platform ☁ that provides services and solutions to connect and manage billions of devices. Since it is a part of Amazon Web Services, we can pipeline it with other products and services which will open more possibilities -

    image.png

    Collect, Store, and Analyze IoT data for industrial, consumer, commercial, and automotive devices 🚡. To manage and support these IoT devices in the real-world, AWS IoT Core supports below protocols -

  • 2
    I got my prototype manufactured from PCBWAY

    For this project and my other projects for PCB manufacturing and assembly, I take help from PCBWAY, they are the best in this business and I have been never let down by their quality.

  • 3
    Getting Started

    AWS IoT is an application that can be accessed through different methods - Device SDKs, Command Line Interface (CLI), Application Programming Interface (API), or Console (Dashboard).

    image.png

    In our case, we shall be using the AWS Console for a visual representation which is a better way to use an IoT Cloud Platform for connecting with the device.

    The 👨💻 Console has a message broker that allows the devices and clients that use MQTT and MQTT over WSS protocols to publish and subscribe to messages. It also supports devices and clients that use the HTTPS protocol to publish messages.

    Before we continue further, let us understand the concept of MQTT which shall be used as a communication protocol in this application.

    MQTT - Message Queuing and Telemetry Transport 🔀

    It is a publish/subscribe protocol for machine-to-machine communication. This simple protocol, is easy to implement for any client. Termed as the Pub and Sub, both are used for same purpose but different method.

    image.png

    Above we can see there are 2 sections (left & right) - Publish and Subscribe. And then there is a middleman - Broker.

    IoT Devices play the role to collect sensor data and send to the cloud (broker). While PC/Server/Mobile devices play the role to monitor and receive the sensor data to be viewed - Here, IoT Device is a Publisher, and PC Devices are a Subscriber.

    image.png

    [EXAMPLE] When a user1 publishes an image on social media, then only the user2 subscribed to user1 can view/receive the image. Here, the user1 is the PUBLISHER, user2 is the SUBSCRIBER, and the user1's account is the BROKER.

    According to the above analogy, the image that is published is the data, that was transferred from user1 to user2 📤. And that is the exact scenario in an MQTT Pub/Sub model.

    image.png

    image.png


    We have a more secure layer 🔒 to make sure the data is shared through a specific path, we call that 'topic', When user1 publishes data on topic, the subscriber automatically receives if already connected to the broker. Hence, the LOW latency.