Merge branch 'main' into adb-fixes

artberger · web-flow · commit 4cb0992ff493 · 2026-07-23T11:47:19.000-04:00
diff --git a/content/docs/kubernetes/main/llm/guardrails/bedrock-guardrails.md b/content/docs/kubernetes/main/llm/guardrails/bedrock-guardrails.md
@@ -55,7 +55,7 @@ AWS Bedrock Guardrails are model-agnostic and can be applied to any Large Langua
    apiVersion: {{< reuse "agw-docs/snippets/api-version.md" >}}
    kind: {{< reuse "agw-docs/snippets/policy.md" >}}
    metadata:
-     name: openai-prompt-guard
+     name: bedrock-prompt-guard
      namespace: {{< reuse "agw-docs/snippets/namespace.md" >}}
    spec:
      targetRefs:
@@ -69,7 +69,7 @@ AWS Bedrock Guardrails are model-agnostic and can be applied to any Large Langua
            - bedrockGuardrails:
                identifier: <guardrail-ID>
                version: "<version>" 
-               region: <region>>
+               region: <region>
                policies:
                  auth:
                    aws: 
@@ -79,7 +79,7 @@ AWS Bedrock Guardrails are model-agnostic and can be applied to any Large Langua
            - bedrockGuardrails:
                identifier: <guardrail-ID>
                version: "<version>" 
-               region: <region>>
+               region: <region>
                policies:
                  auth:
                    aws: 
