From 1d936b4e12493a52cbfb993aefc2ad48cd46212e Mon Sep 17 00:00:00 2001 From: James Carppe Date: Mon, 18 Dec 2023 01:32:23 +0000 Subject: [PATCH] GITBOOK-74: Corrected order of Edge key components --- advanced/edge-agent.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/advanced/edge-agent.md b/advanced/edge-agent.md index 94c8430a..820a3d1e 100644 --- a/advanced/edge-agent.md +++ b/advanced/edge-agent.md @@ -24,8 +24,8 @@ During the creation process, an Edge ID is dynamically generated. This is a rand * The Portainer instance API URL. This is how the Edge Agent knows how to ‘call home’ to your Portainer instance. * The Portainer instance reverse tunnel server address. This is identical to the API URL (unless [changed during deployment](../admin/environments/add/docker/edge.md#deploying) or in [Edge Compute settings](../admin/settings/edge.md#edge-compute-settings)) but with the tunnel server port (`8000` is the default). -* The environment identifier key (endpoint ID). * The Portainer instance reverse-tunnel server fingerprint (prevents MITM when creating a tunnel). +* The environment identifier key (endpoint / environment ID). Use the command syntax to deploy an Edge Agent across your remote node or remote swarm cluster.