AWS Security ChangesHomeSearch

AWS step-functions: Update disallowed headers for Step Functions HTTP Task

Service: step-functions · 2026-10-24 · Documentation medium

File: step-functions/latest/dg/call-https-apis.md · Type: ssrf

Summary

Modifies the list of headers that cannot be used in an HTTP Task definition: removes the conditional If-* headers (If-Match, If-Modified-Since, If-None-Match, If-Range, If-Unmodified-Since) and adds Proxy-Authenticate and WWW-Authenticate.

Security assessment

The disallowed-header list is a security-relevant restriction on outbound HTTP requests made by the HTTP Task; adding authentication-challenge headers (WWW-Authenticate, Proxy-Authenticate) and removing the If-* conditional headers changes that control surface. No CVE or specific vulnerability is cited, but the change is security-adjacent hardening/config.

Evidence

  * WWW-Authenticate

Diff

diff --git a/step-functions/latest/dg/call-https-apis.md b/step-functions/latest/dg/call-https-apis.md
index a945053..a8d9d36 100644
--- a//step-functions/latest/dg/call-https-apis.md
+++ b//step-functions/latest/dg/call-https-apis.md
@@ -228,10 +227,0 @@ You can't use the following headers in your HTTP Task definition. If you use the
-  * If-Match
-
-  * If-Modified-Since
-
-  * If-None-Match
-
-  * If-Range
-
-  * If-Unmodified-Since
-
@@ -243,0 +234,2 @@ You can't use the following headers in your HTTP Task definition. If you use the
+  * Proxy-Authenticate
+
@@ -261,0 +254,2 @@ You can't use the following headers in your HTTP Task definition. If you use the
+  * WWW-Authenticate
+