Thanks for using AWS IoT. As our docs(https://docs.aws.amazon.com/iot/latest/developerguide/thing-policy-variables.html) say, to use thing-policy variables these two things must be true.
- ClientId must match with ThingName.
- Certificate must be associated with the Thing (specified in the clientId).
A certificate can be associated with more than one thing so we depend on device giving the thing name while connecting to IoT core in clientId field. This is needed even if certificate is attached to a single thing because if the certificate is attached to another thing in its lifetime (maybe accidentally), we don't want existing devices to break as policy variables cannot be resolved if we cannot identify the thing uniquely.
We have a feature request in our backlog to support multiple client ids. We cannot give exact dates but we are working hard to get the features out based on the priorities.
I had overlooked the fact that the thing name should be equal to the client id.
LENGTH() function is not working on a string in a columnasked a year ago
Athena HIVE_METASTORE_ERROR when working with map<string, string> columns in parquet fileasked 10 months ago
Greengrass Lambdas Running on Core Device - Using a Variable in the Topicasked 2 months ago
How do you restrict AMI use with IAM using Deny and NotResourceAccepted Answerasked 4 years ago
how to put variable into a string as a prefix of function in Graphql?asked 3 months ago
Issue concating policy variables with a string in an iot policy's resource blockAccepted Answerasked 10 months ago
How to concatenate thing name with string in mqtt policy?asked 2 years ago
Send a text message and receive a responseasked 4 years ago
AWS IoT Policy - using * in combination with a text string or variableasked 2 years ago