Once you have you have the initial configuration done you will want to add more accounts for Hyperglance to connect to. This is done by creating an IAM role in the account you want Hyperglance to pull from.
NOTE: You can't use ARNs when running Hyperglance on Azure. You need to use an IAM Access/Secret key.
Step 1. Create a policy in the account you want Hyperglance to connect to
a. Go to the AWS console, then the 'IAM' section, 'Policies' then 'Create Policy'
b. Select the 'JSON' tab
c. Copy one of JSON policies from our policy requirements page and overwrite the text in the box. You can choose a Read-Only or Read-Write policy.
d. Name the Policy and select 'Create Policy'
Step 2. Create a Role
a. Go to the account Hyperglance is running in and copy the 'Account ID' (Easiest way is via the 'My Account' Section in the AWS console)
b. Go back to the IAM section in the AWS console of the account you want Hyperglance to connect to and 'Create Role'
c. Select 'Another AWS Account', paste the Account ID of the account Hyperglance is running in and select 'Next: Permissions (Leave both 'Options' tick boxes unchecked)
d. Search for the Policy you created earlier, select the tick box and click 'Next: Review'
e. Name the role and select 'Create role'
f. You will then see a list of all your roles. Select the role you just created
g. Copy the 'Role ARN'
h. Paste the Role ARN into the Hyperglance 'New Account' dialog. Select the regions you are interested in and select 'Submit'
Choose from either the GovCloud regions or the standard regions (it is not possible to choose from both sets at once).
Hyperglance will then connect to the AWS API and pull the new account's details. The time it will take varies depending on a number of factors but it shouldn't take longer than a few minutes.