fix(lambda): show received ephemeral storage size instead of [object Object]

[sanyamk23]

The out-of-range error interpolated the Size object directly into the message. Size has no toString(), so the value rendered as [object Object] and gave no indication of what was actually passed. Convert to mebibytes in the message, matching the conversion already performed by the range check on the line above.

Fixes #38621

[aws-cdk-automation]

(This review is outdated)

✅ Updated pull request passes all PRLinter validations. Dismissing previous PRLinter review.

[lpizzinidev]

Ty for the contribution! However, the change is no longer necessary after #38662

[maintainer-for-aws]

Automated review

A maintainer will still review this — treat the notes below as a starting point.

This PR improves the EphemeralStorageOutOfRange validation error in the Lambda Function construct: when ephemeralStorageSize is out of the 512–10240 range, the message now interpolates ephemeralStorageSize.toMebibytes() MiB instead of the raw Size object (which rendered as [object Object]). The validation logic, error code, and public API are unchanged. A unit test is tightened to assert the new message text, and a new integ test with snapshot is added.

The fix is low-risk and message-only: toMebibytes() is called inside a branch already guarded by !isUnresolved(), so there is no token or undefined risk, and the tightened unit test discharges the coverage the change owes. The one point worth a look is whether the added integ test — which exercises only a valid path and cannot reach the changed error path — earns its new snapshot for a cosmetic fix.

🔴 0 blocking · 🟡 0 recommended · ⚪ 1 optional

Files with findings (1)

File	Findings
packages/@aws-cdk-testing/framework-integ/test/aws-lambda/test/integ.lambda-ephemeral-storage-validation.ts	⚪ 1

---

Generated automatically. React 👍 or 👎 to tell us whether this review helped, so we can improve these reviews.

[maintainer-for-aws]

See the review summary comment for the overview; the notes below are inline.

[maintainer-for-aws]

⚪ Optional — This new integ test exercises only a valid ephemeral storage size (Size.mebibytes(1024)), so it never touches the out-of-range error path this change actually fixes — and it cannot, since an out-of-range value throws at synth time and can never be deployed. The behavior under change is a validation message string, which the tightened unit test already covers and catches regressions for. The test's own comment references an "out-of-range check" the test does not trigger, and the result is a new synthesized snapshot for a cosmetic message change (INTEGRATION_TESTS.md).

Suggested change: Consider dropping the integ test and its snapshot and relying on the unit-test update alone, since the changed error string is only coverable at the unit level. If the intent is genuinely to add first-time deploy coverage for ephemeralStorageSize, keep the test but update the comment to state that goal rather than referencing an out-of-range check it never triggers.

[github-actions]

Comments on closed issues and PRs are hard for our team to see.
If you need help, please open a new issue that references this one.