Self Hosted API gateway communication with configuration endpoint in private mode

Niccolo Giulianelli 0 Reputation points
2024-03-20T09:51:58.3366667+00:00

Hello Community

I found this post https://learn.microsoft.com/en-us/answers/questions/921919/azure-apim-self-hosted-gateway-new-stv2-configurat that is now a bit dated. I have a similar use case, with an Azure APIM that I would like to deploy in private mode and a self-hosted gateway running on AWS. The self-hosted gateway needs to be able to communicated with the configuration endpoint of the Azure APIM, <apim-service-name>.configuration.azure-api.net , so I was thinking about using Front Door to configure a custom domain and reach the configuration endpoint even if the APIM is in private mode. Is this a supported configuration? Or will I need to make the APIM public for the self-hosted gateway to communicate correctly with its configuration endpoint?

Azure API Management
Azure API Management
An Azure service that provides a hybrid, multi-cloud management platform for APIs.
1,751 questions
Azure Front Door
Azure Front Door
An Azure service that provides a cloud content delivery network with threat protection.
576 questions
{count} votes

1 answer

Sort by: Most helpful
  1. JananiRamesh-MSFT 21,171 Reputation points
    2024-03-21T17:43:07.6833333+00:00

    @Niccolo Giulianelli Thanks for reaching out. Azure Front Door cannot be used to route traffic to a backend that is deployed in a private network. This is because Azure Front Door is a public-facing service and cannot access resources that are not publicly accessible.

    In the case of an Azure APIM instance that is deployed in private mode, you will need to use a different solution to allow a self-hosted gateway running on AWS to communicate with the configuration endpoint. One possible solution is to use a VPN or ExpressRoute connection between your Azure and AWS environments to establish a private network connection.

    Let me know if you have any further questions, i would be happy to assist you.

    0 comments No comments