Adding the ability to snapshot multiple accounts within an organization. #5
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
This change adds the ability to download from multiple accounts that are within an AWS organization. This is done by modifying the config file with new options.
accountsis either an empty list to collect all accounts or individual json objects to specify specific accounts within the organization.Each account object needs at minimum an Id and optionally a role if different from the default role.
defaultRoleis the role used across all accounts (unless overridden by an account specific role). The user running the script will need the ability to assume the roles or else that account will raise an error when retrieving credentials.useAccountNameallows for each account directory to either be named after the ID or the human-friendly name.The following is an example configuration including only changes.
{ "accounts": [ { "id": "1234", "role": "Engineer" }, { "id": "5678" } ], "defaultRole": "Admin" "useAccountName": true }The outputs would look something like the following (I have cut out some of the JSON files to save space)