MQTT AT Examples for Cloud

This document mainly describes how to connect your ESP32 to AWS IoT with MQTT AT commands.

Important

For details on how to use MQTT AT commands, please refer to MQTT AT Commands. You need to become familiar with the AWS IoT by reading the AWS IoT Development Guide.

Please follow the steps below to connect your ESP32 to AWS IoT with ESP-AT.

Obtain certificates and endpoints from AWS IoT
Connect to AWS IoT based on mutual authentication with MQTT AT commands

Obtain certificates and endpoints from AWS IoT 

Sign in to your AWS IoT Console account and switch to the IoT Core services.
Create an AWS IoT policy, thing, and certificates following the instructions in Create AWS IoT Resources.

Make sure you have got the following certificate and key files:

device.pem.crt (Device certificate)

private.pem.key (Private key)

Amazon-root-CA-1.pem (Root CA certificate)

Get the endpoint and bind the thing to the policy through the certificate according to the documentation Set up the policy.

The endpoint value has the format of xxx-ats.iot.us-east-2.amazonaws.com.

Note

It is strongly recommended to familiarize yourself with the AWS IoT Developer Guide. Below are some key points from this Guide that are worth noting.

All devices must have a device certificate, private key, and root CA certificate installed in order to communicate with AWS IoT.
Information on how to activate certificates.
Select Ohio as your region.

Connect to AWS IoT based on mutual authentication with MQTT AT commands 

Replace certificates

Open your local ESP-AT project and do the following:

Replace customized_partitions/raw_data/mqtt_ca/mqtt_ca.crt with Amazon-root-CA-1.pem.
Replace customized_partitions/raw_data/mqtt_cert/mqtt_client.crt with device.pem.crt.
Replace customized_partitions/raw_data/mqtt_key/mqtt_client.key with private.pem.key.

Compile and flash the AT firmware

Compile the ESP-AT project to build the AT firmware, and flash the firmware to your ESP32. For more information, please refer to Compile ESP-AT Project Locally.

Note

If you do not want to compile the ESP-AT project to replace certificates, you can directly use the AT command to replace certificates in the firmware. For more information, please refer to How to Update PKI Configuration.

Use AT commands to connect to AWS IoT

Set the Wi-Fi mode to station.

Command:
```
AT+CWMODE=1
```
Response:
```
OK
```
Connect to the AP.

Command:
```
AT+CWJAP=<ssid>,<password>
```
Response:
```
OK
```
Set the SNTP server.

Command:
```
AT+CIPSNTPCFG=1,8,"pool.ntp.org"
```
Response:
```
OK
```
Query the SNTP time.

Command:
```
AT+CIPSNTPTIME?
```
Response:
```
+CIPSNTPTIME:<asctime style time>
OK
```
Note:
- The <asctime style time> obtained at this time must be the real-time time of the set time zone, otherwise the connection will fail due to the validity period of the certificate.
Set MQTT user properties.

Command:
```
AT+MQTTUSERCFG=0,5,"esp32","espressif","1234567890",0,0,""
```
Response:
```
OK
```
Note:
- If the second parameter of AT+MQTTUSERCFG is 5, it is authenticated by both sides and cannot be changed.
Connect to AWS IoT.

Command:
```
AT+MQTTCONN=0,"<endpoint>",8883,1
```
Response:
```
+MQTTCONNECTED:0,5,<endpoint>,"8883","",1
OK
```
Note:
- Please fill in your endpoint value in the <endpoint> parameter.
- The port 8883 cannot be changed.
Subscribe to messages.

Command:
```
AT+MQTTSUB=0,"topic/esp32at",1
```
Response:
```
OK
```

Publish a message.

Command:

AT+MQTTPUB=0,"topic/esp32at","hello aws!",1,0

Response:

+MQTTSUBRECV:0,"topic/esp32at",10,hello aws!

OK

Example log

Log for normal interaction is as follows:

Log on the ESP32 side
Log on the AWS side

Provide feedback about this document