AWS IoT detecting connection attempts

0

I've been trying to connect a PIC-IOT WA to my AWS IOT instance for a few days now, even digging into old provisioning code with no luck.

I've tried both of these tutorials:

  1. http://ww1.microchip.com/downloads/en/AppNotes/AN3089-Repurpose-AVR-IoT-WG-to-Connect-to-AWS-00003089A.pdf
  2. https://github.com/microchip-pic-avr-solutions/microchip-iot-developer-guides-for-aws/tree/master/connect-the-board-to-your-aws-account

The provisioning code does setup a Certificate Authority and also has steps for a rule and lambda functions to perform JITR. I have followed these steps closely and am unable to diagnose if the device is unable to connect (or not trying to connect) OR if the rules aren't being implemented.

As far as I can see through Cloudwatch is that the Lambda function never gets instantiated. The AWS IoT Rule is pretty straightforward:

SELECT * FROM '$aws/events/certificates/registered/#'

and if this happens trigger the lambda function. All the policies and user roles are set. From the code in the Lambda function, it checks for the certificate of the device and creates the "thing" based on the certificate and device ID.

From my perspective, it looks like the problem is either

  1. Certificate isn't loaded to the device properly through the provisioning script and so the device is trying to connect but is not successful
  2. The certificate is setup on the device properly but the rule isn't actually executing as expected.

I am reaching out to Microchip for #1, but was curious if there was anything I can do to check if the device is attempting to connect to the cloud. Or if there is a different rule I can setup to log connection attempts.

Note: the device is able to connect to the Microchip AWS instance through provisioning tool (option to connect to "sandbox")

Any help or advice here would be appreciated!!

已提问 4 年前381 查看次数
1 回答
0

Accidentally came to the solution.

The solution was that us-west-1 somehow didn't allow our devices to connect. When we switched to us-east-1 or us-east-2, there wasn't a problem.... Not sure why this would happen. I hope these odd faults aren't representative of the platform. But moving on to the next challenges!

已回答 4 年前

您未登录。 登录 发布回答。

一个好的回答可以清楚地解答问题和提供建设性反馈,并能促进提问者的职业发展。

回答问题的准则