AWS bedrock documentation change
Summary
Fixed typo in parameter name from 'fieldsToExlcude' to 'fieldsToExclude' in metadata configuration documentation
Security assessment
Typographical correction improves documentation accuracy but doesn't address security vulnerabilities or describe security features. Ensures proper parameter usage without changing security posture.
Diff
diff --git a/bedrock/latest/userguide/kb-metadata.md b/bedrock/latest/userguide/kb-metadata.md index a95e1b927..fde6e72ec 100644 --- a//bedrock/latest/userguide/kb-metadata.md +++ b//bedrock/latest/userguide/kb-metadata.md @@ -58 +58 @@ For example, say there's a CSV with a column 'Description' and a column 'Creatio -If no inclusion/exclusion fields are provided, all columns are treated as metadata columns, except the content column. If only inclusion fields are provided, only the provided columns are treated as metadata. If only exclusion fields are provided, all columns, except the exclusion columns are treated as metadata. If you provide the same `fieldName` in both `fieldsToInclude` and `fieldsToExlcude`, Amazon Bedrock throws a validation exception. If there’s a conflict between inclusion and exclusion, it ] will result in a failure. +If no inclusion/exclusion fields are provided, all columns are treated as metadata columns, except the content column. If only inclusion fields are provided, only the provided columns are treated as metadata. If only exclusion fields are provided, all columns, except the exclusion columns are treated as metadata. If you provide the same `fieldName` in both `fieldsToInclude` and `fieldsToExclude`, Amazon Bedrock throws a validation exception. If there’s a conflict between inclusion and exclusion, it ] will result in a failure.