SonarQube DR Setup

  • which versions are you using (SonarQube, Scanner, Plugin, and any relevant extension)
    SonarQube - Enterprise Edition Version 9.9.2 (build 77730)
  • how is SonarQube deployed: zip, Docker, Helm
    Docker, Sonar deployed in AWS cloud
  • what are you trying to achieve
    I am trying to configure Sonar DR which is running in AWS
  • what have you tried so far to achieve this
    Yes, I am using AWS Elastic Disaster Recovery to configure Sonar DR where it is provisioning new instance from the source server. So the new Sonar application ( which is replicated from the snapshot for DR ) server ID changed and it is not provisioning with the existing server ID. Since the server ID changes for every new machine provisioning in the DR activity. Since the Sonar License is based on the Server ID. We couldn’t use the application with License. Could you please assist on this.


Do not share screenshots of logs – share the text itself (bonus points for being well-formatted)!

Hey there.

In SonarQube v9.9.3, we added the possibilty of a 7-day grace period when the Server ID is regenerated, like in DR scenarios.

When your license is invalidated due to a change of server ID, you can exceptionally extend it to benefit from a grace period of seven days. After this period, the license will remain not valid. Note that you can only do this once.

I suggest upgrading to v9.9.4 so you can take advantage of this possibility.

Here are the docs on requesting a new license.

Hello Colin,

Thanks for the updates on licensing.

But the testing was creating the new instance from the existing server where it should not ask for a new license ( Server ID should not change )
So please recommend the server ID of the server should not get changed while creating the new instance through AWS DRS


Have you reviewed the actions that can invalidate a license key (meaning the Server ID gets regenerated)?