Create a Gateway Routing Configuration
Focus
Focus
Prisma AIRS

Create a Gateway Routing Configuration

Table of Contents


Create a Gateway Routing Configuration

Create a routing configuration in Strata Cloud Manager to control load balancing, fallback, caching, retry, and guardrail behavior for AI Gateway requests.
Where Can I Use This?What Do I Need?
  • Prisma AIRS AI Gateway (Americas region)
  • AI Gateway activated
  • At least one LLM integration configured
Gateway routing configurations are JSON objects that define how AI Gateway routes, retries, caches, and applies guardrails to LLM requests. After you create a config, it is assigned a pc- prefixed identifier and synced to the gateway data plane within 30 seconds. Applications reference the config in requests using the config field in the request body, or by using a gateway API key that has the config attached. For an overview of what configs can do, see AI Gateway Routing Configurations.
  1. In Strata Cloud Manager, select Security ServicesPolicies & ProfilesConfiguration and click Add Configuration.
  2. In Configuration Name, enter a descriptive name.
  3. In the JSON editor, enter the configuration object.
    The following example creates a load-balanced config that distributes requests evenly between two targets and retries on failure:
    { "strategy": { "mode": "loadbalance" }, "targets": [ { "virtualKey": "<workspace_virtual_key_1>", "weight": 50 }, { "virtualKey": "<workspace_virtual_key_2>", "weight": 50 } ], "retry": { "attempts": 3, "onStatusCodes": [429, 500, 502, 503] } }
    To add guardrails, include a before_request_hooks or after_request_hooks array referencing guardrail IDs. Guardrail IDs use a pg- prefix; you create these in Create a Guardrail.
  4. Click Save.
    The config is assigned a pc- prefixed ID visible in the configuration list. The gateway syncs the new config within 30 seconds; wait at least one minute before testing.
  5. (Optional) To attach this config to a gateway API key so that it applies automatically to all requests using that key, edit the key and select this config from the Default Config list. See Manage Gateway API Keys.
  6. Click Commit to apply the configuration.
    To restore a previous version, select the config in the configuration list, click Version History, and click Restore next to the version you want to roll back to.