NetBeez customers can deploy a NetBeez server instance on their own AWS infrastructure. The following procedure explains how to do this.
Step 1: Launch an AWS instance
Spin up a fresh Ubuntu 20.04 EC2 instance sized according to the table at the bottom of this article.
Instance size: Minimum requirements are 2 vCPU and 4GB of RAM. Consult the NetBeez team and the table at the bottom of this article to select the instance type based on your installation size. Here's the list of available AWS instances (m5 type recommended).
IP Address: Don't let AWS assign a public IP address when you launch the instance. You must assign an EIP (Elastic IP) to your instance once it's launched. If you don't do so, your instance will be assigned a new public IP address each time it is rebooted.
Storage: Ensure you have enough disk space to host your historical data (see table).
Security Group: Create a security group for your NetBeez instance that will allow the following rules:
Outbound: All.
Inbound: TCP/22 (SSH), TCP/443 (HTTPS), and TCP/20018 (server-agent communication).
SSH into the newly created instance and run the command sent to you by the NetBeez team (ask support@netbeez.net for the commands if you haven't received them). The command looks like this:
curl -H "Authorization: Bearer XXXXXXXX_secret_key_XXXXXXXX" -H "Content-Type: text/plain" https://ims.netbeez.net/servers/d406cbf4aaa1-server-id-c1f90dce/install | sudo bash
Step 2: Request SSL certificates from your CA
In order to get your HTTPS certificates generated, follow this guide.
Once you have your HTTPS certificates contact our support team to arrange for a time to install them.
Step 3: Activate your NetBeez installation.
Follow the first run wizard to complete the activation of your dashboard.
AWS Instance types based on the number of agents
Below are the suggested instance types based on the number of network agents managed by the dashboard (assuming a maximum of 50 tests per agent). Remote worker agents account for 1/2 a network agent (they can run up to 25 tests per agent). Please keep in mind that instance requirements change based also on the number of tests running, as well as type, and interval.
Number of network agents | Instance size | CPU | RAM | HDD |
0 - 10 | m5.large | 2 | 8 | 200GB |
11 - 60 | m5.xlarge | 4 | 16 | |
61 - 100 | m5.2xlarge | 8 | 32 | 500GB |
101 - 200 | m5.4xlarge | 16 | 64 | 1TB |
201 - 500 | m5.8xlarge | 32 | 128 | 2TB |
501 - 1000 | m5.12xlarge | 48 | 192 | 3TB |
1001 - 2500 | m5.16xlarge | 64 | 256 | 4TB |