Hello. We are in the process of upgrading from 0.8.10->0.8.11 (yes...baby steps) and got hit by a limitation that the frontend can only talk

http

with the gms, not

https

. In our setup all datahub components talk with each other over SSL. However, if I change the scheme here to https I get a 400 Bad Request response back from the GMS. I was wondering if I'm missing something else that might have to be configured to make the connection work over SSL. I see that by coincidence, 12 hours ago some support for https was committed to master, but we prefer to stay a few releases behind latest. Perhaps @big-carpet-38439 you have a tip?

Hey will get back soon

Just FYI, I got this to work (a bit hackish) by making the protocol configurable in combination with removing the 'host' http header. Since our components sit behind AWS LBs (with custom Route53 dns names), the value of the 'host' header as set by the frontend is probably considered corrupted by the metadata-service since it doesn't match the actual hostname of the frontend instance that makes the request.

Got it - so you were also able to configure a certificate at GMS so it can accept inbound https?

Not necessary. Incoming SSL termination is at the AWS LB. GMS only sees plain http.

Oh - then how are you making HTTPs authenticated requests to GMS? I guess it reroutes to the LB?