3 ms·
Right, you can go to cloudtrail and probably get it, but I have definitely ran into things like service says you do not have access to resource or it does not e
by hobs 2y ago
Right, you can go to cloudtrail and probably get it, but I have definitely ran into things like service says you do not have access to resource or it does not exist - randomly providing the account some other tangentially related permission magically fixes it, I've found sometimes trying the UI and the API will give different errors to help, and neither is particularly more useful than the others.
- deleted 2y ago[deleted]
- bshacklett 2y agoassuming you can get the cloud trail message sometimes there’s more information that you can decode using the STS service: https://docs.aws.amazon.com/cli/latest/reference/sts/decode-authorization-message.html https://docs.aws.amazon.com/cli/latest/reference/sts/decode-...
- donavanm 2y agoLook in to the AWS IAM “service description files” aka SDF. Thats exposed via the console Policy Builder or Policy Evaluator logic. The SDF _should_ encode all the context (eg resource attributes, principal metadat) that goes in to the authz decision. The most common opaque issue youll see is where one action has other required resources/actions. Eg a single action attaching an ebs volume requires permission on both instance and volume and _maybe_ kms key with permissions across those services.