Sharing AWS MQTT Connection between process

[caiotoledo-lunasystems]

In the project in which I'm working, we are going to perform provisioning on our device which is going to receive a certificate and assign it to a Thing in AWS IoT Core, the Thing name is going to be its Client ID.
Our Linux Embedded Device is going to have multiple services/processes which are going to need to communicate with AWS IoT Core.

But, as AWS Documentation makes it clear, two devices can not use the same Client ID:
https://docs.aws.amazon.com/iot/latest/developerguide/audit-chk-conflicting-client-ids.html
This conflict applies to two processes running on the same device as well.

Therefore I would like to know:
Is there a way to share the same MQTT Connection between multiple processes? In this case, reusing the same Connection for multiple processes.

One solution might be to create a "centralized" process to handle the MQTT Connection and make the other process communicate to this "central" process over IPC, but I was wondering if there's another possible solution for this matter.

[jmklix]

You can't share the MQTT connection between processes, but like you suggested you could create a centralized process to handle the MQTT connection. Something you might want to look into is using greengrass components and using a different component for each of your processes. Let me know if you have any more questions about this

[caiotoledo-lunasystems]

Thanks for the feedback @jmklix.

Regarding Greengrass, does that mean if I follow this example: https://github.com/aws/aws-iot-device-sdk-cpp-v2/blob/main/samples/greengrass/ipc/main.cpp I would be able to have multiple processes using MQTT?

What do you mean with:

using a different component for each of your processes.

Does it mean that I can't have multiple processes using, for example, AWS IoT Core even with greengrass?

[jmklix]

Greengrass components can be a lot of things:

Components can represent applications, runtime installers, libraries, or any code that you would run on a device

You can have multiple components doing different things and the greengrass nucleus will act as a central location and manage your MQTT connection to IoT Core. The components are just a structure of greengrass that can be compared to a process, but aren't limited to just that. It really just matters what you want to do with each process and why you are trying to split them up.

[github-actions[bot]]

Hello! Reopening this discussion to make it searchable.