AWS bedrock: Guardrail constraints for Bedrock agentic retrieval
Summary
Expands the policyConfiguration field description to state that guardrails are only supported when foundationModelType is CUSTOM (requiring an explicit modelArn), and adds a note that agentic retrieval rejects guardrails whose sensitive information policy uses the ANONYMIZE action for PII entities or regexes.
Security assessment
The change documents how Bedrock Guardrails (a data-protection/safety control) can and cannot be applied during agentic retrieval, including a limitation on PII anonymization. It clarifies configuration behavior rather than fixing a vulnerability, so it is security-adjacent guidance of medium impact.
Evidence
+Agentic retrieval does not support guardrails whose sensitive information policy uses the `ANONYMIZE` action for PII entities or regular expressions. Such a request fails validation even when `foundationModelType` is `CUSTOM`.
Diff
diff --git a/bedrock/latest/userguide/kb-test-agentic-retrieve.md b/bedrock/latest/userguide/kb-test-agentic-retrieve.md index 7ca6f2e..3b04fbe 100644 --- a//bedrock/latest/userguide/kb-test-agentic-retrieve.md +++ b//bedrock/latest/userguide/kb-test-agentic-retrieve.md @@ -61 +61 @@ Optional fields Field | Description -policyConfiguration | Configures a Amazon Bedrock guardrail to apply during agentic retrieval. Specify a `guardrailId` and `guardrailVersion`. +policyConfiguration | Configures a Amazon Bedrock guardrail to apply during agentic retrieval. Specify a `guardrailId` and `guardrailVersion`. A guardrail is supported only when `foundationModelType` is `CUSTOM`. Passing a guardrail with the default `MANAGED` type, or without setting `foundationModelType`, fails validation. Because `CUSTOM` also requires `foundationModelConfiguration`, applying a guardrail means naming an explicit model by its `modelArn`. @@ -65,0 +66,4 @@ generateResponse | A boolean field that, when set to `true` (the default), instr +###### Note + +Agentic retrieval does not support guardrails whose sensitive information policy uses the `ANONYMIZE` action for PII entities or regular expressions. Such a request fails validation even when `foundationModelType` is `CUSTOM`. +