Getting started in the AWS Marketplace

In order to ensure a positive experience loading Hyperglance via AWS Marketplace, it is important to follow our getting started instructions.

Setup Instructions:

TIP: To see what Hyperglance considers a resource see here

Note: Upgrading Hyperglance to the latest version

After you finish the set-up remember to upgrade Hyperglance to the latest version.

Follow these instructions to upgrade


Firstly go to the AWS Marketplace and find Hyperglance. We have multiple tiers depending on how many resources you have.

Choose 'Continue to Subscribe'. 


Accept the software terms.

Screenshot (6)


This will take us to a page describing the next steps, read and return to the launch page. 

Screenshot (7)

Select the blue button at the top right - 'Continue to Configuration

Screenshot (8)


It will take a few minutes before the subscription is ready. Once the subscription is live choose the region you want the Hyperglance instance to be created in.

Screenshot (9)

 Select the blue 'Continue to Launch' button (top right).

Screenshot (10)


 Select ‘Launch CloudFormation’ option.

Screenshot (11)

Once you have selected Launch CloudFormation the 'Launch' button will turn orange and you can select it.

Screenshot (12)

This takes us to CloudFormation in your AWS console. There is nothing to change here as the S3 template is already selected so click ‘Next’.

Screenshot (13)


In the 'Specify stack details' page you have the option to name the CloudFormation stack, and decide on things like assigning a public IP.

NOTE: Be careful when choosing the VPC & Subnet you want Hyperglance to be deployed in. It's possible to mismatch the VPC & Subnet causing the stack creation to fail.

NOTE: Hyperglance needs access to the AWS API in order to pull down the information needed.

Screenshot (14)


Once that’s all set click next

Screenshot (15)

You’ll then get the option to tag tags, in the screenshot we have added a Name tag of ‘Hyperglance’.

Screenshot (16)


Scroll down to the bottom of the page, select 'Stack creation options' and select 'Disabled' for 'Rollback on Failure'. This will allow you to see which steps failed if the stack has issues. After that, select 'Next'

Screenshot (17)

On the review screen scroll down to the bottom to accept the disclaimer and click on ‘Create stack’ so CloudFormation can start to create the Hyperglance instance.

Screenshot (18)

You’ll then be taken to the CloudFormation stack console page, the actual instance creation will take up to 10 minutes.

Screenshot (19)


Once the stack has been created successfully you need to look at the ‘Output tab’. This gives details of how you can connect to the Hyperglance Instance. By Default Hyperglance’s password is the instance ID, so copy that and then click on the link to go to Hyperglance. 

Screenshot (20)

NOTE: Be careful when copying and pasting the instance-id. Sometimes there is a copy/paste space at the end or start of the instanceid and that will cause the authentication to fail. 

Proceed to the Hyperglance console page.

We are now at the Hyperglance console. The default userid is ‘admin’ and the password is the instance-id of the Hyperglance instance.

NOTE: Make sure you use HTTPS (port 443) to connect to Hyperglance 



After logging in the first time you will be asked to select some regions for Hyperglance to monitor within. By default Hyperglance will pull in the topology from the account you’ve used to create the instance.

If you want to add other account(s) then Hyperglance can use STS Assume-Role to access other AWS accounts if you provide a suitable Role ARN for Hyperglance to use. You can add as many accounts as you need via this administration page.

Leave the "Is Billing Only" option unchecked so that Hyperglance will pull down inventory (as well as billing data, if available).

Update to the latest Hyperglance version


It is recommended to update to the latest Hyperglance version once you have finished the initial setup. Follow these instructions to upgrade

After upgrading all user data will be retained, including authentication credentials, Rules, and tag-view keys.