Skip to main content

Proxy to External Services

As an application grows, sites typically start to integrate with external services. These external services can range from APIs for offloading resource intensive tasks to completely separate sites which are built for a sub section of the site e.g. https://example.com/site2.

Skpr provides development teams with the ability to connect their application to others via the edge layer.

Diagram showing how Skpr routes requests through the edge layer to external proxy origins

Usage​

The example configuration below routes all /api requests to the api.example.com origin.

ingress:
  proxy:
    api:
      path: /api*
      origin: api.example.com
      cache:
        policy: drupal

Benefits​

  • External services will be cached by the Skpr edge layer.
  • Development teams will have a high level view of the application's health e.g. how many 5xx responses occurred for the application and its external services.
  • External applications will inherit Skpr's certificate management and WAF rules.