1. Prerequisites - Before you start
We know you're excited to get going but it pays to be prepared, make sure you the have following things ready:
- Choose or create a suitable VNet and Subnet that will host Hyperglance. See section "1.1 Creating a suitable network environment" below.
- Set up Cost Exports - This is how Hyperglance ingests your billing data.
1.1 Creating a suitable network environment
Easiest Option -- For trials and simple installs
The easiest way to deploy Hyperglance is as a public VM. When prompted by the ARM template choose the option to create/attach a public IP address.
When deploying Hyperglance you will be prompted to select (or create) a VNet and Subnet to deploy the Hyperglance Virtual Machine into.
To operate correctly the Hyperglance VM needs to be launched into a networking environment that allows the following types of access:
- Outbound access:
- To the Azure APIs.
- Inbound access:
- Users need HTTPS inbound access to reach the Hyperglance web interface
- Admins may also want SSH access (if not using SSM)
Examples:
Outbound access to the AWS APIs can be achieved in a few ways, for example:
- The VM is given a Public IP
- The VM communicates through a NAT Gateway
Inbound access for users to reach Hyperglance can be achieved in a few ways, for example:
- The VM is given a Public IP
- The VM is placed behind a LoadBalancer
- A VPN connection into the cloud environment
- A Bastion Host through which users will connect to first
2. Launch the ARM template
Click a button to launch the template:
(The ARM template itself can be found in our github deploy repo.)
The Hyperglance ARM template uses a custom UI definition to provide you with helpful notes and prompts to guide you through deploying the stack field by field:
3. Log in and activate
Congratulations you have deployed Hyperglance into your cloud environment!
Now log in and activate:
- Visit: https://IP_OF_YOUR_VM
- At the login screen the default login user details are:
- Username: admin
- Password: The Computer Name you assigned to the VM
- Follow the on-screen prompts to accept the EULA and activate the product with a commercial license key or start a trial.
4. Connecting subscriptions
- See: How to add Azure Subscriptions
- See: How to add AWS Accounts
- See: How to add GCP Projects
- See: Connect 3rd party tooling (email, slack, teams, JIRA)
- See: Hyperglance Automations