- Newest
- Most votes
- Most comments
From the error message it looks like the role being used by Sagemaker does not have permission to publish to SNS. You need to attach a policy to the role that grants Sagemaker the ability to publish SNS messages to the relevant topic.
Hello,
Not all resources support * at the beginning of the name. So try with only * just to rule it out. But as you said in your question, you have added Admin rights, so it's probably not that.
I would first look at the SNS topic policy to ensure it's not blocking anything, then have a look at the role permissions boundary.
In some cases, I have seen the real errors "hide behind" an AccessDenied, like a wrong key och S3 giving AccessDenied instead of 404. And Creating an ECS cluster will fail on AccessDenied because its lacking tagging permission even though you can create a cluster. So an overall sanity check of the rest of your config could help.
Hope it helps!
Relevant content
- asked 5 years ago
- Accepted Answerasked 2 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
Hello Indranil, I think I attached the right permission. You can see this picture: https://1drv.ms/u/s!Alcer1f10FI6itBh-46Md-YtBtyCWw?e=C1KqYf