generated from amazon-archives/__template_Apache-2.0
-
Notifications
You must be signed in to change notification settings - Fork 261
Enhancement/third party guardrails improvements #190
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
akshseh
merged 10 commits into
strands-agents:main
from
manoj-selvakumar5:enhancement/third-party-guardrails-improvements
Nov 12, 2025
Merged
Enhancement/third party guardrails improvements #190
akshseh
merged 10 commits into
strands-agents:main
from
manoj-selvakumar5:enhancement/third-party-guardrails-improvements
Nov 12, 2025
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Resolves directory numbering conflict with upstream samples. The number 16 is already used by lambda-error-analysis-agent, so renumbering to 19 which is the next available slot.
- Moved 02-samples/19-third-party-guardrails to 03-integrations/third-party-guardrails - Removed entry 19 from 02-samples README - Added new integration entry to 03-integrations README - Removed Python cache files before move
- README.md: 'recommended use' -> 'recommended to use', 'way to extracting' -> 'way to extract' - 01-llama-firewall/README.md: 'wiill' -> 'will' - 03-nvidia-nemo/README.md: 'seperately' -> 'separately', 'nvivida' -> 'nvidia', 'guardrai' -> 'guardrail'
- Changed line 35 from profanity to a non-profane toxic example - Example still triggers the toxic language guardrail as intended - Makes the code example more appropriate for documentation
|
Latest scan for commit: ✅ Security Scan Report (PR Files Only)Scanned Files
Security Scan Results
Threshold: High No security issues detected in your changes. Great job! This scan only covers files changed in this PR. |
Contributor
|
Thanks for sorting this out @manoj-selvakumar5 I did do a little writeup on my blog about them if thats useful at all -> https://akingscote.co.uk/posts/aws-strands-agents-guardrail-integration/ |
akshseh
previously approved these changes
Nov 12, 2025
mttanke
approved these changes
Nov 12, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Third-party guardrail integrations for Strands Agents including NVIDIA NeMo, GuardRails AI, and Llama Firewall.
Attribution
This PR builds upon the excellent work by @akingscote in #136.
Changes from original PR:
02-samples/to03-integrations/All core implementation and examples credit to @akingscote.
Supersedes #136
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.