-
Notifications
You must be signed in to change notification settings - Fork 65
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #126 from kuettai/main
Added instruction for organization level scan
- Loading branch information
Showing
1 changed file
with
13 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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 | ||
``` | ||
|