Sonarqube enterprise edition setup

Hi Team, I am trying to install SonarQube enterprise edition in Ubuntu. as per document guide, need to install postgresql and Sonarqube. I am going to spin up azure managed postgresql in azure and same as azure managed Ubuntu machine for SonarQube installation. I have some questions, Can you please help me to understand.

  1. Do we need new subnet for postgresql and Sonarqube ubuntu server? or can we use existing subnet to spin up these resource?

  2. What will be the CPU size recommended for postgresql in azure
    Example sizes
    DS2_v2: 2 CPU, 7 GB
    DS3_v2: 4 CPU, 14 GB

  3. Which version of Ubuntu server version I can consider and can I consider D8s_v3 VM Size with 8 vCPU and 32 GiB RAM for Sonarqube installation.

4)What all are the inbound ports we need to allow when creating Ubuntu server in azure for Sonarqube installation.

  1. As per the installation document guide Installing SonarQube from the ZIP file, Do we need to download this zip file and move from local machine to Azure managed Ubuntu server and can be executed the script on bin/linux-x86-64/ start right?

  2. Apart from Installing PostgreSQL and Sonarqube any other installation needed?

  3. Do we need PostgreSQL server and Ubuntu server in the same subnet?

I have tried to get all these details from installation and setup guide, but couldn’t able to find the details.

Please help me to understand and install Sonarqube with Azure managed servers.


Hi @suresh1256644,

Welcome to SonarSource community! :wave:

I’m not an Azure expert nor a sysadmin so I may not give the best advice. Regardless of what you choose, please ensure you have a test plan in place: record your configurations, test at small scale, monitor, adjust, etc. Eventually, you’ll know better than SonarSource at what’s best for your setup.

Azure would have a better recommendation for you regarding this question. I suggest using a new subnet to as not to crowd the existing subnet with mixed resources and concerns.

Please read our Hardware Recommendations:


We recommend that for large instances, the database used by SonarQube is hosted on a machine which is physically separate from SonarQube Server but close to it on the network.

We don’t give any hard recommendations. You should choose a size that fits your future goal of SonarQube usage. You did not mention how many users or projects/lines-of-code you will have, so I would just go with the smaller one for now. You will need to monitor usage and react accordingly.

Please read our Prerequisites and Overview for more information.

Again, this depends on how big your organization and planned SonarQube usage will be. D8s_v3 VM with 8 vCPU and 32 GiB RAM looks good. See also our recommendations for hardware for our Data Center Edition.

Please download SonarQube and open the /conf/ file. You will see all the different ports needed for each of the components of SonarQube and you can adjust the sonar.web.port (default 9000) and the (default 9001). I would just use the defaults unless you have something running on that port that’s more important than SonarQube.

If the Azure-managed Ubuntu server does not have internet access to download SonarQube, then yes you will have to move it from local machine to the Ubuntu server. bin/linux-x86-64/ start is correct for Linux, as shown in Install the Server: Installing SonarQube from the ZIP file.

No, just follow our documentation and it should be enough.

Typically, you usually don’t install a distributed system across multiple subnets due to possible increased latency between subnets, thus all nodes in the cluster should be installed on the same subnet, if you are using a cluster.

Since you are using Azure to manage your servers and DB, you should not need to be on the same subnet since Azure should handle this high availability. I suggest you verify with Azure help team.


Thanks Joe for your quick response. Let me try and share any issues. Thanks