Using an HTTPS proxy for outgoing ALEE and AEJD traffic from your tethered node

Edit online

This is an optional step in the process of tethering your IBM Aspera HSTS node to your AoC organization. To use an HTTPS proxy for outgoing ALEE (Aspera License and Entitlement Engine) traffic between your tethered node and Aspera on Cloud (optional), you must add options to the JVM_OPTIONS assignment.

Go to the HSTS Admin Guide for your platform and release, then search for the topic "Aspera Entitlement Service (ALEE) Configuration for Use with an HTTP Web Proxy". For a Linux server, see also the IBM Support article "How to make ALEE on Linux connect via forward HTTPS proxy"; this article includes troubleshooting and implementation details that may be useful for any server platform.

This is step 3 in tethering a node

Before you begin step 3, be sure you have completed step 2: Firewall requirements for tethered nodes.

ssl certs firewall HTTPs proxy configure node nginx transfer user optional for HA cluster add node mark remote storage alee and aejd backup and restore
Note: Transfer volume through your own tethered, bandwidth-based, licensed Aspera HSTS node is not metered or charged in your AoC subscription.

Set environment variables

To use an HTTPS proxy for outgoing AEJD (Aspera Event Journaling Daemon) traffic between your tethered node and Aspera on Cloud (optional), you must set environment variables. On a Linux server, go to /usr/lib/systemd/system/asperaejd.service and set environment variables like in a regular systemd service, as follows:

[Unit]
Description=IBM Aspera Event Journal Daemon
ConditionPathExists=/opt/aspera/sbin/aejd
 
[Service]
Environment="AEJD_LOG_FILE=/opt/aspera/var/log/aejd/aejd.log"
Environment="HTTPS_PROXY=proxy_host:proxy_port"
Type=simple
User=asperadaemon
Group=aspadmins
PIDFile=/opt/aspera/var/run/aspera/aejd.pid
ExecStart=/opt/aspera/sbin/aejd
ExecReload=/bin/kill -HUP $MAINPID
TimeoutStopSec=20
KillMode=process
Restart=on-failure

Next step in tethering a node

You've completed the HTTPS proxy configuration for your tethered node. For step 4 in tethering the HSTS node to your AoC organization, go to Configure your transfer server as a tethered node.