[REL-961] Close Grafana port from outside access #1204
Merged
+1
−4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
REL-961 Review Docker Compose file for Grafana port exposure security
Is there any particular reason why we have the Grafana port 3370 open for side channel access? It seems like it's been open since Grafana was first bundled with the product in 51ca079, even though the reverse proxy was implemented at about the same time, in https://github.com/sourcegraph/sourcegraph/commit/939b612fb319f6563116f4bcd5814dc486f78361
I suggest we close the side channel access, to reduce exposure for customers running the Airgapped Analytics dashboard.
Also, fixed a broken port number in sourcegraph-frontend-internal's config for the Grafana URL, which has been broken since f6f8d8d, so probably not used.
Checklist
Test plan
Tested on test instance, frontend still proxies the connection to Grafana as needed, without side channel access