Hi @luong-komorebi - thanks for reporting.

While we further look into it, can you share your SDK minimal repro code with Next.js? Here's my quick repro attempt with 3.629.0 and it works as expected:

npx create-next-app next-aws-sdk-repro
cd next-aws-sdk-repro
npm install @aws-sdk/[email protected] @aws-sdk/[email protected]

SDK

import { S3Client, GetObjectCommand } from "@aws-sdk/client-s3";
import { getSignedUrl } from "@aws-sdk/s3-request-presigner";

const s3Client = new S3Client({
  region: "us-west-1",
  credentials: {
    accessKeyId: "ACCESS_KEY_ID",
    secretAccessKey: "SECRET_ACCESS_KEY",
  },
});

export default async function handler(req, res) {
  try {
    const command = new GetObjectCommand({
      Bucket: "BUCKET_NAME",
      Key: "OBJECT_KEY",
    });

    const signedUrl = await getSignedUrl(s3Client, command, {
      expiresIn: 3600,
    });

    res.status(200).json({ signedUrl });
  } catch (error) {
    console.error(error);
    res.status(500).json({ error: error.message });
  }
}

Best,
John

@aBurmeseDev sorry I could not share the original source code and I could not also reproduce this in a fresh nextjs project with some similar next.config.js setting so I am not sure what was causing the error

Please feel free to close this issue.
Meanwhile I fix things on my side by adding

serverComponentsExternalPackages: [
  "@aws-sdk/client-s3",
  "@aws-sdk/s3-request-presigner"
]

like some suggestions on the internet and it works.
It is weird that I did not have to do this on earlier versions of aws-sdk/client-s3
as well as nextjs has already pre-configured this on their side https://github.com/vercel/next.js/blob/0bf7f52db8b2c1e0b13d332de105fab645240e1e/packages/next/src/lib/server-external-packages.json#L2

I'm experiencing the same issue right now. Same problem on .629 and latest .637

Same issue for me, reverting to 3.623.0 worked as a temporary fix.

Add this to your nextjs config:

// Nextjs 14
const nextConfig = {
  experimental: {
    serverComponentsExternalPackages: ['@aws-sdk/client-s3', '@aws-sdk/s3-request-presigner']
  }

Notice that serverComponentsExternalPackages will become stable in next.js 15 and will be renamed to serverExternalPackages.

// Nextjs 15
const nextConfig = {
  serverExternalPackages: ['@aws-sdk/client-s3', '@aws-sdk/s3-request-presigner'],
}

Links to the docs:
https://nextjs.org/docs/app/api-reference/next-config-js/serverExternalPackages

@magoz I already have that in my config, and it did not fix anything. Reverting to .623 worked.

@kasperaamodt, double-check that you add the serverComponentsExternalPackages within the experimental object. It wasn't working for me either until I realized.

In any case, I agree that this must be fixed.

@magoz Ahh, sorry i did not catch that! My bad. That fixed it.

Ideally, we should not have to config the serverComponentsExternalPackages or serverExternalPackages manually,
because since this commit vercel/next.js@a06775c, next has already excluded aws client s3 and s3-request-presigner by default. I am still unable to figure out why this happens

same here with '@aws-sdk/middleware-sdk-s3', '@aws-sdk/client-s3', '@aws-sdk/s3-request-presigner' packages