AWS bedrock documentation change
Summary
Clarified that CORS configuration is specifically required on the S3 output bucket for human-based evaluation jobs to display content to annotators.
Security assessment
Change provides operational clarification about when CORS is needed but doesn't address a security vulnerability or weakness. It enhances documentation accuracy without security implications.
Diff
diff --git a/bedrock/latest/userguide/model-evaluation-prompt-datasets-custom-human.md b/bedrock/latest/userguide/model-evaluation-prompt-datasets-custom-human.md index 754ca029d..2215a82ed 100644 --- a//bedrock/latest/userguide/model-evaluation-prompt-datasets-custom-human.md +++ b//bedrock/latest/userguide/model-evaluation-prompt-datasets-custom-human.md @@ -17 +17 @@ Custom prompt datasets must be stored in Amazon S3, and use the JSON line format -For job created using the console you must update the Cross Origin Resource Sharing (CORS) configuration on the S3 bucket. To learn more about the required CORS permissions, see [Required Cross Origin Resource Sharing (CORS) permissions on S3 buckets](./model-evaluation-security-cors.html). +For human-based evaluation jobs created using the console, you must configure Cross Origin Resource Sharing (CORS) on the S3 output bucket. This is required to display prompts and inference results to human annotators in the annotation portal. To learn more about the required CORS permissions, see [Required Cross Origin Resource Sharing (CORS) permissions on S3 buckets](./model-evaluation-security-cors.html).