AWS lambda documentation change
Summary
Updated response streaming payload limit from 20 MB soft limit to 200 MB maximum
Security assessment
Change increases documented payload capacity limits but contains no security context. No vulnerabilities or security controls are mentioned.
Diff
diff --git a/lambda/latest/dg/configuration-response-streaming.md b/lambda/latest/dg/configuration-response-streaming.md index 4697c7898..784569840 100644 --- a//lambda/latest/dg/configuration-response-streaming.md +++ b//lambda/latest/dg/configuration-response-streaming.md @@ -9 +9 @@ Bandwidth limits for response streamingVPC compatibility with response streaming -You can configure your Lambda function URLs to stream response payloads back to clients. Response streaming can benefit latency sensitive applications by improving time to first byte (TTFB) performance. This is because you can send partial responses back to the client as they become available. Additionally, you can use response streaming to build functions that return larger payloads. Response stream payloads have a soft limit of 20 MB as compared to the 6 MB limit for buffered responses. Streaming a response also means that your function doesn’t need to fit the entire response in memory. For very large responses, this can reduce the amount of memory you need to configure for your function. +You can configure your Lambda function URLs to stream response payloads back to clients. Response streaming can benefit latency sensitive applications by improving time to first byte (TTFB) performance. This is because you can send partial responses back to the client as they become available. Additionally, response streaming functions can return payloads up to 200 MB, compared to the 6 MB maximum for buffered responses. Streaming a response also means that your function doesn’t need to fit the entire response in memory. For very large responses, this can reduce the amount of memory you need to configure for your function.