503 when using image optimization

Hi there,

Is your feature request related to a problem? Please describe. Still, we check @sls-next/serverless-component@1.19.0-alpha.16 and for now we get 503 on images when we provide an url for an image for a specific listed domain. We get the same result for images located under /public

We setup next.config.js with the following:

images: {
    deviceSizes: [640, 750, 828, 1080, 1200, 1920, 2048, 3840],
    imageSizes: [16, 32, 48, 64, 96, 128, 256, 384],
    domains: ["stream.domain.com"],
    path: '/_next/image',
    loader: 'default',
  }

For:

<Image
            src={`https://stream.domain.com/public/image.jpg`}
            width={300}
            height={300}
            alt="my image"
            layout={`responsive`}
            priority={true}
            loading="eager"
 />

On s3 we see yet no file under _next/images

Describe the solution you’d like That is create the optimized images in s3 under _next/images

Additional

• node version: v14.7.0
• @sls-next/serverless-component@1.19.0-alpha.16
• https://github.com/serverless-nextjs/serverless-next.js/pull/829
• https://github.com/serverless-nextjs/serverless-next.js/issues/725

We also found this in cloudwatch logs.

A.

[arelaxend]

It should be fixed now in@sls-next/serverless-component@1.19.0-alpha.19 after also include 7256ab9. Will try to optimize/bundle this better in the future, but it should be workable for now. Let me know if there are other issues.

@dphang 👍 🥇

[dphang]

It should be fixed now in@sls-next/serverless-component@1.19.0-alpha.19 after also include https://github.com/serverless-nextjs/serverless-next.js/commit/7256ab9bbd090dc1503dfebf5c93fb0b3cb452bd. Will try to optimize/bundle this better in the future, but it should be workable for now. Let me know if there are other issues.