Skip to content
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

[AWS ORG] Permissions for our new organization account #2331

Open
1 task
jeniawhite opened this issue Jul 16, 2024 · 0 comments
Open
1 task

[AWS ORG] Permissions for our new organization account #2331

jeniawhite opened this issue Jul 16, 2024 · 0 comments
Labels
Team:Cloud Security Cloud Security team related

Comments

@jeniawhite
Copy link
Contributor

Motivation
Investigating the errors in the long living environment of the QA, I saw that we have a lot of errors on our new organization account.
We should make sure that we have permissions to perform our scans correctly.
Example:

failed to aggregate monitoring resources: operation error CloudTrail: DescribeTrails, get identity: get credentials: failed to refresh cached credentials, operation error STS: AssumeRole, https response error StatusCode: 403, RequestID: ID, api error AccessDenied: User: arn:aws:sts::ORGID:assumed-role/cloudbeat-root/aws-go-sdk-1720620241428501785 is not authorized to perform: sts:AssumeRole on resource: arn:aws:iam::OTHERID:role/cloudbeat-securityaudit

I saw that we have hundreds of errors like that to different resources.

Definition of done
What needs to be completed at the end of this task

  • We should be able to scan organization resources

Out of scope
What should not be included in this task

Related tasks/epics
Reference related issues and epics

@jeniawhite jeniawhite added the Team:Cloud Security Cloud Security team related label Jul 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:Cloud Security Cloud Security team related
Projects
None yet
Development

No branches or pull requests

1 participant