Deploy EDGE on Exoscale
This section guides you through the steps to get the Anapaya EDGE Appliance from the Exoscale Marketplace up and running.
Prerequisites
Before you can start, you need to have an Exoscale account. If you do not have one yet, create one on Exoscale. You also need to have a SCION access into the Exoscale cloud. If you do not have one yet, contact the Anapaya support team for further information.
Installation
The Anapaya EDGE appliance is available on the Exoscale marketplace.
Start an Anapaya EDGE VM using one of the recommended instance types. It is recommended to allocate
at least four CPUs and 4GB of RAM. You can always change the instance type later on if you want to
improve performance. By default you can use anapaya as the username for SSH public key based
authentication.
Network configuration
It is recommended to launch the appliance with at least two subnets. One subnet is used for the management interface and can have Internet access. The other subnet is used for the SCION interface towards the SCION network; the IP addressing details of this subnet are provided by your SCION access provider. Ideally, you should also have a third subnet to connect the EDGE appliance to your applications.
Security group configuration
If you want to access the appliance from the Internet via SSH, you need to configure the security
group to allow incoming SSH connections. The appliance uses port 22 for SSH.
Connecting to the appliance
Once the VM is started, you can connect to it via SSH using the anapaya user. If you configured
SSH keys via cloud-init, use your private key for authentication. Otherwise, use the default
credentials (username: anapaya, password: anapaya) for the initial login.
Configuration
After connecting to the appliance, configure it by following the steps in Setup.
The appliance is configured to use DHCP on initial launch. When you start changing the appliance
configuration, you should first configure the interfaces section with the values for the
management interface that were potentially assigned during VM boot via DHCP. Otherwise, you might
lose connectivity to the appliance.
Relevant values include the IP address and routing information.
Cloud-Init
The appliance supports cloud-init for additional customization during initial launch. Refer to the Cloud-init guide for details and examples.
NAT configuration
In some scenarios you might need to configure NAT on the appliance; for more details, refer to the NAT section in the general configuration guide. For example, you may need NAT when a service must be exposed on a public IP to the SCION network but is running on a private IP.
Redundancy
To achieve redundancy, you can deploy two appliances in different availability zones and configure them as a cluster. Refer to Cluster for more details.