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

Organizations using SCPs to Restrict Regions #682

Closed
andrewkrug opened this issue Mar 11, 2020 · 3 comments
Closed

Organizations using SCPs to Restrict Regions #682

andrewkrug opened this issue Mar 11, 2020 · 3 comments

Comments

@andrewkrug
Copy link
Contributor

CloudMapper uses ec2.describe_regions() to pull back which regions to iterate over. Is there a better way to get this in an org that restricts regions using SCPs? Currently this causes a lot of access denied errors as cloudmapper tries to run describe calls in regions that aren't enabled.

@0xdabbad00
Copy link
Collaborator

I wanted to avoid hard-coding a list as AWS adds more regions, but it could make sense to fall back to a hard-coded list where this call is restricted. There has been this PR to filter on the regions you collect from for this PR #496 and issue #549

@0xdabbad00 0xdabbad00 added this to the 2.8.3 milestone Apr 14, 2020
@dr460neye
Copy link

Thanks for showing up a ticket about this exists already.
Please be aware, that thee "hardcoded" region does not only appear in the ec2.describe_regions part.
It appears way more often in the meaning of "hardcoded".
Maybe a effortless workaround could be, that there is on top of the "default" region also an "api" region.
This is available for all services except the "universal/global" ones. This could get rid of the situtation that my "hosting" region is depending somehow on the api region.

@0xdabbad00 0xdabbad00 removed this from the 2.8.3 milestone Aug 12, 2020
@0xdabbad00
Copy link
Collaborator

This issue has been resolved via #698 where you can now define which regions to collect from.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants