AWS Lambda函数Node.js 6.10停服，如何升级至8.10版本？

Absolutely! You can directly select Node.js 8.10 from the Lambda runtime options since it’s already available in the console. That said, it’s smart to run quick compatibility checks first to avoid breaking your functions. Here’s a straightforward, step-by-step guide to get you through the upgrade:

Step 1: Backup your function first (critical!) #

• Export your Lambda function code as a ZIP file from the console, or use this AWS CLI command to grab the code:

  aws lambda get-function --function-name YOUR_FUNCTION_NAME --query 'Code.Location' --output text > function-backup.zip
  

• Jot down any custom environment variables, attached IAM roles, or trigger configurations—you’ll want these handy if you need to roll back later.

Step 2: Update the runtime in the Lambda Console #

• Open the AWS Lambda Console and navigate to your target function.
• Switch to the Configuration tab, then locate the Runtime settings section.
• Click Edit, then select Node.js 8.10 from the Runtime dropdown menu.
• Hit Save to apply the runtime change.

Step 3: Test the upgraded function thoroughly #

• Go to the Test tab, pick an existing test event (or create one that matches real-world usage of your function).
• Click Test and review the execution result. If there are errors, head to the Monitor tab and check CloudWatch logs to debug issues like missing dependencies or syntax breaks.

Step 4: Validate code and dependency compatibility #

• Node.js 8.10 introduced better support for async/await and updated some core APIs. If your 6.10 code uses deprecated methods (like older Buffer constructors), you might need small tweaks to fix those.
• If you rely on third-party npm packages, confirm they support Node.js 8.10. Test installing and running your code locally with Node.js 8.10 (use nvm to switch versions easily) before fully deploying to Lambda.

Step 5: Roll out to all functions (if you have multiple) #

• Start with a non-critical function first to validate the process works without issues. Once you’re confident, repeat the steps for all remaining Node.js 6.10 functions.

Quick heads-up #

While Node.js 8.10 is a valid upgrade path from 6.10, note that 8.10 is also end-of-life now. But if your requirement is specifically to move from 6.10 to 8.10, this process will work perfectly.

内容的提问来源于stack exchange，提问作者Srk