During open enrollment, API clients receive HTTP 429 responses while a Lambda function’s reserved concurrency is set far below actual demand. Code errors are not appearing in logs. What is the likely diagnosis and fix direction?
Select an answer to reveal the explanation.
Short Explanation
429s with quiet error logs often mean the bouncer—reserved concurrency—turned people away, not that the code crashed. Lift the concurrency cap carefully for open enrollment instead of deleting logs or faking success in the browser.
Full Explanation
Lambda returns throttling responses when concurrent executions exceed reserved or account concurrency limits; that differs from unhandled exceptions in function code. Remediation is to right-size reserved concurrency or request limit increases based on load testing—not to suppress logs or skip server-side confirmation.