> ## Documentation Index
> Fetch the complete documentation index at: https://cloud-architect.ipoint-labs.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Wokwi IoT Device Simulation with AWS IoT Core Real-Time Dashboard
> Hands-on lab · 45m
Launch this lab in the IP Lab Portal, then follow the steps below in the AWS console.
Open IP Lab Portal
## Overview
### Project Details
1. In this lab, we demonstrate how **AWS IoT Core** can seamlessly integrate with **AWS Lambda** to process IoT device messages in real time. You will simulate an IoT device using the **Wokwi ESP32 emulator**, connect it to **AWS IoT Core**, and send telemetry data that triggers a **Lambda function**. The processed data is then reflected on a **real-time dashboard hosted on an S3 static website**.
2. Duration: **2 hour**.
3. AWS Region: **US East (N. Virginia) us-east-1**.
### Prerequisites (in VS Code)
* Install the following extensions in Visual Studio Code:
* **Wokwi**
* **PlatformIO IDE**
* **C/C++**
### Introduction
#### What is AWS IoT Core?
1. **AWS IoT Core** is a managed cloud service that enables connected devices to easily and securely interact with cloud applications and other devices
2. AWS IoT Core allows billions of devices to connect securely to the cloud, enabling communication between devices and cloud applications via standard protocols like MQTT, HTTP, and WebSockets
3. The service provides a message broker that routes messages between devices and applications, ensuring reliable communication. It supports one-to-one or one-to-many communications, allowing for complex interactions.
4. AWS IoT Core offers robust security features, including device authentication and authorization using X.509 certificates, AWS Identity and Access Management (IAM), and encryption of data in transit
5. AWS IoT Core integrates seamlessly with other AWS services, such as AWS Lambda, Amazon S3, and Amazon DynamoDB, enabling users to build scalable IoT applications that leverage the full AWS ecosystem.
#### Project Features:
* **Simulated IoT Device (Wokwi ESP32):**
* Use Wokwi’s online emulator to simulate an ESP32-based IoT device without any physical hardware.
* **Secure Device Authentication:**
* Attach AWS IoT Core certificates to enable secure MQTT communication.
* **AWS IoT Core Integration:**
* Establish real-time MQTT communication between the device and AWS.
* **Lambda Function Trigger:**
* Use an AWS IoT Rule to trigger a Lambda function on each device message.
* **Real-Time Web Dashboard:**
* Host a live HTML dashboard on Amazon S3 with static website hosting.
* **IoT Core Test Client:**
* Monitor messages sent by your IoT device directly within AWS.
#### Benefits:
* **No Hardware Required:**
* Develop and test IoT applications entirely in the cloud using Wokwi.
* **Cost Efficiency:**
* Pay only for Lambda executions; no need for always-on compute.
* **Hands-On with AWS Security:**
* Learn how to manage device authentication with IoT certificates and policies.
* **Real-Time Processing:**
* Process data instantly using AWS Lambda for analytics or actions.
* **Data Visualization:**
* Build dashboards to visually monitor IoT metrics using static web hosting.
* **Scalable Architecture:**
* Gain insight into a serverless, event-driven architecture suitable for production IoT solutions.
### Architecture Diagram
### Task Details
1. Sign in to the AWS Management Console.
2. Create an IoT Policy.
3. Create an IoT Thing.
4. Activate the Wokwi license key in your browser.
5. Attach the AWS IoT certificates in the code.
6. Create a public S3 bucket.
7. Upload the HTML file and enable static website hosting.
8. Create a Lambda function.
9. Create an IoT Core rule.
10. Check IoT messages in the AWS IoT Core test client.
11. Run the wokwi code and check AWS IoT Core test client.
12. Check the live website and ensure data updates in real time.
### Launching Environment
1. To launch the lab environment, click on the **Start Project** button.
2. Please wait until the cloud environment is provisioned. It will take less than a minute to provision.
3. Once the Project is started, you will be provided with **IAM username, Password, Access Key and Secret Access Key**.
> **Note:** You can only start one lab at any given time.
## Lab guide
### Lab Steps
#### Task 1: Sign in to AWS Management Console
1. Click on the **Open Console** button, and you will get redirected to AWS Console in a new browser tab.
2. On the AWS sign-in page,
* Leave the **Account ID** as default. Never edit/remove the 12 digit Account ID present in the AWS Console. otherwise, you cannot proceed with the lab.
* Now copy your **User Name** and **Password** in the lab Console to the **IAM Username and Password** in AWS Console and click on the **Sign in** button.
3. Once Signed In to the AWS Management Console, Make the default AWS Region as **US East (N. Virginia) us-east-1**.
#### Task 2: Create an IoT Policy
1. Make sure you are in the **US East (N. Virginia) us-east-1** Region.
2. Navigate to **IoT Core** by clicking on the Services menu in the top, then click on IoT Core.
3. From the left menu on Bedrock page click on **Policies** Under Security
4. On the Policy page click on **Create policy** button.
5. For policy name: Enter **whiz-policy**
6. For Policy Document Select JSON remove the existing and copy paste the below policy
```
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": "*",
"Resource": "*"
}
]
}
```
7. Click on **Create** button
#### Task 3: Create an IoT Thing
1. On the left side menu Click on **Thing** under All devices.
2. Click on **Create things** button.
3. For Number of things to create: Select **Create single thing** and click on **Next** button.
4. For Thing name: Enter **whiz-thing**
5. Leave rest as default and click on **Next** button.
6. For Device Certifications leave it as default and click on **Next** button.
7. For Attach Policies select whiz-policy created above and click on **Create thing** button.
8. Download all the 5 certificates and keys in your local and click on Done.
9. Once certificates get downloaded navigate to downloads folder to view downloaded files.
10. Now first we will rename the files we will be using them later to configure authentication for the device
* Rename the certificate.pem.crt file to : **device.pem.crt**
* Rename the private.pem.key file to : **private.pem.key**
#### Task 4: Activate the Wokwi license key in your browser
1. Download the "[AWS\_IoT\_Core](https://labresources.whizlabs.com/d4af9350a40053467c4d40549623c9a7/aws_iot_core.zip)" file and extract it.
2. Navigate and Open the "**aws\_iot\_core**" folder.
3. Open the "**diagram.json**" file click "**Get your license key**" then click "**Open**".
4. Click "**Get your license**" log in with your email or Gmail ID then click "**Get your license**" again.
5. Click **Get your license.**
6. Once the popup appears in your browser, click "**Open Visual Studio Code**" allow the **Wokwi Simulator** extension check the checkbox and click "**Open**".
?7. If you get the following notification, click **Do not ask me again,** and Select **Open.**
?
#### Task 5: Attach the AWS IoT certificates in the code
1. Navigate to **AWS iot core** service, then Click “**Connect one device**”
* Scroll down to find and copy the endpoint command, e.g.: **arti9nb0f3kjog-ats.iot.us-east-1.amazonaws.com**
* Open **VS Code** aws\_iot\_core **src secrets.h**
* Replace the existing endpoint "aws\_end\_point" in the **secrets.h** file
2. Copy and paste the certificates in “**secrets.h**” : Amazon Root CA1, Device Certificate, and Private Key in the respective place.
3.Now, Copy paste the **“device\_certificate”** and **“private.key**”
4.Open **main.cpp,** Click the tick button on the top right to compile
#### Task 6: Create a public S3 bucket
In this task, we are going to create a new S3 bucket in the US East (N. Virginia) region with a unique name disabling ACLs, and allowing public access for hosting the static website.
1. Navigate to S3 by clicking on the **Services** menu at the top, then click on **S3** in the Storage section.
2. In the S3 dashboard, click on the **Create Bucket** button.
3. In the General Configuration,
* Select Bucket Type : **General purpose**
* Bucket name: Enter “**whizlabs-iot-dashboard**”
> **Note:** S3 bucket name is globally unique, choose a name that is available.
4. AWS Region: Select **US East (N. Virginia) us-east-1**
5. Object ownership: Select **ACLs disabled** (recommended) option
6. In the option of Block Public Access settings for this bucket, Uncheck the option of Block all public access.
* Check the I acknowledge that the current settings might result in this bucket and the objects within becoming public checkbox.
7. Keep everything default and click on **Create Bucket** button.
#### Task 7: Upload the HTML file and Enable Static Website Hosting settings
In this task, we will enable static website hosting for our S3 bucket, configure it to use index.html and error.html, copy the provided endpoint, upload two files, and configure the bucket policy by copying its ARN and pasting the provided policy code.
1. To proceed, go to the S3 bucket name that you created and click on it. After that, navigate to the **Properties** tab which can be found at the top of the screen.
2. Scroll down to the Static website hosting section and click on **Edit** button.
3. In the Static website hosting dialog box
* Static website hosting: Select **Enable**
* Hosting type: Choose Host a static website
* Index document: Type **index.html**
* Error document: Type **error.html**
* Click on Save Changes.
4. Go to the **Properties** tab of your S3 bucket, and find the Static website hosting section. Copy the **Endpoint** provided in this section to your clipboard and save it for future reference.
5. The next step is to download the zip file by clicking on the replace the le [html\_file](https://labresources.whizlabs.com/d4af9350a40053467c4d40549623c9a7/html_file.zip), extract it, and upload two files named **index.html** and **error.html** to the S3 bucket you created earlier.
6. To configure your S3 bucket, access the Permissions tab and make the necessary configurations.
* In the Permissions tab, Click on the **Edit** button beside the Bucket Policy.
* You will be able to see a Blank policy editor.
* Before creating the policy, you will need to copy the ARN (Amazon Resource Name) of your bucket.
* Copy the ARN of your bucket to the clipboard. It is displayed at the top of the policy editor. it will look like **ARN:“arn:aws:s3:::your-bucket-name"**.
* In the policy below, Update the **bucket ARN** on the Resource key value and paste the below policy code in the editor.
```
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "PublicReadForWebsite",
"Effect": "Allow",
"Principal": "*",
"Action": "s3:GetObject",
"Resource": "arn:aws:s3:::replace-the-bucket-name/*"
}
]
}
```
> **Note :** Ignore if any error popped up.
7. Click on **Save** changes button.
#### Task 8: Create a Lambda Function
In this task, we are going to create a Lambda function which is used to process the device messages.
1. Navigate to the services menu at the top, then click on Lambda under the Compute section.
2. Click on the Create a function button.
* Choose: **Author from scratch**.
* Function name: Enter “**WhizFunction**”
* Runtime: Select **Python 3.13**
* Architecture : **x86\_64**
* Click “**Change default execution role**” -> choose “**Use an existing role**”
* Select “**Lambda\_role\_ xxx**”
3. Leave other fields as default and click on **Create function button**
4. If you scroll down a little bit, you can see the Code source section.
5. Remove the existing code in AWS lambda **lambda\_function.py** Copy the below code and paste it into your lambda **lambda\_function.py** file.
##### Code here:
```
import boto3
import json
s3 = boto3.client('s3')
bucket_name = 'bucket-name' # replace with your actual bucket
def lambda_handler(event, context):
print("Received from IoT:", event)
sensor_data = {
'timestamp': event['timestamp'],
'humidity': event['humidity'],
'temperature': event['temperature']
}
s3.put_object(
Bucket=bucket_name,
Key='latest-data.json',
Body=json.dumps(sensor_data),
ContentType='application/json'
)
return {"statusCode": 200}
```
6. Replace the bucket name.
7. Save the function by clicking on **Deploy** button.
#### Task 9: Create an IoT Core rule
In this task, we will create an AWS IoT rule which will call Lambda function to process the messages from the device to AWS IoT core.
1. Open the IoT Core console on the left side menu click on **Rules** under Message routing.
2. Click on **Create rule** button.
3. For Rule name: Enter **whiz\_rule** and click on **Next** button.
4. For the SQL Query Statement copy paste the below sql statement and click on **Next** button.
```
SELECT * FROM 'iot/whizlabs'
```
5. Now to Attach rule actions search for Lambda and select Lambda action.
* For Lambda function: Select **WhizFunction**
* Lambda function version: Select **\$Latest**
6. Review all the details and click on **Create** button.
#### Task 10: Check IoT messages in the AWS IoT Core test client
In this task, we will test message sending and receiving using the MQTT client in the AWS IoT Core dashboard.
1. On the AWS **IoT Core** console, click on **MQTT test client** and Click on the **Subscribe** to a topic tab.
2. For topic filter : Enter **iot/whizlabs** and click on **Subscribe** button.
3. Scroll down to view the subscription.
4. Now, click on **Publish** to a topic tab.
5. For Topic name: Select **iot/whizlabs**
6. For the the Message payload copy paste the below message and click on Publish button.
```
{
"timestamp": "20260701",
"humidity": 10,
"temperature": 90
}
```
7. To verify the message, go to the “**Subscribe to a topic**” tab in the MQTT client dashboard.
8. You will see the incoming messages displayed in real time as they are published.
#### Task 11: Run the wokwi code and check AWS IoT Core test client
1. Open the **aws\_iot\_core** folder, then navigate to the **src directory** and open the **main.cpp** file. Wait 2–3 minutes
2. To compile the code, click the checkmark button in the top right corner.
3. Once the code compiles successfully, open the diagram.json file.
4. Click the “**Run**” button. Please wait 2–3 minutes, as it may take some time to connect to AWS IoT Core.
5. Once successfully connected, the device will start sending data in JSON format.
6. To verify the data is being sent, go to the AWS IoT Core MQTT test client.
7. In the “**Subscribe to a topic**” tab, enter the topic used in your code (e.g., iot/whizlabs) and click Subscribe.
8. You will see the JSON-formatted messages appear in real time — this confirms successful data transmission from your device to AWS IoT Core.
#### Task 12: Check the live website and ensure data updates in real time
1. Go to the S3 bucket where your files are stored. Click on the **index.html** file to open its details.
2. Copy and click the “**Object URL**” from the file overview section — this is the public link to access the web page (if permissions allow).
3. The index.html file will open as a webpage. You should now see your hosted web content rendered in the browser.
4. Click to change the value from the sensor . (vscode)
5. The updated data will be sent through AWS IoT Core and you will see the values update live on the webpage.
6. If the data does not update on the webpage, try rerunning the Wokwi simulator. After restarting, wait for it to reconnect to AWS IoT Core, and the live data should begin updating again.
> ##### Do You Know?
>
> “ AWS IoT Core can handle billions of messages from millions of devices simultaneously — and route them to AWS services like Lambda, S3, DynamoDB, or even Machine Learning models in real time. It uses MQTT, HTTP, and WebSocket protocols, making it flexible for different types of IoT devices — from microcontrollers to complex edge systems. ”
[https://labresources.whizlabs.com/d4af9350a40053467c4d40549623c9a7/chrome-capture-2025-8-5\\\_37\\\_26.gif](https://labresources.whizlabs.com/d4af9350a40053467c4d40549623c9a7/chrome-capture-2025-8-5\\_37\\_26.gif)
### Completion and Conclusion
1. You have successfully created an IoT Policy
2. You have successfully created an IoT Thing
3. You have successfully created a Wokwi simulation dashboard using VS Code.
4. You have successfully created a Lambda Function.
5. You have successfully created an IoT Rule.
6. You have successfully created and launched an Amazon S3 bucket.
7. You have successfully configured the bucket to host a static website.
8. You have tested your static website to make sure it works correctly.
### End Lab
1. Sign out of AWS Account.
2. You have successfully completed the lab.
3. Once you completed the steps, click on **End Lab** from your IP Lab Portal and wait till the process gets completed.
## What gets checked
When you press **Check my work**, the platform verifies each of these:
* **Create an AWS Lambda Function** — Check whether a Lambda Function is created or not
* **Create IoT Core Rule** — Check whether an IoT Core Rule is created or not.
* **Create IoT Core Thing** — Check whether an IoT Core Thing is created or not.
* **Create IoT Core Policy** — Check whether an IoT Core Policy is created or not.
* **Create Public AWS S3 Bucket** — Check whether a Public S3 Bucket created or not
## Related help
* [FAQs and Troubleshooting](/aws-saa/support/faqs-and-troubleshooting)
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.