feat/bedrock-secure-prompt-caching #5035
Merged
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
We have learned from our AWS account rep that prompt caching for AWS Bedrock is at the AWS account level. As such there is risk that similar prompts submitted by multiple users or system processes that may contain confidential information might result in leaked data between users. The best practice recommended is to add a unique value to user prompts to avoid prompt leakage between client sessions. This PR adds that feature.
Checklist
Screenshots
[ For visual changes, include screenshots. Screen recordings are particularly helpful, and appreciated! ]
Testing instructions
I've added unit tests and manually validated that the secure ID is added to the relevant prompts. I've noted that prompt caching is still functioning as expected.