Using APIM as a Proxy
  • 17 Feb 2020
  • 1 Minute to read
  • Contributors
  • Dark
    Light
  • PDF

Using APIM as a Proxy

  • Dark
    Light
  • PDF

One of the approaches I quite like to implement is a follow up to using the Custom Connector approach. What I can do when using the custom connector is to change the connector from pointing directly to Serverless360 BAM API and instead to point it to Azure API Management and to then use API Management to forward on my calls to the Serverless360 BAM API.

Although I am adding an extra step this will create a layer of abstraction which has a number of benefits. First off I can change whats behing the API if I want to, next up I can use the APIM policy to inject the url rewrite and the key for the BAM API into the call, but when I have potentially got a number of other teams using the API and using it with different components I can use the entire user and subscription management features of API Management to give different people their own keys and the ability to manage the recycle of keys or disabling specific users and teams from the API. This is a good way to implement a very fine grained level of control for components to access BAM in a way your likely to already be doing for other parts of your architecture.


Was this article helpful?