A Lambda function reading a stream sees throttling. What is a likely fix?
Why A is the answer
Adjust batch size and concurrency
Batch size and concurrency control how consumers keep up.
In detail
- Batch size and concurrency control how Lambda reads.
- Test the settings at peak volume.
Use case
An illustrative scenario, not a real incident.
A function falls behind at peak. Tuning batch size and concurrency lets it keep up.
See it in different ways
sequenceDiagram participant P as Producer participant K as Kinesis Data Streams participant A as Consumer A participant B as Consumer B P->>K: Records K->>A: Reads from its own position K->>B: Reads from its own position A->>A: Processes idempotently
flowchart LR S0["Throttling appears"] --> S1["Review batch size"] --> S2["Adjust concurrency"] --> S3["Watch metrics"]
Key point: Batch size and concurrency control consumers.
Why the other options are wrong
- B. Increase the stream's retention period
- Longer retention does not fix throttling.
- C. Move the stream to a new account
- A new account does not fix it.
- D. Enable encryption on the stream
- Encryption does not fix it.