- Newest
- Most votes
- Most comments
When facing a "Runtime.Unknown" error after a Lambda runtime update, this indicates a compatibility issue between your function and the new runtime version.
To move forward, you have a few options:
-
Investigate the specific error: The "Runtime.Unknown" error is quite generic. Check the complete CloudWatch logs for more detailed error messages that might help identify the root cause.
-
Test incrementally: Since you've already reverted to v96 successfully, you could try updating to intermediate versions between v96 and v101 to identify which specific version introduces the issue.
-
Review dependencies: Although you've tested with Python 3.9.23 locally, Lambda's runtime environment might differ. Check if you're using any libraries with native extensions (like psycopg2) that might need to be recompiled or updated for the new runtime.
-
Update your runtime management configuration: Consider changing from Auto mode to Function update mode, which would allow you to control when runtime updates are applied to your function.
Regarding the runtime version changelog, AWS Lambda doesn't typically publish detailed changelogs for specific runtime version updates. The runtime versions include security patches, bug fixes, and performance improvements, but detailed information about what's in v101 specifically isn't publicly available.
If you need to continue using the latest runtime version, you might need to update your function code or dependencies to be compatible with the changes in v101. Alternatively, you can continue using v96 in Manual mode until you're ready to update, though it's generally recommended to use the latest runtime version for security and performance benefits.
Sources
Troubleshoot Lambda function runtime version errors | AWS re:Post
Learn the differences between Lambda runtime version and runtime identifier | AWS re:Post
Identifying Lambda runtime version changes - AWS Lambda
Rolling back a Lambda runtime version - AWS Lambda
Relevant content
asked a year ago
asked 8 months ago
- AWS OFFICIALUpdated 6 months ago
