Keywords: SonarQube - AWS - Technical issue - Secure Connections (SSL/HTTPS)
bnsupport ID: 27c4aad1-4699-f297-2022-c3b84dab6b2b
I have spun up an EC2 instance with sonarqube running on it from the bitnami AMI available in the AWS marketplace. EC2 is in a private subnet behind a load balancer which routes requests from the domain (sonarqube.'domain'.com). Even though the documents mentioned bitnami stacks are HTTPS backed and enabled, right now, when I hit the domain, the connection is not secure (HTTP).
I am following this document (https://docs.bitnami.com/general/how-to/understand-bncert/) to enable HTTPS but I am getting error "Warning: The domain 'sonarqube.domain.com' resolves to a different IP address
than the one detected for this machine, which is 'xx.xx.xx.xx'. Please fix
its DNS entries or remove it. For more info see:
I will not have a public IP for my host as it's in the private subnet. Can you recommend other ways to enable HTTPS for my sonar instance?