AWS m2: Rate limiting doc: clarify IP bypass list as "allowlist"
Summary
Reworded the `whitelistIps` configuration comment and description to call it a comma-separated IP allowlist rather than a generic list of IPs; behavior and default unchanged.
Security assessment
The change is purely terminology ("IPs" -> "IP allowlist") in an existing rate-limiting configuration doc. The parameter and its semantics (IPs that bypass rate limiting) are unchanged, so there is no new vulnerability fix or new security guidance introduced.
Evidence
+ whitelistIps: "" # Comma-separated IP allowlist to bypass limiting
Diff
diff --git a/m2/latest/userguide/ba-runtime-rate-limiting.md b/m2/latest/userguide/ba-runtime-rate-limiting.md index 9b4f91ace..935ca470f 100644 --- a//m2/latest/userguide/ba-runtime-rate-limiting.md +++ b//m2/latest/userguide/ba-runtime-rate-limiting.md @@ -100 +100 @@ Configure rate limiting in your `application-main.yaml` file: - whitelistIps: "" # Comma-separated IPs to bypass limiting + whitelistIps: "" # Comma-separated IP allowlist to bypass limiting @@ -143 +143 @@ Custom error message returned in the JSON response when rate limit is exceeded. -Comma-separated list of IP addresses that bypass rate limiting entirely. Useful for health checks or trusted systems. Default: `empty` +Comma-separated IP allowlist of addresses that bypass rate limiting entirely. Useful for health checks or trusted systems. Default: `empty`