Page Comparison

Image Added To see how Cloudaware seamlessly integrates with TunHub in action, request a demo.

Introduction

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. 

...

...

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.

...

2. Install Breeze on this server*.

Server requirements:

3. Once Breeze is installed, the server gets access to breeze-server.cloudaware.com and may act as TunHub proxy.

...

****Dedicated Port - check this box if it is not possible to have unique public source IP addresses for all egress Tunhub TunHub connections in your organization. This will assign a dedicated port out of 30000-40000 range (ensure that your firewall allows egress for this range). Otherwise, Tunhub TunHub listens on port 443 and expects the connection to be established from a unique public IP address.

...

5. Review the integration details. The yellow light in 'Primary Channel' means that TunHub is waiting for the local collector proxy (Breeze) to connect. 

Configure Routes

Tunhub TunHub integration should have at least one route configured. A route is an entity that maps a private address in your network to the one which is reachable by Cloudaware. The route generates an alternate address which customers may use for adding integrations that require secure connection.

...

4. Once the route is pre-configured and ready, get the generated Destination Host and Destination Port required for adding the integration in question.

5. Go back to 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.

...