Self-hosted API Management gateway
To expand support for hybrid use cases and enable more efficient on-premises-to-on-premises call patterns for internal-only and internal/external APIs, we will provide an option for customers to self-host a containerized version of the API Management gateway component (fully equivalent to the gateway in the cloud, not a “micro-gateway”) on-premises or other environment e.g. other public clouds. Self-hosted gateway will require and will be managed from a cloud-based Azure API Management instance.
Nathan Becker commented
Well, it looks like it's reached general availability ( https://azure.microsoft.com/en-us/updates/selfhosted-gateway-feature-in-api-management-is-now-generally-available/ ), but we were extremely disappointed to see that each gateway is an additional $1000/month, *on top* of the $2700/month for the Premium requirement. We don't have a large amount of volume, but ideally would like to have our exposed API endpoints globally distributed to reduce latency between our customers and us and to have high-availability in the event of a regional outage. We would be fine with a tier that throttled the number of requests per gateway if it would mean we could globally distribute our endpoints and not be charged for the Premium subscription. As of now, the only viable option for us, if we keep using API management, is hacked-together solutions like this that sync API Endpoint instances, which is definitely not ideal: https://www.sanganakauthority.com/2019/08/azure-api-management-disaster-recovery.html I'm not sure why the API management team is insisting on locking some of the most major useful features for companies of all sizes (VNET support, DR, multi-region deployments) behind the Premium version, when it's not really financially viable for anyone but large corporations with huge volumes. It's really frustrating.
Gregory Douglas commented
Is there an OFFICIAL list of the names and/or IPs for required to configure and operate the self-hosted gateway for API Management? I am working on a POC of the API Management and Self-Hosted Gateway. We had this stood up and working until The Cyber Security group at my client shut down all outside internet access from all the servers we have been working with.
They are only willing to open ports absolutely necessary for our services to run. with that said I am looking for the list of IPS/urls and/or Services necessary to configure and operate API Management and Self-Hosted Gateway.
Is this information available anywhere?
What is the ETA for general availability
Nathan Becker commented
Like many others, we simply cannot justify $2400/month for our volume, but would love the ability to deploy to multiple regions. Adding this to all tiers would be perfect.
Stephane LE TANTER commented
Same question as Guna, Is there an ETA for the General Availability for Self-Hosted API Gateways?
My organisation is looking into moving our Sharepoint workloads to Sharepoint Online.
Unfortunately not being able to easily access on-premise APIs is blocking the whole project.
Guna Sekhar commented
What is the General Availability (GA) timeline for Self-Hosted API Gateway?
Ahmet Arsan commented
I'm confused if this service requires Azure Arc or not. The quickstart just shows docker but the announcement says "arc enabled apim":
Can we enable the twobway ssl with this feature?
Can we also get the feature , access based on operation level of API?
As in preview, a self-hosted gateway is available only for Developer and Premium tiers.
Will be this feature available also in Standard tier later ?
In our organization we have no use for Premium tier but we would certainly utilize 2 or 3 self-hosted gateways.
The API mANAGEMENT SHOULD BE ALSO AVAILABLE ON PREMISES
How many API gateways can be connected to self hosted portal? and Does the new API portal has the features to show only required API's based on user roles. We want to show API's to users who they are allowed.
That would be great, but when will this feature be available for customers?
James Estes commented
This will really help with hybrid use cases
Jørgen Michelsen commented
Are there any plans regarding the licensing model for self-hosted gateways? Will they be free of charge as long as the management instance is paid for?
Andrej Medic commented
Wondering how this wold integrate with Service Fabric and Service Fabric Mesh clusters in Azure and also on-prem? For example will we be able to Self-host the API Management gateway in an Azure SF cluster?
Rexon Jeyasingh commented
great news much needed feature so you can have a single view for both onpremise and cloud API's.
Alessandro Moura commented
Yes, this will be very much appreciated by companies that just have API communication in the internal network and it does not make sense to go to the cloud to route back to the internal network.
Eurico Borges commented
This is a step in the right direction and I think it will certainly benefict many companies that want to have an API led architecture also on-premise only.
What I would strongly request is the possibility to aggreagate centraly the analytics and management of several of these on-premises gateways.
Daniel Hoenig commented
This has been set to planned for 2 years...is it really planned? We would choose Azure APIM over the other api management tools if this feature existed. Since it does not, Azure APIM is off the list.
Nikolai Blackie commented
Please split API gateway from API Management and allow gateways to be deployed anywhere. 2 years in planning, hope we see an awesome result. Getting slated in industry analysis and makes it very hard to sell solution into organisations with on prem gateway support. Also latency is a massive issue.
"As the offering became generally available as long ago as 2014, Gartner has concerns about Microsoft's commitment of resources to it, and about the offering's long-term viability in a rapidly evolving API management market.", "Azure API Management supports virtual network connectivity for access to on-premises resources, but does not have a customer-managed deployment option that could be hosted on-premises or outside Azure"