- Newest
- Most votes
- Most comments
It appears that the relevance check in your Amazon Bedrock Guardrails configuration is not functioning as expected. There are a few potential reasons for this:
-
Configuration: Ensure that your guardrail is properly configured with the relevance check enabled. Double-check your guardrail settings in the Amazon Bedrock console.
-
Content structure: The way you're structuring the content in your API call might not be optimal for the relevance check. Make sure you're correctly designating the 'query', 'guard_content', and 'grounding_source' in your input.
-
Threshold sensitivity: The relevance check might not be sensitive enough to detect the discrepancy between your input and output. You may need to adjust the threshold settings for the relevance check in your guardrail configuration.
-
Guardrail version: You're using the 'DRAFT' version of the guardrail. Ensure that your changes are saved and that you're using the correct version of the guardrail.
-
API usage: Verify that you're using the correct API call for your use case. The ApplyGuardrail API is designed to assess text using pre-configured guardrails without invoking foundation models.
To troubleshoot this issue:
- Review your guardrail configuration in the Amazon Bedrock console.
- Ensure your content structure in the API call is correct.
- Try adjusting the sensitivity of your relevance check.
- Confirm you're using the intended version of your guardrail.
- Double-check that you're using the appropriate API for your use case.
If the issue persists after these steps, you may want to contact AWS support for further assistance.
Sources
Use the ApplyGuardrail API in your application - Amazon Bedrock
How Amazon Bedrock Guardrails works - Amazon Bedrock
Relevant content
asked 5 months ago
- AWS OFFICIALUpdated a month ago
