1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
0
As described, it seems your certificates are good - each device has its own set of certificates, generated when the things have been created. You don't need to copy certificates from one device to another.
Here are some things to check:
- Are your client devices associated to the GG core device? Ref. https://docs.aws.amazon.com/greengrass/v2/developerguide/associate-client-devices.html
- Here is how a client device connects to a GG core device with MQTT: https://docs.aws.amazon.com/greengrass/v2/developerguide/connecting-to-mqtt.html
- Please insure the client device auth component (aws.greengrass.clientdevices.Auth) is installed and running on the GG core device. It authenticates client devices and authorizes client device actions. Ref. https://docs.aws.amazon.com/greengrass/v2/developerguide/client-device-auth-component.html#client-device-auth-component-configuration
con risposta 2 mesi fa
Contenuto pertinente
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata un anno fa
Hi. To add a little bit, when you use Greengrass client devices, the MQTT broker on the core device has its own CA. That's the CA that should be on each client devices, for validating the server certificate (because, in this case, the server is the MQTT broker on the Greengrass core device, not AWS IoT Core).
More information here (one of the links ggainaru already supplied): https://docs.aws.amazon.com/greengrass/v2/developerguide/connecting-to-mqtt.html