FAQs: Not connecting to MQTT broker (Why does location of AWS IoT server matter?)

Solved
PeterF's picture
PeterF
Moderator(15)

Topic started for Q&A on topic of Getting Started with AWS IoT

 

Q: Why does location of the AWS IoT server and MQTT broker matter?

 

A: Though AWS IoT supports multiple host server locations, in the AWS examples provided in WICED SDK the AWS IoT host is hard-coded to US East (N.Virginia) - as defined in the aws_common.h file:
#define AWS_IOT_HOST_NAME  “data.iot.us-east-1.amazonaws.com”

The application firmware will consequently attempt to connect to the MQTT Broker at this location. For this reason it is critical that the same server host “US East (N.Virginia)” be selected from pull-down menu at top of your screen, when using AWS IoT Console to create your AWS IoT Things, Certificates, Policies, etc

PeterF's picture
PeterF
Moderator(15)

If you are having certificate / authentication issues, check that the US East (N.Virginia) server host was used when you created your AWS IoT Things, Certificates, Policies,etc and that this is what your AWS application is connectiong to.