Unable to use ECS hosted Grafana behind AWS ALB

kylegordon · June 6, 2018, 9:53am

I couldn’t ask here as it has more than two links, so here’s the Github issue I’m trying to discuss.

Unable to use ECS hosted Grafana behind AWS ALB

opened 09:52AM - 06 Jun 18 UTC

closed 08:04PM - 06 Jun 18 UTC

I tried to post this in the community forums, but was denied as it has more than… two links. Hi, I'm trying to launch Grafana on AWS ECS (Docker underneath), and having some issues with what Grafana thinks it should be addressed by. When using ECS you have to use an AWS ALB in order to have a consistent front end. The ALB is, in some ways, like HAProxy, NGinx, etc. It does path pattern matching, and in my case I'm trying to present Grafana as a path within a larger application, ie, we have https://app.foo.bar/sales, https://app.foo.bar/marketing, and hopefully https://app.foo.bar/grafana - the ALB takes care of directing the relevant requests to the appropriate ECS tasks. I have Grafana configured with what I believe to be appropriate values: - Name: GF_SERVER_DOMAIN Value: "app.foo.bar" - Name: GF_SERVER_ROOT_URL Value: "https://app.foo.bar/grafana" On all occasions it returns the Grafana unhandled 404 page - the white page with '{{alert.title}} and 4 links at the top left. At startup it emits the following log: t=2018-06-06T09:12:45+0000 lvl=info msg="Initializing HTTP Server" logger=http.server address=0.0.0.0:3000 protocol=http subUrl=/grafana socket= When I visit https://app.foo.bar/grafana/, Chrome Dev tools suggest that it's trying to load https://app.foo.bar/grafana/public/build/grafana.dark.css?v5.1.3 but being met with a 404. The logs from the docker container when trying to visit the main page are as follows: t=2018-06-06T09:40:46+0000 lvl=info msg="Request Completed" logger=context userId=0 orgId=1 uname= method=GET path=/grafana/public/build/grafana.dark.css status=404 remote_addr=10.2.10.206 time_ms=1 size=14912 referer=https://app.foo.bar/grafana/ I'm not sure why it's failing to deliver content from /grafana/. Can anyone help? It appears to be a bug.