timetobail
My stack

Playbook for makers · Forced move · free while in beta

Act

AWS Lambda Ruby 3.3 runtime deprecated March 31, 2027

Readers can stay on AWS Lambda: they change a setting or plan. Help the ones who would rather leave.

164 days left · March 31, 2027 · Public page

Low switching pressure29/100

An estimate from the deadline, cost, discussion and need to move. It is not a product rating.

What goes into it

Confidence: medium.

deadline8/30
money14/25
attention0/25
audience0/12
force7/8
  • Hard deadline in 164 days.
  • The change is forced: it reaches users even if they wait.

  1. 1 Related discussions

    Only threads tied to this event that talk about leaving, moving or prices. Saved, not live. Check the date and read the thread before replying.

    No live threads yet.

  2. 2 What people ask

    No common questions yet.

  3. 3 Reply templates

    Answer the question first. Link only if it helps. Always keep the disclosure line. Never post the same text twice.

    Helpful first
    Sorry you have to deal with this. You can stay on AWS Lambda. Here is what to change before March 31, 2027:

1. Find functions on Ruby 3.3. Filter by runtime in the Lambda console, or list ruby3.3 functions with the AWS CLI in each region.
2. Move to a newer runtime. Switch to ruby3.4 or ruby4.0. Rebuild layers and packages for it.
3. Test and deploy before the blocks. Test each function on the new runtime. After August 31, 2027 you cannot update a ruby3.3 function.

If they would rather leave, describe a verified way <your product> can help: <your link>
[Disclosure: I build <your product>.]
    Short answer
    You have until March 31, 2027. You can stay on AWS Lambda. First: find functions on Ruby 3.3. Then move to a newer runtime.
Happy to help if you get stuck.
[Disclosure: I build <your product>.]

  4. 4 Switch-page builder

    Create a draft “Switch from AWS Lambda” page. Add your product, review every claim, then copy HTML or Markdown. Your product claims need your own evidence.

    • Add your product name to replace “Your product”.
    Preview

    Switch from AWS Lambda to Your product

    Lambda functions on Ruby 3.3: a change is due by March 31. You can stay on AWS Lambda. If you would rather leave, here is how to move to Your product.

    What changes at AWS Lambda

    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.

    • Deprecation date: March 31, 2027 (Amazon Web Services)
    • Runtime: ruby3.3 (Ruby 3.3 on Amazon Linux 2023) (Amazon Web Services)
    • Creating new functions blocked: July 29, 2027 (Amazon Web Services)
    • Updating functions blocked: August 31, 2027 (Amazon Web Services)
    • After deprecation: AWS may stop security patches and technical support; you can still invoke your functions (Amazon Web Services)
    • 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 (Amazon Web Services)
    • Once updates are blocked: You cannot go back to the deprecated runtime (Amazon Web Services)
    • How AWS tells you: Email and Health Dashboard notices at least 180 days before; Trusted Advisor lists the functions (Amazon Web Services)
    • Can the dates change?: Yes. AWS says the dates are for planning and subject to change (Amazon Web Services)
    • How to list them: aws lambda list-functions --function-version ALL --region us-east-1 --query "Functions[?Runtime=='ruby3.3'].FunctionArn" (once per region) (Amazon Web Services)
    • Newer Ruby runtimes: ruby3.4 until March 31, 2028; ruby4.0 until March 31, 2029 (Amazon Web Services)
    • Functions on Ruby 3.3: May get no security patches after March 31, 2027; no updates from August 31, 2027 (Amazon Web Services)

    You can stay on AWS Lambda if you make the change. This page is for people who would rather leave.

    What Your product gives you

    Write two or three short lines here. Say what Your product does, who it is for, and what it costs. Use only facts you can show.

    How to move from AWS Lambda to Your product

    1. Save what you need from AWS Lambda. Keep a copy before you cancel anything.
    2. Import into Your product. Say which files you accept and how long an import takes.

    Tell readers the key date: March 31, 2027.

    Questions people ask

    If Your product has a direct answer to one of these, add it here. Keep it short and true.

    How to help new users settle in

    Send one short email. Say what changed, where to find you now, and what they need to do. 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.

    Sources

  5. 5 Search ideas to validate

    suggested, not measured Phrases people may search when a tool changes like this. We have no search volume data for them.

    • lambda functions on ruby 3.3
    • aws lambda alternative
    • aws lambda alternatives
    • aws lambda export
    • how to leave aws lambda
    • switch from aws lambda
    • aws lambda migration
    • aws lambda migration 2027