Setting up an API Gateway - Internal hosts

Questions and Answers
1

ISSUE

I’m setting up an API gateway. In order for this to work, I need to have connectivity between the gateway and my API’s. I’m doing this using the external URL’s (the ones defined as environment variables, e.g. QOVERY_APPLICATION_APPID_HOST_EXTERNAL) and it’s working. But I’d like to remove the public visibility for these API’s, so I ran tests with the internal URL’s, but those aren’t working. Is there anything different when I use internal va external url’s?

Thanks in advance

API Gateway: Qovery Web Console | Deploy and Manage On-demand Environments on AWS, Remarkably Fast

Some API: Qovery Web Console | Deploy and Manage On-demand Environments on AWS, Remarkably Fast

2

Hi @donaldinostroza ,

Did you take a look at this guide.

3

Hi Romaric, thanks for the reply. Yes, I have read it, but our case is slightly different, as we’re implementing Kong api gateway. However, I gave it a second look, and I realize we were using https (instead of http), but despite of that change it is still failing. I have to say the request is never completed, it just waits until timeout.

The url the gateway is calling (and failing) is like this “http://app-z3a8eefd6/specific-endpoint”.
The url that is working is like this: “https://zf0050c5b-z9deaa37c-gtw.zb8507aad.rustrocks.me/specific-endpoint”

Am I missing something?

4

Hi @donaldinostroza You need to include the port of your application in the url when calling internal services. For example http://app-z3a8eefd6:3000/specific-endpoint

1 Like
5

exactly! thank you @itajenglish !

1 Like
6

Hi @donaldinostroza - I am also setting up API Gateway using Kong and have a few questions on the architecture.

Deployment

Seems like there are two options.

  1. To use helm charts to install kong on the kubernetes cluster that is from Qovery
  2. To create a repo with dockerfile and register it as an app in Qovery.

Which method did you choose and why?

For more context, I am using the 2nd approach but facing issues due to

  1. Postgres connectivity. Most online resources talk about setting up a docker network but that’s not possible in our case.
  2. Exposing various ports. At the moment, qovery only supports 443 as the external port, so I am unable to expose 8081 and so on to the internet.