Update the Agent’s Address Configuration¶
Alation Cloud Service Applies to Alation Cloud Service instances of Alation
You may need to update the Agent’s address configuration if the Agent is in a disconnected status. This may happen if the Agent was set up incorrectly or if you’re an Alation Cloud Service customer who’s been upgraded to the cloud native architecture (available starting in 2022.4).
To update the Agent’s address configuration:
Look up the Alation Cloud Service connectivity endpoint for your region in the following table.
Geography
Location
Agent Connectivity Endpoint
Africa, Europe, & Middle East
Frankfurt
ocf.euc1.eu.alationcloud.com
Dublin
ocf.euw1.eu.alationcloud.com
Americas
Montreal
ocf.cac1.ca.alationcloud.com
Virginia
ocf.use1.alationcloud.com
Oregon
ocf.usw2.alationcloud.com
Asia Pacific
Singapore
ocf.apse1.ap.alationcloud.com
Sydney
ocf.apse2.ap.alationcloud.com
Tokyo
ocf.apne1.ap.alationcloud.com
If your organization uses a Web Application Firewall (WAF), inform your firewall admin to allow the Alation Cloud Service connectivity endpoint to pass through.
The Agent configuration file is located on the Agent host machine at /etc/hydra/hydra.toml. Edit the file using your preferred text editor. You may need to use sudo privileges.
In hydra.toml, look for the
address
line. Replace the address value inside the quotation marks with the Alation Cloud Service connectivity endpoint you obtained earlier. If the address is already correct, you don’t need to do anything else.Restart the agent by running the following command:
sudo hydra restart
In Alation, return to the Agents Dashboard and verify that the Agent is now connected to Alation.