AWS bedrock documentation change
Summary
Clarified enforcement conditions for abuse detection by adding 'non-responsive' as a trigger for suspension
Security assessment
The change strengthens documentation about abuse detection policies but does not address a specific security vulnerability. It clarifies operational security controls for compliance enforcement.
Diff
diff --git a/bedrock/latest/userguide/abuse-detection.md b/bedrock/latest/userguide/abuse-detection.md index cc77b794e..aa2aaea81 100644 --- a//bedrock/latest/userguide/abuse-detection.md +++ b//bedrock/latest/userguide/abuse-detection.md @@ -22 +22 @@ Automated abuse detection includes: -Once our automated abuse detection mechanisms identify potential violations, we may request information about your use of Amazon Bedrock and compliance with our terms of service or a third-party provider’s AUP. In the event that you are unwilling or unable to comply with these terms or policies, AWS may suspend your access to Amazon Bedrock. You may also be billed for the failed fine-tuning jobs if our automated tests detect model responses being inconsistent with third-party model-providers' license terms and policies. +Once our automated abuse detection mechanisms identify potential violations, we may request information about your use of Amazon Bedrock and compliance with our terms of service or a third-party provider’s AUP. In the event that you are are non-responsive or unwilling or unable to comply with these terms or policies, AWS may suspend your access to Amazon Bedrock. You may also be billed for the failed fine-tuning jobs if our automated tests detect model responses being inconsistent with third-party model-providers' license terms and policies.