'Use case of API Management + App Gateway for hosting internet facing API
We intended to host the internet facing API in azure app service.
We see the use of app gateway, the use case of WAF on top of the L7 load balancer
API Management use case is the one debatable, though it does provides a lot goodies,
- $$$$, can't afford the premium tier, so the use without vnet does not quite make a lot of sense in security view
- team also argues could use a sidecar container (e.g. dapr) to serve as an api manager, e.g. to parse the jwt
Thoughts? Thanks
Solution 1:[1]
If you try to access any external API which is hosted on any on-premise server, then you can consider this path : On-premise ----> s2s ( Site to Site) VPN ----> VNet ----> application in VNet.
You may follow : https://docs.microsoft.com/en-us/azure/vpn-gateway/tutorial-site-to-site-portal Please consider these links for the case:
Solution 2:[2]
You could use the API Management self-hosted gateway along with a Dapr sidecar leveraging API Management Dapr integration policies. That way you wouldn't need the Premium Tier for VNet support.
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|---|
| Solution 1 | JayaChatterjee-MSFT |
| Solution 2 | tommasodotNET |