| title | description | services | documentationcenter | author | manager | editor | ms.service | ms.workload | ms.tgt_pltfrm | ms.topic | ms.date | ms.author |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
Provision a self-hosted gateway in Azure API Management | Microsoft Docs |
Learn how to provision a self-hosted gateway in Azure API Management. |
api-management |
miaojiang |
gwallace |
api-management |
mobile |
na |
article |
03/31/2020 |
apimpm |
Provisioning a gateway resource in your Azure API Management instance is a prerequisite for deploying a self-hosted gateway. This article walks through the steps to provision a gateway resource in API Management.
Complete the following quickstart: Create an Azure API Management instance
[!INCLUDE api-management-navigate-to-instance.md]
- Select the Gateways from under Deployment and infrastructure.
- Click + Add.
- Enter the Name and Region of the gateway.
Tip
Region specifies intended location of the gateway nodes that will be associated with this gateway resource. It's semantically equivalent to a similar property associated with any Azure resource, but can be assigned an arbitrary string value.
- Optionally, enter a Description of the gateway resource.
- Optionally, select + under APIs to associate one or more APIs with this gateway resource.
Important
By default, none of the existing APIs will be associated with the new gateway resource. Therefore, attempts to invoke them via the new gateway will result in 404 Resource Not Found responses.
- Click Add.
Now the gateway resource has been provisioned in your API Management instance. You can proceed to deploy the gateway.
- To learn more about the self-hosted gateway, see Azure API Management self-hosted gateway overview
- Learn more about how to Deploy a self-hosted gateway to Kubernetes
- Learn more about how to Deploy a self-hosted gateway to an Azure Arc enabled Kubernetes cluster
- Learn more about how to Deploy a self-hosted gateway to Docker