Lambda runtimes deprecation divergences when change location.

Based on the available information, I cannot confirm the exact current dates for Node.js 16.x runtime deprecation in AWS Lambda, as there appears to be inconsistency between different language versions of the documentation.

What I can confirm is that AWS has been making changes to their runtime deprecation schedules. According to recent information, AWS has delayed the block-function-create and block-function-update dates beyond the usual 30 and 60 days after deprecation for some runtimes. This change was made in response to customer feedback to provide more time for upgrading functions.

For example, there was a noted change for Node.js 16 where the "Block function update" date was previously March 31, 2025, but was later changed to November 1, 2025. Similar date changes have been observed for other runtimes as well.

Since there's a discrepancy between the English and Portuguese documentation, I recommend:

1. Referring to the most recent English version of the AWS Lambda documentation as it's typically updated first
2. Contacting AWS Support directly for the most accurate and up-to-date information about Node.js 16.x deprecation dates
3. Checking the AWS Health Dashboard for notifications about runtime deprecations

For planning purposes, it's always best to migrate to a supported runtime well ahead of any deprecation dates to ensure continued security updates and technical support for your Lambda functions.
Sources
Node.js 16 Runtime Deprecation Date Change | AWS re:Post
Lambda runtimes - AWS Lambda
.NET 6 AWS Lambda Deprecation Dates Changed | AWS re:Post
Leverage Amazon Q to upgrade Lambda runtime functions | AWS Cloud Operations Blog