In order for Cloudaware CMDB collector to discover infrastructure running on the private network, customers must deploy a local proxy. Local collector proxy must have ingress access to the target endpoint and egress access to the Cloudaware TunHub's server.
Introduction
Proxy configuration can be deployed to any Breeze agent that meets requirements. Up to 2 Breeze agents (active and standby) can be designated to support single endpoint connection.
Customers are able to set up the TunHub integration using a self-service interface in Cloudaware Admin panel.
Breeze Setup
Select any existing or a new server that has access to the resources in your private network and may communicate to Cloudaware. Follow the steps below to install Breeze agent:
1. Log in to Cloudaware account → Admin → Breeze to download the Breeze agent.
2. Install Breeze on this server*.
Server requirements:
Linux only (Ubuntu v14 and newer, Centos/RedHat v6..8, Debian 9 and newer, Amazon Linux) CPU: 1 Memory: 256 MB minimum Storage: 200 MB | Ports: outbound TCP 443 for Breeze agent (dest: breeze-server.cloudaware.com) outbound TCP 443 for TunHub (dest: tunhub.cloudaware.com) |
Cloudaware Setup
1. Log in to Cloudaware account → Admin.
2. Find TunHub in the list of integrations. Click +Add.
3. Fill in the required information:
*Description - the integration name
**Primary Channel - Breeze Agent ID of Breeze agent installed on the host
***Standby Channel (optional) - Breeze Agent ID of Breeze agent installed on the reserve host. If Primary Channel is unavailable for any reason, Standby Channel will be used for Cloudaware TunHub integration until Primary Channel connection is restored.
Click Save to test the connection.
4. Review the integration details. The yellow light in 'Primary Channel' means that TunHub is waiting for the local collector proxy (Breeze) to connect.
5. Set up routes for your TunHub integration. Click three dots → Edit Tunnel & Routes → +Add Route.
Fill the form:
*Description - the route name
**Remote Host - Domain Name or IP address of the resource in a private network
***Remote Port - the port of the resource in a private network for Cloudaware to access (commonly 443)
Click Save. Breeze agent runs every 15 minutes, so allow some time for a route to get the green status and then proceed.
6. Once the route is pre-configured and ready, get the generated Destination Host and Destination Port to add your integration. For example, in case of JIRA running on a private network Destination Host and Destination Port will be used for URL field (e.g. https://tunhub.cloudaware.com:12345).
7. Go back to reviewing the integration details. The green light in 'Primary Channel' means that TunHub integration has been successfully added. If there is a red light, please contact support@cloudaware.com.
If the checkbox ‘Managed by Cloudaware' is checked, neither a managed tunnel nor its routes can be edited/deleted by a customer.