Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Connecting to Greengrass Core #9

Open
erikkanderson opened this issue Jun 11, 2020 · 3 comments
Open

Connecting to Greengrass Core #9

erikkanderson opened this issue Jun 11, 2020 · 3 comments

Comments

@erikkanderson
Copy link

Is there anything special that needs to be done to connect to a Greengrass Core instead of the IoT Core?

In the code that I have written I can successfully connect to IoT Core. I use my endpoint address, the AmazonRootCA1.pem file, and my converted .pfx file. No problems.

However, I am now trying to connect to a Greengrass core instead. I've changed the address of the endpoint, using the group CA file, and re-converted the .pfx file to use the group CA file. Now when I try and connect to the greengrass core I get a "The remote certificate is invalid according to the validation procedure" error.

I am fairly confident that my group CA file is correct as is the IP address of the core, as I can connect to the core from other things (running on raspberry pis). Which makes me suspect that I did not convert the certificates correctly to .pfx, however, I'm using the same command line as I use to generate a .pfx to connect to IoT core.

Any suggestions?

@erikkanderson
Copy link
Author

After quite a bit of investigation and experimentation, I discovered that the Greengrass Group CA has to be installed in windows as a trusted root CA. After I did this, my .net application was able to connect to greengrass over MQTT.

The instructions I found for installing the group CA are at https://idk.dev/connecting-disparate-industrial-devices-and-applications-from-the-plant-floor-to-aws-using-kepserverex/.

@devnext2000
Copy link

I am having trouble connecting to IoT
errorIoT

help me, please

@erikkanderson
Copy link
Author

I've had a similar error in the past. At least for me, the solution was the certificate attached to the thing was not activated. Activated it, and hopefully it will work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants