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

Added instruction for organization level scan #126

Merged
merged 2 commits into from
Aug 15, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions usecases/accountsWithinOrganization/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
## Overview

As users launch more and more workload in AWS, users will eventually move themselves towards [AWS Organizations](https://aws.amazon.com/organizations/) to ease the management of their AWS workloads. For user to execute Service-Screener (SS) in one account is direct, but it can become tedious and repetitive if user has multiple AWS accounts within the same organization.

## Solutions

SS today support crossAccounts scanned, which required users to manually setup the crossAccounts.json file by providing the list of AWS accountID, roleNameToBeAssumed, and externalID. To accelerate the crossAccounts.json creation, you can now run ```python3 organizationAccountsInit.py``` and the crossAccounts.json will be generated based on the input given.

Then, you can execute the following to scan all your accounts within your organization
```
screener --regions ALL --crossAccount 1
```

Loading