A Lambda that calls a slow legacy mainframe still uses the default 3-second timeout and fails mid-transaction even though the business allows 45 seconds. What should the developer do?
Select an answer to reveal the explanation.
Short Explanation
If the mainframe needs up to 45 seconds on the phone, don't hang up at three. Align the Lambda timeout with the real SLA—and don't blindly max every function at 15 minutes or fake success. Retries on a too-short timeout just restart the same mid-transaction failure.
Full Explanation
Configure Lambda timeout to cover legitimate downstream latency within the business SLA while avoiding unnecessarily long timeouts that delay failure detection. The default three seconds is often too short for legacy integrations. Maxing every function at 15 minutes or returning fake success masks problems rather than matching the workload.