AWS solutions documentation change

Service: solutions · 2025-06-28 · Documentation low

File: solutions/latest/prebid-server-deployment-on-aws/tune-the-solution.md

Summary

Added 'Lambda Concurrency' section explaining request handling and throttling behavior

Security assessment

The concurrency explanation describes performance characteristics rather than security controls. While throttling could impact availability (a security pillar), the documentation doesn't present it as a security feature or vulnerability mitigation.

Diff

diff --git a/solutions/latest/prebid-server-deployment-on-aws/tune-the-solution.md b/solutions/latest/prebid-server-deployment-on-aws/tune-the-solution.md
index 251ba73b4..347667406 100644
--- a//solutions/latest/prebid-server-deployment-on-aws/tune-the-solution.md
+++ b//solutions/latest/prebid-server-deployment-on-aws/tune-the-solution.md
@@ -5 +5 @@
-CloudFront distribution domain nameGuidance on how to implement/enable TLS between CloudFront and ALBFirewall rulesContainer tuning
+CloudFront distribution domain nameGuidance on how to implement/enable TLS between CloudFront and ALBFirewall rulesContainer tuningLambda Concurrency
@@ -49,0 +50,4 @@ This solution uses a weighted combination of Fargate and Fargate Spot instances
+## Lambda Concurrency
+
+Each incoming request to a Lambda function is handled by a separate execution environment. If multiple requests arrive simultaneously, Lambda scales up the number of environments—up to your concurrency quota. If the Lambda function receives more requests than the available concurrency, excess requests are throttled.
+