Getting started: connect to sites

The first setup task is to connect your site to the Agilicus cloud. This is done with a connector: software that runs at your site and reaches out to the cloud over an outbound-only connection, so your resources are exposed without opening any inbound ports.

What this task is for

Before anything else, the platform needs a way to reach your resources. The connector is that way. It is the physical and logical link between your network and the Agilicus cloud, and every resource you expose later is reached through a connector.

When you need it

Always. You need at least one connector to expose any resource.
You do not need a connector if you have nothing to expose (for example, you only manage identity and users). The guide accounts for both cases.

How to do it

Open Getting Started > Connect to Sites from the left navigation.
Answer the question Do you have resources that need to be exposed?

I have resources that need to be exposed. The guide recommends creating an Agilicus Connector and shows you the steps.
I do not have resources that need to be exposed. No action required; proceed to the next task.

If you need a connector, open Resources > Connectors > New and follow the connector creation wizard. The wizard asks for a name and then gives you the installation instructions for the platform you will run the connector on (container, Linux, router, Windows, and so on).
Install the connector on your chosen device and let it sign in to the platform.
Return to the task board and mark Connect to Sites complete.

After you finish

You now have a connector shown in Resources > Connectors > Overview. Its status should be healthy. You can now move on to Identify users.

Configuration versus diagnostics

Configuration: creating the connector and installing it (see Connectors).
Diagnostics: checking the connector’s health and diagnostic counters in the connector overview (see Connector diagnostic counters).

Troubleshooting

The connector does not appear in the overview: confirm the installation completed and that the device can reach the Agilicus cloud over HTTPS outbound.
The connector shows as unhealthy: check its diagnostic counters, network path, and that the device clock is synchronised.
Firewalls: the connector needs outbound HTTPS to the Agilicus cloud; no inbound rules are required. See Site firewall configuration.