SonarQube Community Edition with PostGreSQL
SonarQube is an automated code scanning tool that can be integrated with CI/CD pipeline to detect security vulnerabilities and defects in the application code. It can integrate with your existing workflow to enable continuous code inspection across your project branches and pull requests. The single node SonarQube AMI by Kurian has pre-configured the community edition of SonarQube with PostgreSQL as the backend database. When an EC2 instance is spun up from this AMI the SonarQube service would be up and running on that machine for your immediate use.
AMI built with the latest, stable version of the community edition of SonarQube.
AMI compatible for spinning up nodes to run SonarQube on a single node with PostgreSQL as the backend database.
AMI is built on a patched operating system and the node created from this is ready to be deployed in production.
How It Works
When an EC2 node spun up from this AMI, the SonarQube service is up and running on port 9000.
SSH into the newly spun up node if you need to perform any additional configuration.
Click on the links below to take you to Amazon Marketplace for spinning up EC2 nodes.
- SonarQube Community Edition for CentOS 7
- SonarQube Community Edition for CentOS 8
- SonarQube Community Edition for Red Hat Enterprise Linux 7
- SonarQube Community Edition for Red Hat Enterprise Linux 8
- SonarQube Community Edition for Debian10
- SonarQube Community Edition for SUSE Linux 12
- SonarQube Community Edition for SUSE Linux 15
- SonarQube Community Edition for Ubuntu 16.04
- SonarQube Community Edition Ubuntu 18.04
- SonarQube Community Edition Ubuntu 20.04
When an EC2 node spun up from this AMI, the SonarQube service would be available on port 9000.
The service can be accessed using the URL http://EC2-NODE-IP:9000. Login as admin/admin and when you login first time you will be required to change the password.
The service can be managed using standard steps:
$ sudo systemctl [start|stop|status] sonarqube.service
At times due to database connection issues the service might not be fully up. Look at logs under logs directory and adjust connection settings in conf/sonar.properties. The sonarqube.service must be restarted for any change made in sonar.properties file to take effect.
Kurian releases latest, stable versions of open source software on popular Linux distributions. If you need a configuration that is not currently available in marketplace, send us your requirements to email@example.com. Please include the following info in the email:
Name of Software with version numbers that need to be released as AMIs.
Linux distribution and the version.
The EC2 instance type that you plan to spin up using the AMI (optional).
Follow official documentation for the directions for any upgrades.
Maintenance and Troubleshooting
The SonarQube service is sonarqube, and it can be managed using standard options available for a Linux service. See the last section also.
The SonarQube application can be integrated with CI/CD pipeline and maintained following the official documentation.
Kurian can help with configuring the application for your specific needs using this AMI. Contact us with details to firstname.lastname@example.org
Remote Access to EC2 Node
Following are the standard AWS defined users available for SSH when a node is provisioned:
Amazon Linux: ec2-user
Red Hat Linux: ec2-user
SuSE Linux: ec2-user
Debian Linux: admin