- Newest
- Most votes
- Most comments
So, the cluster field in the Cloudform wasn't right, not exactly sure how that managed to send it into access denied territory for some reason but.. well it's fixed.
I had faced similar issue. I cannot say what exactly the issue you are facing but might help in how to solve.
Usually AWS errors will mention which particular permission is required or missed. I faced this Access Denied issue on 2 instances
- When I was creating S3 bucket with Bucket policy through Cloud formation. The role has necessary permission but Org level Bucket policy was denied hence I got Access Denied instead of S3 put bucket policy is needed error.
- When I was trying to access a file which is not present. The role has Get object permission but not S3 list object hence I got Access Denied instead of no such file or directory error.
How did I debug? - I checked the CloudTrail which will have event/log for every activity happened in AWS account.
HI KELNOR
There are a couple of possibilities why CloudFormation might be encountering an "Access Denied" error on Create Service even with an IAM role assigned and apparently assumed
please follow the links to resolve the issue:
Troubleshooting access denied error messages - AWS IAM: https://docs.aws.amazon.com/IAM/latest/UserGuide/troubleshoot_access-denied.html
AWS Cloud Formation S3 error: Access Denied:
Relevant content
- asked 3 years ago
- AWS OFFICIALUpdated 9 months ago
