Automation Remote
Remote Targets
Automation Remote enables workflows to communicate with resources in your private network that do not have direct internet access. Deploy an Automation Remote as an OVA or with Docker Compose, then assign it to a target that your workflows use.
Use Cases
Remote Targets can be used in many instances where a device you need to access is not available from the public internet. This keeps your devices safely behind internal network protections and also available as targets for Automation workflows. For example:
- User-Deployed ISE deployments - You can use the Remote Targets to relay API calls to the ISE deployment on the local network. This is useful for tasks such as using a workflow activity to quarantine a device.
- User-Deployed Secure Firewall Management Center deployments - You can use the Remote Targets to relay API calls from the Automation cloud so that workflow activities can run on the local Secure Firewall Management Center.
- User-Deployed terminal or Unix/Linux systems - You can use the Remote Targets to automate shell/terminal commands to a specific identified host within your network.
Requirements
Newly generated and regenerated configuration packages require Remote Appliance version 3.0 or later. Existing connected Remotes continue to run. Before you regenerate a package for an older appliance, upgrade the appliance first. Regenerating a package for an older appliance invalidates its current connection and the regenerated package will not work with that appliance.
The following minimum requirements apply to an OVA deployment:
- VMware ESXi version 5.5 or newer
- 2 vCPU
- 2 GB RAM
- 30 GB Disk
For a Docker Compose deployment, use a Linux x86_64 (AMD64) host with Docker installed and running. Run docker info to verify that Docker is available. Registration commands require root access or an account that can use sudo.
Network requirements for Remote Appliance 3.0 and later
Note: Remote Appliance version 3.0 and later requires outbound TCP connectivity on port 5671 to the endpoint for its region.
| Region | Endpoint |
|---|---|
| North America (NAM) | us-remote-v3.workflows.meraki.com |
| Europe (EU) | eu-remote-v3.workflows.meraki.com |
| Asia Pacific and Japan (APJC) | ap-remote-v3.workflows.meraki.com |
| Canada (CA) | ca-remote-v3.workflows.meraki.com |
| India (IN) | in-remote-v3.workflows.meraki.com |
Allowlist the fully qualified domain name (FQDN), rather than an IP address. The resolved addresses can change.
Legacy Remote Appliance network requirements
Note: Setting up the Remote Targets virtual appliance requires advanced understanding of how to create and manage resources in VMware. If you encounter issues within the vSphere client, contact an administrator in your organization or VMware support.
Legacy Remote Appliances require outbound TCPS connectivity on port 8883 to the endpoint for their region.
-
Region Endpoint North America (NAM) us-remote.workflows.meraki.comEurope (EU) eu-remote.workflows.meraki.comAsia Pacific and Japan (APJC) ap-remote.workflows.meraki.comCanada (CA) ca-remote.workflows.meraki.comIndia (IN) in-remote.workflows.meraki.com
Note: To verify an IP address in the following table, we recommend that you perform an nslookup on the URLs before adding an IP address to your security configuration.
| Region | Source IP Addresses |
|---|---|
| North America (NAM) | 54.185.226.187 52.42.125.47 35.161.183.166 |
| EU | 52.28.26.113 18.194.76.180 3.66.114.23 |
| APJC | 47.128.203.165 13.213.217.40 47.130.160.32 |
| Canada (CA) | 16.52.55.114 16.54.18.112 15.157.217.244 |
| India (IN) | 13.206.14.125 52.66.20.206 3.7.111.65 |
Setup
To set up Remote Targets, see the Remote Setup and Deployment Help topic.
By default, certificates in K3s expire after 12 months. So when the certificate expires on the Remote Targets, the Remote devices will be disconnected from it. You'll need to set up a new replacement virtual appliance for the Remote devices to connect to. Here are the summary steps:
- Shut down the previously installed virtual appliance and delete it to free up network resources such as the IP address.
- In Automation, go to the disconnected Remote and choose the Revoke action to void the existing connection details, which changes the status to Revoked.
- If the appliance is older than version 3.0, upgrade it before regenerating the package.
- Refresh the page, and choose the Regenerate action to download a new configuration file.
- Choose the package that matches your deployment: Remote appliance OVA or Docker Compose package (Linux amd64).
- Follow the appropriate OVA or Docker Compose deployment procedure in the Remote Setup and Deployment Help topic.
- In Automation, verify that the status of the Remote is now connected.
Note: On May 31, 2025, Ubuntu 20.04 LTS will reach the end of its standard five-year support window. Your existing Remote configuration will continue to work. However, we recommend that you redeploy your Remote Targets by completing the steps above with our most recent OVA to maintain support using the newer Ubuntu 24.04 LTS.