AWS Security ChangesHomeSearch

AWS guardduty documentation change

Service: guardduty · 2025-10-16 · Documentation low

File: guardduty/latest/ug/guardduty-lists-update-procedure.md

Summary

Added URL format validation reminders in update procedures

Security assessment

Reiterates existing URL format requirements without introducing new security controls or addressing vulnerabilities. Focuses on operational correctness rather than security fixes.

Diff

diff --git a/guardduty/latest/ug/guardduty-lists-update-procedure.md b/guardduty/latest/ug/guardduty-lists-update-procedure.md
index b226b633a..31ea62140 100644
--- a//guardduty/latest/ug/guardduty-lists-update-procedure.md
+++ b//guardduty/latest/ug/guardduty-lists-update-procedure.md
@@ -35,0 +36,2 @@ For an IP address list, the name of your list must be unique within an AWS accou
+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.
+
@@ -72,0 +75,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.
+
@@ -96,0 +101,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.
+