1 of 20
2 of 20
3 of 20
4 of 20
5 of 20
6 of 20
7 of 20
8 of 20
9 of 20
10 of 20
11 of 20
12 of 20
13 of 20
14 of 20
15 of 20
16 of 20
17 of 20
18 of 20
19 of 20
20 of 20




success stories

Edge Node

Edit on GitHub

Azion Edge Node enables you to create your own edge infrastructure, allowing you to install services and resources in real time.

It is an open software which can be run on different types of microprocessor architecture: x86 and ARM, and different sizes of equipment, including Raspberry PI, network equipment such as network switches and SD-WAN routers as well as corporate servers.

  1. Installing
  2. Viewing your nodes
  3. Authorizing
  4. Services
  5. Agent commands and options
  6. Watcher
  7. Supporting documentation

1. Installing

Edge Node is installed in 3 stages:

  1. Generate a credential to run the actions;

    To generate the credential required to authenticate your edge nodes, follow the steps in the credentials documentation.

  2. Install the Edge Orchestrator agent on the devices;
  3. Authenticate the device after installation.

To begin the Edge Node installation process, you must download the Edge Orchestrator installation binary of your choice.

Note: The commands executed in the edge-orchestrator agent, must be executed with root user privileges.

The root user is the one who has unrestricted access to all system components, whether files or processes. If you do not have these privileges you may experience installation failures when attempting to manage some operating system requirements that demand such privileges.

Check the list of compatible platforms for Azion Edge Node and download the one of your preference:

Operating System Architecture File
FreeBSD x86_64 edge-orchestrator
FreeBSD ARM64 edge-orchestrator
Linux x86_32 edge-orchestrator
Linux x86_64 edge-orchestrator
Linux ARM32 edge-orchestrator
Linux ARM64 edge-orchestrator
MacOS x86_64 edge-orchestrator

Alternatively, you can download it using the Command line. In the example, the download link refers to the Linux/x86_64 agent. If you want to download another version, just change the url for the required operating system or architecture:

curl -O http://downloads.azion.com/linux/x86_64/edge-orchestrator

After downloading, you must follow the steps below, in order to install the Edge Orchestrator agent to your device:

  1. Install the Edge Orchestrator agent:
    chmod +x edge-orchestrator
    ./edge-orchestrator install
  2. Enter the token for the Edge Orchestrator agent;
  3. Confirm the next steps;
  4. Start the Edge Orchestrator agent after installing it:
    edge-orchestrator start
    Note: If your operating system does not have a service manager (systemd, for example), you must run it in the foreground.
    edge-orchestrator start --foreground

    The logs to run the Edge Orchestrator agent are stored in:

2. Viewing your nodes

Whenever the installation code is run for any device and it has been authenticated by the Token, the edge nodes will be listed in Real-Time Manager.

To view the list of edge nodes created for your account, follow the steps below:

  1. Go to Real-Time Manager;
  2. Open the Edge Orchestration item on the top left menu and select the Edge Node page;

You can verify the listed items by checking the HashId column, as it contains the hash used to create and authenticate the edge node.

3. Authorizing

You must authorize your edge nodes to begin orchestrating them. To authorize an edge node, follow the steps below:

  1. Open the list of Edge Nodes in Real-Time Manager;
  2. Click on the icon (key) and accept the confirmation window.

After the authorization, the Edge Node can take up to 10 seconds before services can be orchestrated.

You can also authorize all the edge nodes you want at once. To start using this option, follow the steps below:

  1. Open the list of Edge Nodes in Real-Time Manager;
  2. Select the items you want to authorize or, if you prefer, select all items by checking the first check box on the left;
  3. On the top right corner, click the Actions button and select Authorize;
  4. A message to confirm your action will be shown, click the Confirm button to save your selection;
  5. You will see the following confirmation message: “X nodes were successfully authorized!

4. Services

You can provision the services registered in your library by following steps:

  1. Open the list of Edge Nodes in Real-Time Manager;
  2. Select the Edge Node that you want to configure;
  3. Open the Services tab and click the Add Service button;
  4. Link it to the service you want and, if necessary, you can configure the variables required by the service.

Services that are due to be orchestrated via Edge Node, must be registered in Edge Libraries > Edge Services and marked as active.

Once the service is provided, Edge Node can begin orchestrating it based on resource priorities. You can monitor the service installation process via logs in the Edge Orchestrator agent.

The service installation logs are stored in

5. Agent commands and options

The Edge Orchestrator agent has additional commands and options to make it easier to use.

–debug or -d It sets the agent logs to debug mode.
–help or -h It helps on the commands that the agent can execute.
install It installs the agent to the client’s device, copies the binary to the installation location; adds the Edge Orchestrator agent to the device’s service manager (if any) and; sets up credentials to authenticate the Edge Node.
start [–foreground] It initializes the Edge Orchestrator agent through the device’s service manager.
Note: The foreground option is used to run it in the foreground.
start -g OR –join-group By using these flags followed by a comma separated list of group names, you can enroll your edge-node with the specified group(s) through commandline while starting your node for the first time.
Example: sudo edge-orchestrator start -g GROUP1,GROUP2,GROUP3 –foreground
start [-n OR –set-name] By using these flags followed by the desired name, you can specify your new node’s name through commandline while starting your node for the first time . By not using them, the hostname is used as default value.
Example: sudo edge-orchestrator start -n Edgenodename –foreground
status It reports on the status of the execution of the Edge Orchestrator agent.
stop It stops the Edge Orchestrator agent through the device’s service manager.
uninstall It uninstalls the agent from the client’s device, removes the binary from the installation location; removes the Edge Orchestrator agent from the device’s service manager (if any).
Note: authentication credentials remain on the device and can be removed using the Azion control panel.
–version or -v It displays the installed version of the agent.

6. Watcher

To avoid any configuration changes to the resources managed by Orchestrator, the agent provides a feature called Watcher.

It is a non-manageable feature of our agent that restores any tampered file, that is, it consists of a group of workers that periodically scan all provisioned files looking for any drift – modification or removal – based on the last applied manifest, restoring the desired state, if necessary.

You can verify any action made by Watcher by looking at the logfile /var/log/azion/edge-orchestrator.log.


# /var/log/azion/edge-orchestrator.log
{"level":"info","time":"2021-09-22T17:31:16Z","message":"finished applying resources for version 3128"}
{"level":"info","time":"2021-09-22T17:31:16Z","message":"apply manifest 3128 finished"}
{"level":"info","time":"2021-09-22T17:31:16Z","message":"watcher: started with period of 60 seconds using 5 workers"}
{"level":"info","time":"2021-09-22T17:32:16Z","message":"watcher: dispatching workers"}
{"level":"info","time":"2021-09-22T17:32:16Z","message":"watcher: dispatched 5 workers"}
{"level":"info","time":"2021-09-22T17:32:16Z","message":"watcher: workers finished"}
{"level":"info","time":"2021-09-22T17:32:16Z","message":"watcher: checked 19576 artifacts, 0 drifted from manifest."}

7. Supporting documentation

Didn’t find what you were looking for? Open a support ticket.