1 Answers
1
So, I found out what it was - fresh pair of eyes and all that.....
In the IoT policy, rather than use the ARN of the Role Alias, I had used the ARN of the IAM role itself.
I changed that, and hey presto, all good.
answered 18 days ago
Relevant questions
Hot configure the newtork between gstreamer and Kinesis Video Stream?
asked 4 years agoUnable to receive messages in the Raspberry Pi connection example
asked 10 months agoCould not connect to the endpoint URL: "https://s3.local.amazonaws.com/"
asked a year agoThe image cannot be displayed because it contains errors
asked 4 months agoHi guys, Deployed the datasync agent on-premised (Vmware environment) successfully and did the "Test Network Connectivity" to AWS DataSync which is also successful.
asked 8 months agoUsing the KVS kvs_gstreamer_sample - errors trying to connect
asked 18 days agoI am trying to deploy the EKS cluster using s3 template but getting errors, please help me
asked 7 months agoUsing the encryption sdk within lambda
Accepted Answerasked 2 years agoHow to resolve the issues in viewing the dataset and creating the calculated fields when using edit dataset option in quicksight?
asked 8 months agoErrors attaching policies to the role
Accepted Answerasked 3 months ago
Great that you found the issue! If this is something that was not clear in the YouTube video, could you post a comment on the video? That way the author, Paul, could look to include an overlay in the relevant area to highlight the Role Alias vs IAMR role ARNs.