How Do We Deploy The Edgescan Jumpbox?
There are multiple ways to deploy them dependent on the environment you are using. We've categorized the most common deployments and their steps in the below.
Version Number: v1.0.0
Published Date: 13 Mar 2026
____________________________________________________________________________
Introduction
Welcome to the Jumpbox Starter Guide. This document provides quick-start instructions for deploying your Jumpbox virtual machine in the two most common environments:
-
VMware ESXi – using a provided OVA file
-
Amazon EC2 – using a pre-configured AMI image
These instructions cover the essential steps to get your Jumpbox up and running. For more advanced configuration options, networking requirements, or troubleshooting, please refer to the official documentation linked within each section.
Bespoke deployments
We found that some organisations are not able to deploy a Jumpbox into their private/internal/cloud networks. To help get the deployment smoothly implemented, we offer custom built OVAs or configuration of your golden images.
This allows your Jumpbox to be compliant per your corporate guidelines, and allows you to install technology such as host based firewalls or monitoring solutions so you can configure access and ensure the device remains compliant throughout your Edgescan licences.
If you need to deploy a Jumpbox to a different cloud provider or hypervisor, please contact Edgescan Support at shout@edgescan.com, and we will assist you with your specific deployment requirements.
Before You Begin
To function correctly, your Jumpbox must be able to establish an outbound connection to the Edgescan platform. You will be provided with a public IP address that the Jumpbox needs to reach on port 9801 (TCP). The Jumpbox operating system is already configured to initiate this connection - you simply need to ensure that your network or cloud environment permits this outbound traffic.
Keep the provided IP address handy, as you will need it when configuring firewall or security group rules during deployment.