@@ -92,6 +92,8 @@ AWS Bedrock Guardrails are model-agnostic and can be applied to any Large Langua
    The `aws: {}` configuration uses the default AWS credential chain (IAM role, environment variables, or instance profile). For authentication details, see the [AWS authentication documentation](https://docs.aws.amazon.com/sdk-for-go/api/aws/session/).
    {{< /callout >}}
 
+   The `policies` field supports more than the `aws` credential source shown here. You can choose a different authentication method or tune the connection that agentgateway opens to Bedrock, such as setting a request timeout or custom TLS. For all the options, see [Backend connection and authentication policies](#backend-connection-and-authentication-policies).
+
 
 5. Test the guardrail. The following commands assume that you set up your guardrail to block requests that contain email information. 
    {{< tabs >}}
@@ -156,12 +158,56 @@ AWS Bedrock Guardrails are model-agnostic and can be applied to any Large Langua
    The request was rejected due to inappropriate content
    ```
 
+## Backend connection and authentication policies
+
+The `policies` field configures how agentgateway connects and authenticates to the AWS Bedrock Guardrails service when it evaluates a request or response.
+
+### Authentication
+
+Under `policies.auth`, set one credential source (`aws`, `secretRef`, or `key`). Optionally, set `location` to control where the credential is placed.
+
+| Method | Description |
+| -- | -- |
+| `aws` | Authenticate with AWS credentials. Set `aws: {}` to use the default AWS credential chain (IAM role, environment variables, or instance profile), or set `aws.secretRef` to read credentials from a Kubernetes secret. |
+| `secretRef` | Read the API key from a Kubernetes secret. By default, the key that matches the credential location is used, such as `Authorization` for the default header location. To use a different key, set `secretRef.key`. |
+| `key` | Send an inline API key in the `Authorization` header. This option is the least secure. Use a secret instead when possible. |
+| `location` | Where to place the credential. Defaults to the `Authorization` header with a `Bearer` prefix. To change it, set a `header`, `queryParameter`, or `cookie`. |
+
+### Backend connection settings
+
+You can also tune the connection that agentgateway opens to the Bedrock Guardrails backend by setting the following `BackendConnectionPolicy` fields under `policies`.
+
+| Setting | Description |
+| -- | -- |
+| `tls` | TLS settings for the connection, such as a custom CA certificate or SNI. |
+| `http` | HTTP settings, such as the `requestTimeout` and HTTP protocol `version`. |
+| `tcp` | TCP connection settings. |
+| `tunnel` | Tunnel settings, such as an `HTTPS_PROXY`, used to reach the backend. |
+
+For example, the following prompt guard authenticates with a secret and sets a request timeout for the calls to Bedrock.
+
+```yaml
+- bedrockGuardrails:
+    identifier: <guardrail-ID>
+    version: "<version>"
+    region: <region>
+    policies:
+      auth:
+        aws:
+          secretRef:
+            name: aws-secret
+      http:
+        requestTimeout: 5s
+```
+
+For the full set of fields, see the [API reference]({{< link-hextra path="/reference/api/" >}}).
+
 ## Cleanup
 
 {{< reuse "agw-docs/snippets/cleanup.md" >}}
 
 ```sh
-kubectl delete {{< reuse "agw-docs/snippets/policy.md" >}} openai-prompt-guard -n {{< reuse "agw-docs/snippets/namespace.md" >}} 
+kubectl delete {{< reuse "agw-docs/snippets/policy.md" >}} bedrock-prompt-guard -n {{< reuse "agw-docs/snippets/namespace.md" >}} 
 kubectl delete secret aws-secret -n {{< reuse "agw-docs/snippets/namespace.md" >}} 
 ```
     
diff --git a/content/docs/kubernetes/main/llm/guardrails/google-model-armor.md b/content/docs/kubernetes/main/llm/guardrails/google-model-armor.md
@@ -178,7 +178,7 @@ In your GKE cluster, set up workload identity.
          promptGuard:
            request:
            - googleModelArmor:
-               templateId: <template-ID
+               templateId: <template-ID>
                projectId: <project-ID>
                location: <location>
                policies:
@@ -187,7 +187,7 @@ In your GKE cluster, set up workload identity.
                      type: AccessToken
            response:
            - googleModelArmor:
-               templateId: <template-ID
+               templateId: <template-ID>
                projectId: <project-ID>
                location: <location>
                policies:
@@ -197,6 +197,8 @@ In your GKE cluster, set up workload identity.
    EOF
    ```
 
+   The `policies` field supports more than the `gcp` authentication shown here. You can also tune the connection that agentgateway opens to Model Armor, such as setting a request timeout or custom TLS. For all the options, see [Backend connection and authentication policies](#backend-connection-and-authentication-policies).
+
 2. Send a request to the Gemini provider that triggers the guardrail. 
    {{< tabs >}}
    {{% tab name="Gemini default" %}}
@@ -269,3 +271,56 @@ In your GKE cluster, set up workload identity.
    The request was rejected due to inappropriate content
    ```
 
+## Backend connection and authentication policies
+
+The `policies` field configures how agentgateway connects and authenticates to Google Model Armor when it evaluates a request or response.
+
+### Authentication
+
+Under `policies.auth`, set the credential source.
+
+| Method | Description |
+| -- | -- |
+| `gcp` | Authenticate with GCP credentials. Set `gcp: {}` to use the default Google credential discovery, or set the credential `type` to use, such as `AccessToken`. |
+
+### Backend connection settings
+
+You can also tune the connection that agentgateway opens to the Model Armor backend by setting the following `BackendConnectionPolicy` fields under `policies`.
+
+| Setting | Description |
+| -- | -- |
+| `tls` | TLS settings for the connection, such as a custom CA certificate or SNI. |
+| `http` | HTTP settings, such as the `requestTimeout` and HTTP protocol `version`. |
+| `tcp` | TCP connection settings. |
+| `tunnel` | Tunnel settings, such as an `HTTPS_PROXY`, used to reach the backend. |
+
+For example, the following prompt guard sets a request timeout for the calls to Model Armor.
+
+```yaml
+- googleModelArmor:
+    templateId: <template-ID>
+    projectId: <project-ID>
+    location: <location>
+    policies:
+      auth:
+        gcp:
+          type: AccessToken
+      http:
+        requestTimeout: 5s
+```
+
+For the full set of fields, see the [API reference]({{< link-hextra path="/reference/api/" >}}).
+
+## Cleanup
+
+{{< reuse "agw-docs/snippets/cleanup.md" >}}
+
+```sh
+kubectl delete {{< reuse "agw-docs/snippets/policy.md" >}} google-prompt-guard -n {{< reuse "agw-docs/snippets/namespace.md" >}}
+```
+
+If you set up a local cluster (kind), also delete the credentials secret. For a GKE cluster that uses workload identity, no secret is created.
+
+```sh
+kubectl delete secret gcp-credentials -n {{< reuse "agw-docs/snippets/namespace.md" >}}
+```
diff --git a/content/docs/kubernetes/main/llm/guardrails/moderation.md b/content/docs/kubernetes/main/llm/guardrails/moderation.md
@@ -40,6 +40,8 @@ The OpenAI Moderation API detects potentially harmful content across categories
    EOF
    ```
 
+   The `policies` field supports more than the `secretRef` authentication shown here. You can choose a different authentication method or tune the connection that agentgateway opens to the Moderation API, such as setting a request timeout or custom TLS. For all the options, see [Backend connection and authentication policies](#backend-connection-and-authentication-policies).
+
 2. Test with content that triggers moderation. 
    {{< tabs >}}
 
@@ -83,6 +85,46 @@ The OpenAI Moderation API detects potentially harmful content across categories
    Content blocked by moderation policy
    ```
 
+## Backend connection and authentication policies
+
+The `policies` field configures how agentgateway connects and authenticates to the OpenAI Moderation API when it evaluates a request.
+
+### Authentication
+
+Under `policies.auth`, set one credential source (`secretRef` or `key`). Optionally, set `location` to control where the credential is placed.
+
+| Method | Description |
+| -- | -- |
+| `secretRef` | Read the API key from a Kubernetes secret. By default, the key that matches the credential location is used, such as `Authorization` for the default header location. To use a different key, set `secretRef.key`. |
+| `key` | Send an inline API key in the `Authorization` header. This option is the least secure. Use a secret instead when possible. |
+| `location` | Where to place the credential. Defaults to the `Authorization` header with a `Bearer` prefix. To change it, set a `header`, `queryParameter`, or `cookie`. |
+
+### Backend connection settings
+
+You can also tune the connection that agentgateway opens to the OpenAI Moderation backend by setting the following `BackendConnectionPolicy` fields under `policies`.
+
+| Setting | Description |
+| -- | -- |
+| `tls` | TLS settings for the connection, such as a custom CA certificate or SNI. |
+| `http` | HTTP settings, such as the `requestTimeout` and HTTP protocol `version`. |
+| `tcp` | TCP connection settings. |
+| `tunnel` | Tunnel settings, such as an `HTTPS_PROXY`, used to reach the backend. |
+
+For example, the following prompt guard authenticates with a secret and sets a request timeout for the calls to the Moderation API.
+
+```yaml
+- openAIModeration:
+    model: omni-moderation-latest
+    policies:
+      auth:
+        secretRef:
+          name: openai-secret
+      http:
+        requestTimeout: 5s
+```
+
+For the full set of fields, see the [API reference]({{< link-hextra path="/reference/api/" >}}).
+
 ## Cleanup
 
 {{< reuse "agw-docs/snippets/cleanup.md" >}}
