aws-iot-device-sdk-python | SDK for connecting to AWS IoT from a device using Python

I'm trying to connect to AWS IoT Core via aws-iot-sdk-js-v2 and receiving the following error when I'm running the PubSub example as described below:

I'm setting up an AWS IoT MQTT connection from a Python environment using Python package awsiotsdk. I have followed this example https://github.com/aws/aws-iot-device-sdk-python-v2/blob/main/samples/pubsub.py and gotten the demo publish/subscribe to work, so I have all the pieces.

The only difference from the demo is that in my environment the certificates all reside in memory rather than on disk. A hack solution would be to write them to a temp location on disk and follow the example.

I would prefer to simply instantiate the appropriate AWS authentication class which can accept a file-like object rather than a string filename. However following the code only leads me to c-binding dead ends.

How can I create an MQTT client using in-memory certificates?

I'm following the pubsub.py example code for AWS IoT using MQTT here. In particular I'm connecting to MQTT using the awsiotsdk.

That example works ok, but it connects to MQTT as a generic client, not as a specific device.

I would like to connect to MQTT to publish and subscribe as a specific device. In particular I want to be able to query for connected devices and see this device show up.

In the demo code I see that --client-id is included. By default it uses a UUID to generate a unique client ID for the demo. I've tried setting the client-id to the thing ARN arn:aws:iot:us-west-2:123456789012:thing/test

What I want/expect to see is the following search show the connected thing. The query comes back empty while the pubsub demo is running. The fact that it's empty tells me that the pubsub example is connecting as an MQTT client, not as a device. How do I connect as a device?

I'm following the example pub/sub in awsiotsdk.

I'm creating an AwsCredentialsProvider class (api docs) from:

I am using MOKOSMART_mkgw1 to collect data and send it to AWS IoT Core. for that, I need to set the following configurations,

1. endpoint (aws iot endpoint)
2. topic (any)
3. device certificate and private key
4. root ca.

I was able to connect and send data to aws iot core.

i have greengrass running, on ip 192.196.1.12 on port 8883 (windows machine). i download Group CA using basic discovery api. so i used this mqtt settings for device:

1. broker endpoint (192.168.1.12:8883)
2. topic (same as registered in subscription in aws iot GG)
3. device certificate and private key (the device is registered in aws iot GG)
4. Group CA (downloaded by basic discovery sample application)

but i am still not able to connect to aws gg?

my understanding is aws GG also has a MQTT broker. so by providing a proper authentication and topic, i should be able to connect to it, whether or not I have aws device SDKs or not. am i wrong? what does "basic discovery example" do extra to be able to connect to aws gg ??