Time to Bail · Boarding pass
Act. You can stay.
Ruby 3.3 on Lambda is deprecated March 31, 2027. Updates to these functions are blocked from August 31, 2027.[1]
Act means: change a setting or plan before the date. You can stay.
AWS Lambda Ruby 3.3 runtime deprecated March 31, 2027
AWS deprecates the Ruby 3.3 runtime (ruby3.3) for Lambda on March 31, 2027. After that it may get no more security patches. Creating functions is blocked from July 29, 2027, and updating them from August 31, 2027.
One email with the first steps. Nothing else.
Or add the date to your calendar: Apple or Outlook (.ics) · Google Calendar
Tick steps as you go. Your progress stays in this browser.
Filter by runtime in the Lambda console, or list ruby3.3 functions with the AWS CLI in each region.
Switch to ruby3.4 or ruby4.0. Rebuild layers and packages for it.
Test each function on the new runtime. After August 31, 2027 you cannot update a ruby3.3 function.
One email with the first steps. Nothing else.
Or add the date to your calendar: Apple or Outlook (.ics) · Google Calendar
| Deprecation date | March 31, 2027[1] |
|---|---|
| Runtime | ruby3.3 (Ruby 3.3 on Amazon Linux 2023)[1] |
| Creating new functions blocked | July 29, 2027[1] |
| Updating functions blocked | August 31, 2027[1] |
| After deprecation | AWS may stop security patches and technical support; you can still invoke your functions[1] |
| In the Lambda console | From the deprecation date you cannot create or update these functions there; the AWS CLI, AWS SAM and CloudFormation still work until the blocks[1] |
| Once updates are blocked | You cannot go back to the deprecated runtime[1] |
| How AWS tells you | Email and Health Dashboard notices at least 180 days before; Trusted Advisor lists the functions[1] |
| Can the dates change? | Yes. AWS says the dates are for planning and subject to change[1] |
| How to list them | aws lambda list-functions --function-version ALL --region us-east-1 --query "Functions[?Runtime=='ruby3.3'].FunctionArn" (once per region)[2] |
| Newer Ruby runtimes | ruby3.4 until March 31, 2028; ruby4.0 until March 31, 2029[1] |
| Functions on Ruby 3.3 | May get no security patches after March 31, 2027; no updates from August 31, 2027[1] |
In the Lambda console you can no longer create or update functions on ruby3.3. The AWS CLI, AWS SAM and CloudFormation still work until the blocks. Your functions keep running, but AWS may stop security patches.
ruby3.3 functions: aws lambda list-functions --function-version ALL --region us-east-1 --output text --query "Functions[?Runtime=='ruby3.3'].FunctionArn". Run it in each region.ruby3.4 or ruby4.0. Test it before you ship.Source: [1] Lambda runtimes (Amazon Web Services) · [2] Retrieve data about Lambda Event Functions that use a deprecated runtime (Amazon Web Services)
Check it yourself. Every fact above links here.
Time to bail on Lambda functions on Ruby 3.3? Act. You can stay. Ruby 3.3 on Lambda is deprecated March 31, 2027. Updates to these functions are blocked from August 31, 2027.
On our scale this is Act: change a setting or plan before the date. You can stay.
AWS deprecates the Ruby 3.3 runtime (ruby3.3) for Lambda on March 31, 2027. After that it may get no more security patches. Creating functions is blocked from July 29, 2027, and updating them from August 31, 2027.
Here are the facts we checked:
You can stay on AWS Lambda. You have to change a setting or plan before the date.
Leaving is a choice here, not a must.
Amazon Web Services is the main source for this page. AWS Lambda has not said more than what is listed here. If a fact is not on this page, we do not know it yet.
Functions on Ruby 3.3: May get no security patches after March 31, 2027; no updates from August 31, 2027.
The date to remember is March 31, 2027. Make the change before then.
A few tips:
If the change affects your members or team, send one short email. Say what changes for them and when. Put the most important line first.
If there is a date, send a short reminder a few days before it. Keep a copy of the list you sent it to.
Listed for convenience. Not ranked. Not paid. These names come up in threads and reviews; that does not show where people moved.
Before you pay, check the price page of each tool yourself. Prices change, and we only list what our sources say.
No questions collected yet.
Thanks.
Run SaaS spend at work? Get these changes before the invoice
Arrivals · for builders
People on Lambda functions on Ruby 3.3 can stay if they make the change. Some would rather leave. Get the playbook for this change, and list your product here.
Listing is free. An editor checks it. Not ranked. Not paid.
One email when we publish a checked change in the category you pick. No account needed.
One email on Mondays: the gates in the next 14 days, with the first step for each.