- 最新
- 投票最多
- 评论最多
Each device should have a unique certificate to authenticate with AWS IoT. When multiple devices use the same certificate, it might be a security breach.
For the problematic device(s): go to IoT Core -> Things -> select the thing -> Certificates -> click on the attached certificate -> Policies -> click on the policy (default policy name: GreengrassV2IoTThingPolicy) -> check to have something similar to:
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"iot:Connect",
"iot:Publish",
"iot:Subscribe",
"iot:Receive"
],
"Resource": "*"
}
]
}
Ressource line should be "*" (access to all topics, less secure but good for testing) or only the arn of the intended topic. Your current policy attached to the problematic devices might include only the arn of "sdk/test/js" which explains limited access to this topic only.
Please check the IoT policy attached to the new devices - does it include permissions to connect and subscribe to 'sdk/test/akm'?
The new Device are all connected with the same certificates? I cant find anything about policies by All Devices>Things. When i change the topic in the two newer devices to sdk/test/js it works.... So i guess the policies are correct? Correct me if im wrong
相关内容
- AWS 官方已更新 3 年前
- AWS 官方已更新 1 年前
- AWS 官方已更新 3 年前
- AWS 官方已更新 1 年前
Thanks it works !