Changed endpoint for domain whitelist?

[christophernruud (Chris Aurora Neumann Ruud)]

Refering this one:

Domains / URLs / internet resources that SonarCloud requires access to

Hi, We have been running SonarCloud as part of our CI/CD for a while now. Our pipeline is realized using github actions, running on Azure VMs added to our github org as self-hosted github runners. SonarCloud is invoked as part of the maven build step using the sonar-maven-plugin. The VMs acting as build servers have a strict firewall for outgoing traffic and recently two new domains have popped up in the firewall blocked traffic log: ea6ne4j2sb.execute-api.eu-central-1.amazonaws.com sc-clean…

In our build logs we get a warning:

[WARNING] 08:33:30.897 Failed to publish the sensor cache

In our firewall logs since 2024-07-11, we have noticed that sonar seems to call

http://analysis-sensorcache-eu-central-1-prod.s3.amazonaws.com:443

Which we suspect is a changed endpoint for sonarcloud sensor cache, but

Organizations advanced administration & SonarCloud

does not reference this endpoint so we are reluctant to open traffic to this unless we are certain that it is sonarcloud that initiates this traffic.

[kevin.hinz]

@christophernruud

does not reference this endpoint so we are reluctant to open traffic to this unless we are certain that it is sonarcloud that initiates this traffic.

Hi @christophernruud, I verified with the Engineers that this is in fact a valid URL to white list.

The documentation has been updated. One address was added (the one you called out) and two others were removed (because they are no longer relevant).

Thanks for bringing attention to this topic!