Configuring cloud routing

After you create a cloud supergraph, you can view and manage its router's configuration from Apollo Studio. Go to the Settings page for your variant in Studio, then click the Cloud Router tab:

This page shows the following information:

• The URL of your router's GraphQL endpoint
  • Every cloud router's URL is on a subdomain of apollographos.net.
• Your router's current status and launch history
• Any secrets you've added
• Your router's YAML-based configuration

Managing secrets

You can store secret string values that you can then use in your router's YAML configuration. For example, you might store an authorization token that the router needs to include in each of its request to a subgraph.

To add a new secret, click Save a secret. The following dialog appears:

Enter a name and value for your secret. You can't view a secret's value after you save it, so make sure that the value is correct before saving. When you're ready, click Save secret.

Your secret is encrypted and stored. You can then use the secret's value in your router's YAML configuration.

The following example YAML configuration uses the value of a secret named MY_SECRET:

1
headers:
2
  all:
3
    request:
4
      - insert:
5
          name: 'subgraph-token'
6
          value: '${env.MY_SECRET}' 

Router configuration YAML

You can configure certain aspects of your router's behavior in the Router configuration YAML section of the Cloud Router tab. Specifically, you can configure:

• HTTP headers that the router sends to your subgraphs
• CORS rules for browser-based applications connecting to the router
• Subgraph error inclusion to expose subgraph errors to querying clients (including the Apollo Explorer)

• Introspection to allow resolving introspection queries.

After you make any changes to your YAML configuration, you must save those changes (CMD+S or CTRL+S) for those changes to take effect.

HTTP header rules

You can configure which HTTP headers your router includes in its requests to each of your subgraphs. You can define per-subgraph header rules, along with rules that apply to all subgraphs.

You define header rules in your Router configuration YAML, like so:

1
# ...other configuration...
2
headers:
3
  all: # Header rules for all subgraphs
4
    request:
5
      - propagate:
6
          matching: ^upstream-header-.*
7
      - remove:
8
          named: 'x-legacy-account-id'
9
  subgraphs:
10
    products: # Header rules for just the products subgraph
11
      request:
12
        - insert:
13
            name: 'router-subgraph-name'
14
            value: 'products'

Supported header rules

Cloud routing supports the following types of header rules:

propagate

Enables you to selectively pass along headers that were included in the client's request to the router.

You can specify which headers to propagate based on a matching regex pattern:

1
- propagate:
2
    matching: .*

Alternatively, you can provide a static string via the named option. These named configurations have additional flexibility, because they support the following options:

• default: A value to set if no value was sent by the client
• rename: Renames the header's key to the provided value

1
- propagate:
2
    named: 'x-user-id'
3
    default: 'abc123'
4
    rename: 'account-id'

remove

Enables you to selectively remove headers that were included in the client's request to the router. Like propagate, this option can match either a static string or a regular expression.

1
# Do not send this subgraph the "Cookie" header.
2
- remove:
3
    named: 'Cookie'
4
- remove:
5
    # Remove headers that include the legacy 'x-' prefix.
6
    matching: ^x-.*$

insert

Enables you to add custom headers to requests going to a specific subgraph. These headers are always static strings that originate in the router, instead of originating in the client.

1
- insert:
2
    name: 'sent-from-our-apollo-router'
3
    value: 'indeed'

Rule ordering

Header rules are applied in the same order they're declared, and later rules can override the effects of earlier rules. Consider this example:

❌

1
headers:
2
  all:
3
    request:
4
      - remove:
5
        named: 'test'
6
      - propagate:
7
        matching: .*

In this example, first any header named test is removed from the list of headers to propagate. However, the list of headers to propagate is currently empty! Next, the propagate rule adds all headers to the propagation list, including test.

To correctly remove a header from the propagation list, make sure to define your remove rule after any propagate rules:

✅

1
headers:
2
  all:
3
    request:
4
      - propagate:
5
        matching: .*
6
      - remove:
7
        named: 'test'

With this ordering, first all headers are added to the propagation list, then the test header is removed.

Example

Here's a complete example that demonstrates all supported headers configuration options:

1
headers:
2
  # Header rules for all subgraphs
3
  all:
4
    request:
5
      # Propagate matching headers
6
      - propagate:
7
          matching: ^upstream-header-.*
8
      # Propagate matching headers
9
      - propagate:
10
          named: 'some-header'
11
          default: 'default-value'
12
          rename: 'destination-header'
13
      # Remove the "x-legacy-account-id" header
14
      - remove:
15
          named: 'x-legacy-account-id'
16
      # Remove matching headers
17
      - remove:
18
          matching: ^x-deprecated-.*
19
      # Insert the 'my-company' header
20
      - insert:
21
          name: 'my-company'
22
          value: 'acme'
23
  # Subgraph-specific header rules
24
  subgraphs:
25
    products:
