AWS solutions documentation change

Service: solutions · 2025-07-13 · Documentation low

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

Summary

Removed section about Lambda Concurrency configuration

Security assessment

Removal of non-security-related tuning guidance. No impact on security controls or vulnerability management.

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 347667406..251ba73b4 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 tuningLambda Concurrency
+CloudFront distribution domain nameGuidance on how to implement/enable TLS between CloudFront and ALBFirewall rulesContainer tuning
@@ -50,4 +49,0 @@ 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.
-