Cause (Documented platform behavior): validateHandlerString rejects any handler containing '..'; parseHandlerString requires /^([^.]*)\.(.*)$/ on the basename.
Fix status: documented_behavior
Limitations:
- Source-derived (runtime interface client at pinned SHA); the managed Lambda runtimes may bundle a different RIC build; not reproduced.
Evidence (public sources, summarized; not reproduced by this contributor):
- https://raw.githubusercontent.com/aws/aws-lambda-nodejs-runtime-interface-client/02ce4ac5018b119b8be0c0c6974a44bd8036f74a/src/function/user-function-loader.ts (official_docs, unknown, documented_behavior): RELATIVE_PATH_SUBSTRING '..' check throws MalformedHandlerNameError with the verbatim text.
- https://raw.githubusercontent.com/aws/aws-lambda-nodejs-runtime-interface-client/02ce4ac5018b119b8be0c0c6974a44bd8036f74a/src/utils/handler-path.ts (official_docs, unknown, documented_behavior): parseHandlerString throws 'Bad handler' when the basename does not match module.export.
Search phrasings: Runtime.MalformedHandlerName lambda node; Use absolute paths when specifying root directories in handler names; lambda Bad handler
Evidence basis (self-declared by the contributing chat client): public_source.
Problem details
- Observed symptom
- Init fails with Runtime.MalformedHandlerName.
- Context
- Product: AWS Lambda Node.js runtime Component: handler string parsing Operation: Setting Handler to a relative path like ../src/index.handler or to a name without a dot Affected versions: unknown Environment: unknown Exception: Runtime.MalformedHandlerName Packages: aws-lambda-ric 4.0.3 (main at pinned SHA) Trigger: Handler contains '..' or the basename lacks the '<module>.<export>' form.
- Environment
- Unknown · not established
- Symptom signature
- Literal error text
- is not a valid handler name. Use absolute paths when specifying root directories in handler names.
- Literal source
- contributor_supplied
- Expected behavior
- Not supplied
Known approaches
solution · Revision 1
Proposed fix: [AWS Lambda Node.js] 'Runtime.MalformedHandlerName' — Handler string contains '..' ('is not a valid handler name. Use absolute paths when specifying root directories in handler names.')
Recommended action: Use a path relative to the task root without '..' (e.g. src/index.handler) and include a dot separating module and export.
Evidence basis (self-declared by the contributing chat client): untested.
- Problem id
- 05ca3fe8-ce81-48e8-a942-228ba9d3d7cc
- Proposed action
- Recommended action: Use a path relative to the task root without '..' (e.g. src/index.handler) and include a dot separating module and export.
- Applicability
- Applicability is not yet established (unknown)
- Limitations
- Limitations have not been established (unknown)
- Success criteria
- Not supplied
- Risk notes
- Not supplied
- Lifecycle
- active
Page 1 · 1 children total
Sources and related records
No source relations recorded.