26
      request:
27
        # Calls to the products subgraph have the "router-subgraph-name" header set to `products`.
28
        - insert:
29
            name: 'router-subgraph-name'
30
            value: 'products'
31
    accounts:
32
      request:
33
        # Calls to the accounts subgraph have the "router-subgraph-name" header set to `accounts`.
34
        - insert:
35
            name: 'router-subgraph-name'
36
            value: 'accounts'

CORS settings

By default, the router enables only Apollo Studio to initiate browser connections to it. If your supergraph serves data to other browser-based applications, you need to do one of the following in the cors section of your Router configuration YAML:

• Add the origins of those web applications to the router's list of allowed origins.

  • Use this option if there is a known, finite list of web applications that consume your cloud supergraph.

• Add a regex that matches the origins of those web applications to the router's list of allowed origins.

  • This option comes in handy if you want to match origins against a pattern, see the example below that matches subdomains of a specific namespace.

• Enable the allow_any_origin option.

  • Use this option if your supergraph is a public API with arbitrarily many web app consumers.
  • With this option enabled, the router sends the wildcard (*) value for the Access-Control-Allow-Origin header. This enables any website to initiate browser connections to it (but they can't provide cookies or other credentials).

• You must use the origins + match_origins option if clients need to authenticate their requests with cookies.

The following snippet includes an example of each option (use either allow_any_origin, or origins + match_origins):

1
cors:
2
  # Set to true to allow any origin
3
  # (Defaults to false)
4
  allow_any_origin: true
5

6
  # List of accepted origins
7
  # (Ignored if allow_any_origin is true)
8
  # (Defaults to the Apollo Studio url: `https://studio.apollographql.com`)
9
  #
10
  # An origin is a combination of scheme, hostname and port.
11
  # It does not have any path section, so no trailing slash.
12
  origins:
13
    - https://www.your-app.example.com
14
    - https://studio.apollographql.com # Keep this so Apollo Studio can run queries against your router
15
  match_origins:
16
    - 'https://([a-z0-9]+[.])*api[.]example[.]com' # any host that uses https and ends with .api.example.com

You can also disable CORS entirely by setting origins to an empty list:

1
cors:
2
  origins: []

Passing credentials

If your router requires requests to include a user's credentials (e.g., via cookies), you need to modify your CORS configuration to tell the browser those credentials are allowed.

You can enable credentials with CORS by setting the Access-Control-Allow-Credentials HTTP header to true.

To allow browsers to pass credentials to your router, set allow_credentials to true, like so:

1
cors:
2
  origins:
3
    - https://www.your-app.example.com
4
    - https://studio.apollographql.com
5
  allow_credentials: true

For examples of sending cookies and authorization headers from Apollo Client, see Authentication.

All cors options

The following snippet shows all CORS configuration defaults for your router:

1
#
2
# CORS (Cross Origin Resource Sharing)
3
#
4
cors:
5
  # Set to true to allow any origin
6
  allow_any_origin: false
7

8
  # List of accepted origins
9
  # (Ignored if allow_any_origin is set to true)
10
  #
11
  # An origin is a combination of scheme, hostname and port.
12
  # It does not have any path section, so no trailing slash.
13
  origins:
14
    - https://studio.apollographql.com # Keep this so Apollo Studio can still run queries against your router
15

16
  # Set to true to add the `Access-Control-Allow-Credentials` header
17
  allow_credentials: false
18

19
  # The headers to allow.
20
  # Not setting this mirrors a client's received `access-control-request-headers`
21
  # This is equivalent to allowing any headers,
22
  # except it will also work if allow_credentials is set to true
23
  allow_headers: []
24

25
  # Allowed request methods
26
  methods:
27
    - GET
28
    - POST
29
    - OPTIONS
30

31
  # Which response headers are available to scripts running in the
32
  # browser in response to a cross-origin request.
33
  expose_headers: []

Response Vary header

A plugin may set a response Vary header. If, after all plugins are processed, there is no response Vary header, then the router will add one with a value of "origin".

Subgraph error inclusion

By default, your cloud supergraph redacts the details of subgraph errors in its responses to clients. The router instead returns a default error with the following message:

1
Subgraph errors redacted

This redaction prevents potential leaks of sensitive information to clients.

If you instead want to propagate subgraph errors to clients, you can add the include_subgraph_errors key to your router's YAML configuration, like so:

1
include_subgraph_errors:
2
  all: true # Propagate errors from all subraphs
3
  subgraphs:
4
    products: false # Do not propagate errors from the products subgraph

Any configuration under the subgraphs key takes precedence over configuration under the all key. In the example above, subgraph errors are included from all subgraphs except the products subgraph.

Introspection

By default, your cloud supergraph does not resolve introspection queries. You can enable introspection like so:

1
# Do not enable introspection for production workloads!
2
supergraph:
3
  introspection: true