feat(aws): add support for Node.js 24.x runtime

[casperiv0]

First contribution to SST, so let me know if there should be more added here 🙏.

[smorimoto]

I think there are a few other places that should be changed as well:

diff --git i/platform/src/components/aws/function.ts w/platform/src/components/aws/function.ts
index d02d29de2..7f283869d 100644
--- i/platform/src/components/aws/function.ts
+++ w/platform/src/components/aws/function.ts
@@ -311,7 +311,7 @@ export interface FunctionArgs {
    * @example
    * ```js
    * {
-   *   runtime: "nodejs22.x"
+   *   runtime: "nodejs24.x"
    * }
    * ```
    */
@@ -319,6 +319,7 @@ export interface FunctionArgs {
     | "nodejs18.x"
     | "nodejs20.x"
     | "nodejs22.x"
+    | "nodejs24.x"
     | "go"
     | "rust"
     | "provided.al2023"
diff --git i/platform/src/components/aws/ssr-site.ts w/platform/src/components/aws/ssr-site.ts
index a1eb78d44..cab112f7a 100644
--- i/platform/src/components/aws/ssr-site.ts
+++ w/platform/src/components/aws/ssr-site.ts
@@ -230,12 +230,12 @@ export interface SsrSiteArgs extends BaseSsrSiteArgs {
      * ```js
      * {
      *   server: {
-     *     runtime: "nodejs22.x"
+     *     runtime: "nodejs24.x"
      *   }
      * }
      * ```
      */
-    runtime?: Input<"nodejs18.x" | "nodejs20.x" | "nodejs22.x">;
+    runtime?: Input<"nodejs18.x" | "nodejs20.x" | "nodejs22.x" | "nodejs24.x">;
     /**
      * The maximum amount of time the server function can run.
      *

[casperiv0]

Updated, thanks!

[dragonautdev]

This looks great @casperiv0 and super useful 👍

[jamesgibbons92]

this requires being on one of the latest aws provider versions (atleast 7.12.0 I believe) so you can't use this runtime on default sst installation unless you explictly upgrade aws in your provider config. not sure if this is worth mentioning somewhere until the providers are updated in sst

[casperiv0]

this requires being on one of the latest aws provider versions (atleast 7.12.0 I believe) so you can't use this runtime on default sst installation unless you explictly upgrade aws in your provider config. not sure if this is worth mentioning somewhere until the providers are updated in sst

Would it be fine to update the providers directly in SST in this PR? Or are there breaking changes in those updates?

[jamesgibbons92]

6 -> 7 is a major update and contains some breaking changes if I recall so needs to be done carefully

…

On Mon, 1 Dec 2025, 08:32 Casper Iversen, ***@***.***> wrote: *casperiv0* left a comment (anomalyco/sst#6243) <#6243 (comment)> this requires being on one of the latest aws provider versions (atleast 7.12.0 I believe) so you can't use this runtime on default sst installation unless you explictly upgrade aws in your provider config. not sure if this is worth mentioning somewhere until the providers are updated in sst Would it be fine to update the providers directly in SST in this PR? Or are there breaking changes in those updates? — Reply to this email directly, view it on GitHub <#6243 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACQCV6OOSTLASLC2LVVGWW337P4JLAVCNFSM6AAAAACNLYHC7OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTKOJVGI2TGMZZG4> . You are receiving this because you commented.Message ID: ***@***.***>

[AlperSakarya]

@vimtor

[vimtor]

blocked by #5944

[55Cancri]

Thanks for working on this @casperiv0! I wanted to add some additional context that might be useful, especially since this is blocked by #5944.

Relationship with API Gateway Streaming

While researching the Node.js 24 runtime dependency chain, I discovered that a related feature - API Gateway REST API response streaming - was announced by AWS on November 19, 2025 (6 days before Node.js 24 runtime on Nov 25).

Both features share a common blocker: they require updating to recent versions of the Pulumi AWS provider.

Upstream Dependency Timeline

Date	Event
Nov 19, 2025	AWS announces API Gateway REST API streaming
Nov 21, 2025	Terraform AWS Provider v6.25.0 released (includes API Gateway streaming support)
Nov 25, 2025	AWS announces Node.js 24 Lambda runtime
Dec 9, 2025	Pulumi releases @pulumi/aws v7.13.0 (based on Terraform v6.25.0)

• API Gateway streaming: Should be available once chore: upgrade pulumi to 3.210.0 #5944 merges and SST updates to @pulumi/aws v7.13.0+
• Node.js 24 runtime: May require a slightly later Pulumi version (if the nodejs24.x enum was added in Terraform v6.26.0+, which came after v6.25.0)

So #5944 is the key blocker here. Once that's merged, SST will be much closer to supporting both Node.js 24 runtime AND API Gateway streaming - both of which are highly requested.

Just sharing this in case the broader context is helpful!

[mss-dieliko]

Thanks for this nice feature!

Not sure if I may add this here, but what about the fixed node runtime values like here below? Will these runtime versions also be updated?

• sst/platform/src/components/aws/nextjs.ts

  Line 711 in 5bbaefb

  runtime: "nodejs20.x" as const,

• sst/platform/src/components/aws/nextjs.ts

  Line 848 in 5bbaefb

  runtime: "nodejs20.x",

• sst/platform/src/components/aws/nextjs.ts

  Line 930 in 5bbaefb

  runtime: "nodejs20.x",

There is currently no way to override this with configurations/transforms if I'm not mistaken?

[vimtor]

i'll be reviewing this soon now that the pulumi pr has landed

[guylr]

i'll be reviewing this soon now that the pulumi pr has landed

Thanks for this nice feature!

Not sure if I may add this here, but what about the fixed node runtime values like here below? Will these runtime versions also be updated?

* https://github.com/anomalyco/sst/blob/5bbaefb153ca7e169699b6397b148d4eef14b7f1/platform/src/components/aws/nextjs.ts#L711

* https://github.com/anomalyco/sst/blob/5bbaefb153ca7e169699b6397b148d4eef14b7f1/platform/src/components/aws/nextjs.ts#L848

* https://github.com/anomalyco/sst/blob/5bbaefb153ca7e169699b6397b148d4eef14b7f1/platform/src/components/aws/nextjs.ts#L930

There is currently no way to override this with configurations/transforms if I'm not mistaken?

Worth looking at this as well if possible. Node.js 20.x in Lambda reaches end-of-life on April 30, 2026