-
Notifications
You must be signed in to change notification settings - Fork 431
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
Permissions issues (Support cases, S3 Objects, ECS clusters, etc) - Docker on ECS #87
Comments
Hello @dfeldstarsky , thanks for reporting this out. You need to add ""s3:GetBucketLocation"" permission to the IAM role :) |
I have updated the IAM policy with the missing permissions: https://github.com/mlabouardy/komiser/blob/master/policy.json Let me know, if that fix your issues |
@mlabouardy thanks so much for the quick reply + suggested fix. I applied the permissions change from your new policy and indeed I now get all the S3 metrics :). Now the only permissions problems I see are AWS Support cases and correct ECS cluster counts. Cluster counts is still at 0 despite us having ~5. And we have 2 open AWS support cases. |
@dfeldstarsky you can fix AWS support cases issue by using "support:*" (I have updated the IAM policy) |
@dfeldstarsky I was able to reproduce the issue regarding ECS clusters, I will fix that by the end of today, meanwhile, I will close this ticket, and I let you raise an issue regarding ECS if you dont mind :) |
Done, opened a new issue 👍 |
Hiya - love the app and dashboard. Running into some issues similar to #85 and other permissions issues.
I can't see ECS clusters, S3 object size, number of support cases, etc. I have attached your komiser policy to the ECS workspace role and most of the permissions are working!
Permission issues shown. 0 bucket size for s3 shown.
I am deploying on ECS Fargate, with a task definition attached.
Logs showing 500 errors:
Task def json:
The text was updated successfully, but these errors were encountered: