# Deploying the NetBeez BeezKeeper Server on Your Own AWS Infrastructure **URL:** \ **Category:** Deploy & Configure\ **Tags:** deployment, server, on-prem, aws\ **Created:** [April 12, 2023, 5:56pm UTC](https://community.netbeez.net/t/deploying-the-netbeez-beezkeeper-server-on-your-own-aws-infrastructure/55 "2023-04-12T17:56:46Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![panickos](https://yyz1.discourse-cdn.com/flex031/user_avatar/community.netbeez.net/panickos/32/8_2.png) [@panickos](https://community.netbeez.net/u/panickos)\ **Post date:** [April 12, 2023, 5:56pm UTC](https://community.netbeez.net/t/deploying-the-netbeez-beezkeeper-server-on-your-own-aws-infrastructure/55/1 "2023-04-12T17:56:46Z")
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](https://netbeez.zendesk.com/hc/en-us/articles/8393384064269-Network-firewall-settings): 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: ```auto 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** 1. Follow [this guide](https://netbeez.zendesk.com/hc/en-us/articles/360022798412-Update-HTTPS-Certificates-on-a-Server) 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! ---
**Author:** ![stefano](https://avatars.discourse-cdn.com/v4/letter/s/aca169/32.png) [@stefano](https://community.netbeez.net/u/stefano)\ **Post date:** [April 19, 2023, 7:11pm UTC](https://community.netbeez.net/t/deploying-the-netbeez-beezkeeper-server-on-your-own-aws-infrastructure/55/2 "2023-04-19T19:11:39Z")
Here are the firewall rules that need to be configured to enable installation and software updates: > **[Network firewall settings](https://netbeez.zendesk.com/hc/en-us/articles/8393384064269-Network-firewall-settings)** > > Overview > This document describes the network connections required between the NetBeez agents, the dashboard/server, and other external resources such as software repositories to download the latest... Also, @panickos worth mentioning that this procedure is the same for other clouds, and not really specific to AWS (outside the instance names/sizes). ---
**Author:** ![panickos](https://yyz1.discourse-cdn.com/flex031/user_avatar/community.netbeez.net/panickos/32/8_2.png) [@panickos](https://community.netbeez.net/u/panickos)\ **Post date:** [April 19, 2023, 7:33pm UTC](https://community.netbeez.net/t/deploying-the-netbeez-beezkeeper-server-on-your-own-aws-infrastructure/55/3 "2023-04-19T19:33:12Z")
Thanks @stefano. I have updated the article with the provided link. ---
**Author:** ![stefano](https://avatars.discourse-cdn.com/v4/letter/s/aca169/32.png) [@stefano](https://community.netbeez.net/u/stefano)\ **Post date:** [April 21, 2023, 4:50pm UTC](https://community.netbeez.net/t/deploying-the-netbeez-beezkeeper-server-on-your-own-aws-infrastructure/55/4 "2023-04-21T16:50:25Z")
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: > [@Update the Docker subnet configurations](https://community.netbeez.net/t/update-the-docker-subnet-configurations/57): > > This procedure for on-prem/self-hosted server installations shows how to update the default configuration settings for Docker’s subnets (172.17.0.0/16). This is recommended since, by default, Docker uses commonly used RFC 1918 subnets that may cause conflicts with agents deployed in networks with the same address space. Step 1: Update the following file: /etc/docker/daemon.json Add the following into this file (if it doesn’t exist then create it): { "bip":"198.18.252.130/28", "fixed-ci… ---
**Author:** ![stefano](https://avatars.discourse-cdn.com/v4/letter/s/aca169/32.png) [@stefano](https://community.netbeez.net/u/stefano)\ **Post date:** [June 26, 2023, 7:30pm UTC](https://community.netbeez.net/t/deploying-the-netbeez-beezkeeper-server-on-your-own-aws-infrastructure/55/5 "2023-06-26T19:30:53Z")
@panickos what if the server has to be deployed on-premises via OVA? ---
**Author:** ![panickos](https://yyz1.discourse-cdn.com/flex031/user_avatar/community.netbeez.net/panickos/32/8_2.png) [@panickos](https://community.netbeez.net/u/panickos)\ **Post date:** [June 28, 2023, 1:59pm UTC](https://community.netbeez.net/t/deploying-the-netbeez-beezkeeper-server-on-your-own-aws-infrastructure/55/6 "2023-06-28T13:59:02Z")
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. ---
**Author:** ![stefano](https://avatars.discourse-cdn.com/v4/letter/s/aca169/32.png) [@stefano](https://community.netbeez.net/u/stefano)\ **Post date:** [June 28, 2023, 4:29pm UTC](https://community.netbeez.net/t/deploying-the-netbeez-beezkeeper-server-on-your-own-aws-infrastructure/55/7 "2023-06-28T16:29:27Z")
Thanks! Sharing there the Ubuntu repository for OVA images: [https://cloud-images.ubuntu.com/focal/current/](https://cloud-images.ubuntu.com/focal/current/)