Hi all, I am been trying to setup metabase as a service on AWS ECS Fargate and serve the metabase to public via AWS ALB.
Note that I have setup the path forwarding rule in our ALB where /app/metabase* will forward to the metabase ecs service.
I also point the LB healthcheck to the correct metabase healthcheck API [/api/health] in the ALB and also have confirmed that the healthcheck endpoint got called via verifying the logs in metabase.
DEBUG middleware.log :: e[32mGET /api/health 200 721.8 µs (0 DB calls) App DB connections: 1/4 Jetty threads: 3/50 (4 idle, 0 queued) (31 total active threads) Queries in flight: 0 (0 queued)e[0m
However, I failed to access the service via url https://domain-name/app/metabase.
The attempt that I tried to fix this was to configure the environment variables
Hi @lho, I am also facing a similar issue, I can get to the root/apex of my ALB but as soon as I go to the rule pointing to Metabase target group it just loads forever. Did you manage to figure out how to do it? I am also using internal ALB although I think the issue will be the same
Hello @Mws, I am not sure if it's the same issue, but in my case, the problem occurs because AWS ALB forwards the request to a specific target group along with the defined path pattern.
For example: https://domain-name/app/metabase is forwarded to http://localhost:3000/app/metabase, but this path is not found in the Metabase app.
To solve this, I set up an Nginx reverse proxy in front of the Metabase app to trim away the target group path before forwarding the request to the Metabase app.