-
-
Notifications
You must be signed in to change notification settings - Fork 103
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
elasticloadbalancing:DescribeTags
not added
#36
Comments
upon further review of my generated policy, some
perhaps the ARN was wrong? (too bust atm to got back and test. will do it if i can later) |
(redacted values in my arn fyi) |
Hey @rileytg, Thanks for raising! Looking over your ARN, it looks like there is one too many components at the end. Does removing the last part and its slash resolve your issue? i.e.
Regarding edits to the data source, the map is sourced from https://github.com/iann0036/iam-dataset/blob/main/map.json periodically, so edits are welcomed over there. |
ya that was the resolution. i did a bunch of manual cleanups regarding this. would i read the go code to figure out the format for map.json? or is it some kinda standard? |
i opened this ticket thinking that the generated ARNs are incorrect (aka bug), am i misunderstanding? |
Hey @rileytg, I realise my initial response was incorrect and that the original value you had should have worked. Per the SAR, the correct format is:
Could you reconfirm your fix? |
my fix was lazy 😞 i did:
i’ll need to tighten this down over the coming weeks and i’ll update here if my work is useful to others/this project. thanks for all your work here, this has been an incredible help. |
When I run
terraform apply
as an admin, it works with 0 changes. When I apply the generated policy to a new user, I get... is not authorized to perform: elasticloadbalancing:DescribeTags
Adding this fixes my issue:
I saw some chatter on an issue that this can be updated in
iamlivecore/map.json
, but didn't follow enough to submit a pull. Happy to do so with some guidance.The text was updated successfully, but these errors were encountered: