Lambda Using Deprecated Runtime
The runtime no longer receives security patches, and AWS will eventually block updates to the function and then its invocations.
Free to start. No card. The playground just needs your work email.
AWS
Found, explained, handed over.
Where the estate departs from your policies, frameworks and tagging rules.
Detect
ZopNight checks this automatically across AWS, with read-only access to the account.
Explain
Every finding says exactly what to change: Upgrade Lambda runtime.
Fix
The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.
- Applies to
- Lambda Functions on AWS
- The fix, by hand
- Lambda → Functions → the resource → Code/Runtime. Note the deprecated runtime (e.g. nodejs16.x, python3.8).
- Pick the target current runtime. Typically the latest LTS version supported by Lambda (e.g. python3.12, nodejs20.x).
- Test in staging: deploy a copy of the function with the new runtime + your existing code; run integration tests for library compatibility (boto3 / aws-sdk versions ship inside the runtime).
- Update production: Lambda → the resource → Edit runtime settings → pick new runtime → Save.
- Watch CloudWatch logs + Errors metric for 48h. Python f-string syntax changes, Node ESM/CJS shifts, etc. are common breakers.
These are the steps the finding carries in the product.
- Category
- Compliance. Configuration drift from best practice: public access, missing MFA, unencrypted storage, deprecated runtimes.
- Where it appears
- The Compliance tab of Recommendations, with every affected resource listed.
- Rule ID
RC-155- Full reference
Related checks
See the compliance findings in your account.
Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.
Prefer to talk it through first? Book 20 minutes with the team.
- $30M+annualised cloud spend under management
- 550K+resources tracked since launch
- 20-60%off the bill in the first month
- SOC 2Type II report, plus ISO 27001
Figures published on zop.dev.