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.
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"
David GROSPELIER commented
Anything new regarding this topic?
Michael O'Brien commented
Azure Stack is a new on premise offering that currently does not have Azure API Management, but would be a good service offering for the on premise Azure Stack option.
Tomas Carrillo commented
+3 on this, people does now attacks on cloud are increasing 300% year a year. source https://www.microsoft.com/en-us/security/Intelligence-report
Is there any update on when this feature will be developed and released? While we look to cloud host our services by default, there are situations where government regulations require on premise installation and we would like to use the same framework.
This is a critical issue for us (for performance, security and compliance reasons), and is the main reason why we're considering other other API Platforms than Azure - like Akana (the proxy and api mgmnt package may be installed on-prem).
This is a critical issue for us (for performance, security and compliance reasons), and is the main reason why we're considering other other API Platforms than Azure - like Akana (the proxy may be installed on-prem).