AWS guardduty documentation change
Summary
Added validation notes for custom threat list URL formats
Security assessment
The changes clarify URL format requirements but don't address specific vulnerabilities or security incidents. This is a routine documentation improvement for user guidance.
Diff
diff --git a/guardduty/latest/ug/guardduty-lists-create-activate.md b/guardduty/latest/ug/guardduty-lists-create-activate.md index 472a7b954..797677dde 100644 --- a//guardduty/latest/ug/guardduty-lists-create-activate.md +++ b//guardduty/latest/ug/guardduty-lists-create-activate.md @@ -51 +51,3 @@ For an IP address list, the name of your list must be unique within an AWS accou -###### Format of location URL +Applies only to custom threat and custom trusted entity sets – If you provide a location URL that doesn't match the following supported formats, then you will receive an error message during list addition and activation. + +###### Format of location URL: @@ -115,0 +118,2 @@ The `expected-bucket-owner` parameter is optional. Whether or not you specify th +Applies only to custom threat and custom trusted entity sets – If you provide a location URL that doesn't match the following supported formats, then you will receive an error message during list addition and activation. + @@ -140,0 +145,2 @@ The `expected-bucket-owner` parameter is optional. Whether or not you specify th +Applies only to custom threat and custom trusted entity sets – If you provide a location URL that doesn't match the following supported formats, then you will receive an error message during list addition and activation. +