Using "warm" with sst.aws.Astro breaks lambda handler

Hello! I have an sst ion stack that contains an Astro site, and I tried to enable "warm" for the site:

const astro = new sst.aws.Astro("AstroSite", {
  domain: astroDomain,
  path: "packages/astro-site",
  warm: 1
});

Without the "warm" property, the site deploys fine and is reachable through the astroDomain.

But when I change to warm: 1, I get this error when trying to hit the same url:

This results in a 502 Bad Gateway response from cloudfront that's in front of the astro function.

It also seems that the Runtime configuration of the lambda changes if I inspect in in the AWS console ui, Handler changes from packages/astro-site/dist/server/entry.handler to packages/astro-site/dist/server/server-index.handler.

My astro.config.mjs:

import { defineConfig } from "astro/config";
import tailwind from "@astrojs/tailwind";
import aws from "astro-sst";
import preact from "@astrojs/preact";

// https://astro.build/config
export default defineConfig({
  output: "server",
  adapter: aws(),
  integrations: [tailwind({ applyBaseStyles: false }), preact()]
});

Dependencies:

sst cli: 0.0.393
sst node module: 3.0.32
astro: 4.9.2
astro-sst: 2.42.0

sst / ion

Using "warm" with sst.aws.Astro breaks lambda handler #485