Deploying the NetBeez BeezKeeper Server on Your Own AWS Infrastructure

Hello everyone!

We’ve put together a guide to help you deploy a NetBeez server instance on your own AWS infrastructure. Just follow the steps below:

Step 1: Launch an AWS instance

  1. Create a new Ubuntu 20.04 EC2 instance with the size recommended in the table at the end of this post.
  2. For instance size, minimum requirements are 2 vCPU and 4GB of RAM. Refer to the table at the end and consult the NetBeez team to choose the instance type based on your installation size. We recommend the m5 type.
  3. Do not allow AWS to assign a public IP address upon launching the instance. Instead, assign an EIP (Elastic IP) after it’s launched to avoid changes in public IP address upon rebooting.
  4. Make sure you have enough disk space to store your historical data (refer to the table below).
  5. Set up a security group for your NetBeez instance using the recommended Firewall Rules:
  6. SSH into your new instance and execute the command provided by the NetBeez team (request it from support [at] netbeez [dot] net if you haven’t received it). The command will resemble:
curl -H "Authorization: Bearer XXXXXXXX_secret_key_XXXXXXXX" -H "Content-Type: text/plain" | sudo bash

Step 2: Request SSL certificates from your CA

  1. Follow this guide to generate your HTTPS certificates.
  2. Contact the NetBeez support team to schedule certificate installation.

Step 3: Activate your NetBeez installation

  1. Complete the first run wizard to activate your dashboard.

AWS Instance Types Based on Number of Agents

The suggestions below are based on the number of agents managed by the dashboard (assuming a maximum of 50 tests per agent). Instance requirements may change depending on the number of tests running, type, and interval.

Number of Agents Instance Size CPU RAM HDD
0 - 10 m5.large 2 8 200GB
11 - 60 m5.xlarge 4 16 200GB
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

If you need any help or have questions, feel free to ask in this thread!

1 Like

Here are the firewall rules that need to be configured to enable installation and software updates:

Also, @panickos worth mentioning that this procedure is the same for other clouds, and not really specific to AWS (outside the instance names/sizes).

Thanks @stefano. I have updated the article with the provided link.

1 Like

When deploying a server, make sure to also update the default docker subnet configuration to avoid conflicts with commonly used RFC1918 subnets. Here’s the procedure to follow:

@panickos what if the server has to be deployed on-premises via OVA?

The same procedure should apply in regards to the BeezKeeper installation, but the user should make sure to configure the right network settings such as IP address, gateway and DNS servers.

Thanks! Sharing there the Ubuntu repository for OVA images: