InvalidParameterValueExcexption - runtime parameter of nodejs is no longer supported for AWS Lambda functions

Open

#9 opened on Feb 23, 2017 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 2/5
Estimated time: 1-3 hours
Newbie friendliness: 30/100

Issue type: Bug
Clarity: Mostly clear
Activity status: Stale
Tech stack: aws, node.js
Domain: backend, cloud

Research direction

Start with the fab setup entry point and trace the AWS Lambda create-function command shown in the issue to where its --runtime value is configured. Check the supported Node.js runtime value, update the configuration, and rerun fab setup or the displayed AWS command to confirm the function can be created.

Written by the indexing model from the issue text.

Description

I recieved the following error after running fab setup:
gg

Fatal error: local() encountered an error (return code 255) while executing 'aws lambda create-function    --function-name ecs-worker-launcher    --zip-file fileb://./ecs-worker-launcher.zip    --role arn:aws:iam::622674099863:role/codeguru-Lambda-Execution-Role    --handler ecs-worker-launcher.handler    --runtime nodejs    --region us-east-1    --profile codeguru    --output json'

Aborting.

I tried running the failed command and failed again:

$ aws lambda create-function    --function-name ecs-worker-launcher    --zip-file fileb://./ecs-worker-launcher.zip    --role arn:aws:iam::622674099863:role/codeguru-Lambda-Execution-Role    --handler ecs-worker-launcher.handler    --runtime nodejs    --region us-east-1    --profile codeguru    --output json

An error occurred (InvalidParameterValueException) when calling the CreateFunction operation: The runtime parameter of nodejs is no longer supported for creating or updating AWS Lambda functions. We recommend you use the new runtime (nodejs4.3) while creating or updating functions.

It seems like this project uses a no longer supported api for lambda functions. How can I fix this?

Dominant language: POV-Ray SDL
Stars: 293
Forks: 46
PR merge metrics: No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

Use `charmlibs.interfaces.oauth` instead of deprecated `hydra.oauth` Open

enhancement

Difficulty 2/5 1-3 hours Newbie friendliness 70/100

canonical/paas-charm#368 · 1 comment · Opened Sep 23, 2026
Model API: distributable field returns false even when "Allow Distributed Inference Across Workers" is checked Open

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

gpustack/gpustack#6275 · Opened Sep 23, 2026
attachment_urls parameter descriptions do not state that the value must be a reference Open

tech debt

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

epam/ai-dial-quickapps-backend#579 · Opened Sep 23, 2026
fix: in-app bug reports carry the user-report label — ADR 0143's P1 door never fires Open

area:workflow bug ready-for-agent

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

fil-donadoni/tolaria#4409 · Opened Sep 23, 2026
PHP warning in document.php after importing a saved header template in Elementor 4.3.0 Open

status/awaiting_triage

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

elementor/elementor#37396 · Opened Sep 23, 2026

More Backend & API Design issues