Grafana talks back to 34.120.177.193 even though analytics are disabled

We configured grafana to not talk back to 34.120.177.193 for telemetry / update checks by following the docs at Configure Grafana | Grafana documentation

and setting this in our grafana.ini

[analytics]
enabled=false
check_for_updates=false
check_for_plugin_updates=false
reporting_enabled=false
feedback_links_enabled=false

We are using grafana OSS within the official docker image grafana/grafana:11.2.0

Still, when restarting Grafana, we have several connections to 34.120.177.193.443. We are running this in secured environments where we are not allowed to connect to the outer world and sec-ops complain about the actual attempts.

Could you explain how we could disable those connections? Thank you

Hint: Even though i’am aware of Understanding grafana outgoing connection (firewall configuration), it does not help in our case (we followed the steps described there) - we still see those connections.

Work with your sec-ops - enable deep inspection and find which URL and payload is generated in those requests.

Guess (so don’t blame me): something like cert requests for license/plugin signature validation