amplify-js: Amplify Causing Errors With Next 12 middleware

Before opening, please confirm:

I have searched for duplicate or closed issues and discussions.
I have read the guide for submitting bug reports.
I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

JavaScript Framework

Next.js

Amplify APIs

Authentication

Amplify Categories

auth

Environment information

# Put output below this line

Describe the bug

We are working on updating our application up to NextJS 12. In doing so we are interested in moving the authentication check for protected pages to the new middleware feature available in next 12 (link). This code runs on the server before a request is completed. With that in mind, I went about attempting to use withSSRContext to check the users authentication status in the middleware.

import type { NextFetchEvent, NextRequest } from 'next/server';
import { Amplify, withSSRContext } from 'aws-amplify';
import { AwsConfig } from '../../../../../../src/config';

Amplify.configure({ ...AwsConfig, ssr: true });

export const middleware = async (req: NextRequest, ev: NextFetchEvent) => {
  console.log('req', req);

  const { Auth } = withSSRContext({ req: req });
  return new Response('Hello World!');
};

As you can see above, I didn’t get too far before this already broke the app. It seems that something underlying is attempting to use window which of course is not present on server. This looks to be happening in Reachablility

Expected behavior

Authentication is checked in the same manner it would be for getServerSideProps

Reproduction steps

In a next 12 application. place a _middleware.ts or _middleware.js file in one of your page directories. In that middleware file, simply import Amplify and that should be enough to draw out the exception.

Code Snippet

import type { NextFetchEvent, NextRequest } from 'next/server';
import { Amplify, withSSRContext } from 'aws-amplify';
import { AwsConfig } from '../../../../../../src/config';

Amplify.configure({ ...AwsConfig, ssr: true });

export const middleware = async (req: NextRequest, ev: NextFetchEvent) => {
  console.log('req', req);

  const { Auth } = withSSRContext({ req: req });
  return new Response('Hello World!');
};

Log output

// Put your logs below this line

aws-exports.js

No response

Manual configuration

No response

Additional configuration

No response

Mobile Device

No response

Mobile Operating System

No response

Mobile Browser

No response

Mobile Browser Version

No response

Additional information and screenshots

No response

About this issue

Original URL
State: closed
Created 3 years ago
Reactions: 52
Comments: 62 (19 by maintainers)

Most upvoted comments

@abdallahshaban557 From me and it looks like many of the folks following this I believe the main use case is to manage auth through middleware so that certain Next.js routes can be protected for logged-in users or for specific user groups.

+15

jerocosio on Mar 29, 2023

Hello everyone, we are currently exploring what it would take for our Auth category for Amplify to function consistently with NextJS 12 Middleware. We will update this issue when we have more feedback!

+12

abdallahshaban557 on May 13, 2022

I had the same problem and next-fortress didn’t quite do that trick for me, but I was able to take some of their code to create the solution below.

// _middleware.js
import { NextResponse } from 'next/server';
import { decodeProtectedHeader, importJWK, jwtVerify } from 'jose';

// Middleware that prevents unauthenticated users from accessing protected resources
async function handler(req) {
  const url = req.nextUrl.clone();

  try {
    // Define paths that don't require authentication
    const unauthenticatedPaths = [
      '/',
      '/login',
      '/password-reset',
      '/pricing',
      '/signup',
      '/support',
    ];

    // Allow users to continue for pages that don't require authentication
    if (unauthenticatedPaths.includes(url.pathname)) {
      return NextResponse.next();
    } else {
      // Authenticate users for protected resources

      // Cognito data
      const region = process.env.AWS_REGION;
      const poolId = process.env.AWS_COGNITO_USER_POOL_ID;
      const clientId = process.env.AWS_USER_POOLS_WEB_CLIENT_ID;

      // Get the user's token
      const token = Object.entries(req.cookies).find(([key]) =>
        new RegExp(
          `CognitoIdentityServiceProvider\\.${clientId}\\..+\\.idToken`
        ).test(key)
      )?.[1];

      if (token) {
        // Get keys from AWS
        const { keys } = await fetch(
          `https://cognito-idp.${region}.amazonaws.com/${poolId}/.well-known/jwks.json`
        ).then((res) => res.json());

        // Decode the user's token
        const { kid } = decodeProtectedHeader(token);

        // Find the user's decoded token in the Cognito keys
        const jwk = keys.find((key) => key.kid === kid);

        if (jwk) {
          // Import JWT using the JWK
          const jwtImport = await importJWK(jwk);

          // Verify the users JWT
          const jwtVerified = await jwtVerify(token, jwtImport)
            .then((res) => res.payload.email_verified)
            .catch(() => failedToAuthenticate);

          // Allow verified users to continue
          if (jwtVerified) return NextResponse.next();
        }
      }
    }
  } catch (err) {
    console.log('err', err);
  }

  // Send 401 when an unauthenticated user trys to access API endpoints
  if (url.pathname.includes('api')) {
    return new Response('Auth required', { status: 401 });
  } else {
    // Redirect unauthenticated users to the login page when they attempt to access protected pages
    return NextResponse.redirect(`${url.origin}/login`);
  }
}

export default handler;

+12

dyeoman2 on Jul 13, 2023

+1 , being able to use the new NextJS middleware with Amplify Auth without workarounds will be really great.

+11

rodsfreitas on Feb 9, 2022

Hi @Amirbahal - gotcha! Thank you for sharing the details of your use case! Makes total sense on why you would want to do that in Middleware. We are currently working on fixing this issue! We will provide feedback on this issue when it is resolved.

+10

abdallahshaban557 on Sep 21, 2022

Middleware feature is a must have! I can’t afford to put redirect code in every single page And I can’t afford to put the redirect code in client side

I hope this gets supported soon.

+10

Sodj on May 30, 2022

Unresolved since nearly 2 years 😦

p24-max on Sep 27, 2023

We have this on our radar as a feature that we will support as part of our next major version of the Amplify JavaScript library, which is currently in development. We will provide an update when we have an ETA.

abdallahshaban557 on Aug 7, 2023

Hi @Amirbahal - unfortunately, this issue still exists with the Amplify libray for JavaScript. We do not have an exact timeline for fixing this issue - but we will share it here when we do!

abdallahshaban557 on Dec 20, 2022

The developer preview for v6 of Amplify has officially been released with improvements Next.js middleware and much more! Please check out our announcement and updated documentation to see what has changed.

This issue should be resolved within the dev preview and upcoming General Availability for Amplify v6, but let us know with a comment if there are further issues.

cwomack on Oct 3, 2023

@abdallahshaban557 From me and it looks like many of the folks following this I believe the main use case is to manage auth through middleware so that certain Next.js routes can be protected for logged-in users or for specific user groups.

This 100%

ArturoTorresMartinez on Mar 29, 2023

Unfortunately, still no updates on this one. We don’t officially support Next.js 12 and its new features such as middleware yet.

chrisbonifacio on Mar 30, 2022

Very interesting. I ran into the same problem and couldn’t understand why the function for node required a window, but your pursuit has cleared up that question for me.

The sandbox for running Next.js middleware is quite limited in its functionality (probably to ensure the performance of running Edge), so I hope that amplify will change its implementation to one that does not depend on process.versions.

Incidentally, I temporarily work around this problem by decoding the token (JWT) on the cookie directly.

https://github.com/aiji42/next-fortress/blob/main/src/cognito.ts https://github.com/aiji42/next-fortress#control-by-amazon-cognito

aiji42 on Nov 9, 2021

Hi @arnaringig - not yet, we’ve made some progress and have a design in mind, but we believe it will have some breaking changes. We expect this to be part of our next major version. We will provide an update when we have an ETA.

abdallahshaban557 on May 15, 2023

I had the same problem and next-fortress didn’t quite do that trick for me, but I was able to take some of their code to create the solution below.

// _middleware.js
import { NextResponse } from 'next/server';
import { decodeProtectedHeader, importJWK, jwtVerify } from 'jose';

// Middleware that prevents unauthenticated users from accessing protected resources
async function handler(req) {
  const url = req.nextUrl.clone();

  try {
    // Define paths that don't require authentication
    const unauthenticatedPaths = [
      '/',
      '/login',
      '/password-reset',
      '/pricing',
      '/signup',
      '/support',
    ];

    // Allow users to continue for pages that don't require authentication
    if (unauthenticatedPaths.includes(url.pathname)) {
      return NextResponse.next();
    } else {
      // Authenticate users for protected resources

      // Cognito data
      const region = process.env.AWS_REGION;
      const poolId = process.env.AWS_COGNITO_USER_POOL_ID;
      const clientId = process.env.AWS_USER_POOLS_WEB_CLIENT_ID;

      // Get the user's token
      const token = Object.entries(req.cookies).find(([key]) =>
        new RegExp(
          `CognitoIdentityServiceProvider\\.${clientId}\\..+\\.idToken`
        ).test(key)
      )?.[1];

      if (token) {
        // Get keys from AWS
        const { keys } = await fetch(
          `https://cognito-idp.${region}.amazonaws.com/${poolId}/.well-known/jwks.json`
        ).then((res) => res.json());

        // Decode the user's token
        const { kid } = decodeProtectedHeader(token);

        // Find the user's decoded token in the Cognito keys
        const jwk = keys.find((key) => key.kid === kid);

        if (jwk) {
          // Import JWT using the JWK
          const jwtImport = await importJWK(jwk);

          // Verify the users JWT
          const jwtVerified = await jwtVerify(token, jwtImport)
            .then((res) => res.payload.email_verified)
            .catch(() => failedToAuthenticate);

          // Allow verified users to continue
          if (jwtVerified) return NextResponse.next();
        }
      }
    }
  } catch (err) {
    console.log('err', err);
  }

  // Send 401 when an unauthenticated user trys to access API endpoints
  if (url.pathname.includes('api')) {
    return new Response('Auth required', { status: 401 });
  } else {
    // Redirect unauthenticated users to the login page when they attempt to access protected pages
    return NextResponse.redirect(`${url.origin}/login`);
  }
}

export default handler;

In nextjs 13 we should retrieve the token in the following way:

const token = req.cookies
        .getAll()
        .find((cookie) =>
          new RegExp(
            `CognitoIdentityServiceProvider\\.${clientId}\\..+\\.idToken`,
          ).test(cookie.name),
        )?.value;

hoquescript on Aug 14, 2023

I have the same issue, anyone know of an alternative to this while a fix is deployed? I just want to get the:

const { Auth } = withSSRContext({ req });

but trying to avoid the getServerSideProps on every single file

ArturoTorresMartinez on Jan 25, 2023

@fernandorosenblit - we’ve made a bit of progress in figuring out what is going on - but we are still early on in our analysis. Will keep this issue updated as we discover more!

abdallahshaban557 on Oct 13, 2022

Thank you for the feedback @Sodj! We understand this is an important feature for developers using NextJS v12.

abdallahshaban557 on Jun 1, 2022

Very interesting. I ran into the same problem and couldn’t understand why the function for node required a window, but your pursuit has cleared up that question for me.

The sandbox for running Next.js middleware is quite limited in its functionality (probably to ensure the performance of running Edge), so I hope that amplify will change its implementation to one that does not depend on process.versions.

Incidentally, I temporarily work around this problem by decoding the token (JWT) on the cookie directly.

https://github.com/aiji42/next-fortress/blob/main/src/cognito.ts https://github.com/aiji42/next-fortress#control-by-amazon-cognito

Thank you for this. It helped become the base of us being able to work around this for now.

bluetoken-luke on Nov 10, 2021

With the release of the latest major version of Amplify (aws-amplify@>6), this issue should now be resolved! Please refer to our release announcement, migration guide, and documentation for more information.

cwomack on Nov 16, 2023

Hi @phstc, same on my side. I also noticed that this method: Auth.currentAuthenticatedUser() is getting a new token all the time, but is not updating the Local Storage or Cookies so I am getting the same error as you ERR_JWT_EXPIRED.

Do you have updates ?

louisthomaspro on Jul 9, 2023

@abdallahshaban557 any update on this?

arnaringig on May 2, 2023

thank you for the encouragement, @harrygreen! We will!

abdallahshaban557 on Apr 1, 2023

Ji @cuginoAle - unfortunately we do not have an update yet. I will get back to you when we are closer to identifying the issue here.

abdallahshaban557 on Jan 12, 2023

I am also looking forward to the update.

rnrnstar2 on Apr 30, 2022

Is there an update available?

lewisvoncken on Apr 28, 2022

@chrisbonifacio any updates / solutions found?

zpg6 on Jan 3, 2022

@aiji42 @dyeoman2 thanks for sharing your solutions. I’m trying to implement them, but I’m getting ERR_JWT_EXPIRED after some time (60 minutes/default ID token expiration). Even if I re-login, it seems the cookie/jwt expiration does not get updated. Did you experience this too?

await jwtVerify(token, await importJWK(jwk)) this is what throws the error.

I can probably extend the ID Token expiration. But I’m concerned about why the re-sign-in does not update it.

phstc on May 25, 2023

Perfect - thank you so much for the feedback @jerocosio and @ArturoTorresMartinez !

abdallahshaban557 on Mar 29, 2023

We are investigating this right now @jimmysafe. We are trying to see if there is a way for us to enable this without causing breaking changes, but it might be the case that a breaking change really is necessary. We are trying our best to resolve this.

Can you please elaborate a bit on the use cases you have for middleware in your app?

abdallahshaban557 on Mar 29, 2023

@abdallahshaban557 does this page: https://aws.amazon.com/about-aws/whats-new/2022/11/aws-amplify-hosting-support-next-js-12-13/ mean that this issue is resolved?

AmirNajariH on Dec 20, 2022

Yes @abdallahshaban557 in a nutshell, my intention was to check the current authenticated user in the middle ware + the path of the request. If the authenticated user has access to the path the request gets fulfilled, else, user gets redirected to a different path. 😃

Amirbahal on Sep 21, 2022

I was able to work around this by switching from Amplify to next-auth. Here is my next-auth cognito config: https://github.com/jetbridge/sst-prisma/blob/master/web/pages/api/auth/[...nextauth].ts

revmischa on Sep 20, 2022

@Amirbahal - we are still investigating how to properly fix this issue. Can you please inform us what is your use case for middleware?

abdallahshaban557 on Sep 20, 2022

Thank you very much for your response. I’ll do this 🥰

donaldpipowitch on May 18, 2022

@abdallahshaban557, thanks for the update. So this means the Amplify team is looking into officially supporting NextJS 12? Or are you just looking at the “Auth in Middleware” part right now? Just asking, because there is also this issue which includes more blockers as far as I know: https://github.com/aws-amplify/amplify-hosting/issues/2343 Does the AWS/Amplify internally discuss how to proceed with Next.js support and updates in the future? I’d be really nice to have a bit more clarification here (e.g. it would also be nice to use NextJS 12 support sooner for people who don’t need middleware; what will be the strategy for v13; will there ever be an AWS-official CDK construct, etc.).

donaldpipowitch on May 18, 2022

+1, would like to see a solution here. At the moment, I’m toying with the idea of saving the id token to a cookie upon login and parsing the token in the middleware. Seems like a hacky alternative to the solution provided in this document.

Instead, I get this:

event - compiled client and server successfully in 292 ms (3660 modules)
wait  - compiling /portal...
event - compiled client and server successfully in 253 ms (3668 modules)
error - node_modules/@aws-amplify/core/lib-esm/Util/Reachability.js (21:0) @ <unknown>
ReferenceError: window is not defined

jacorbello on Jan 8, 2022

I am experiencing this issue as well.

I was able to get withSSRContext working fine in getServerSideProps but I can’t use it with middleware because of no window.

revmischa on Jan 3, 2022

@chrisbonifacio any updates over this ?

yogeshwar607 on Nov 18, 2021

Just switched to NextAuth instead of amplify due to this

viep on Jul 13, 2023

@abdallahshaban557 Next.js outputs warning messages at build time that may be helpful, listing out the Node.js APIs that are unsupported, as well as which packages are using those APIs.

Unsupported APIs:

url
buffer
process.versions

Package:

@aws-amplify/auth@v5.2.1

Expand for full log

./node_modules/@aws-amplify/auth/lib-esm/Auth.js
A Node.js module is loaded ('url' at line 7) which is not supported in the Edge Runtime.
Learn More: https://nextjs.org/docs/messages/node-module-in-edge-runtime

Import trace for requested module:
./node_modules/@aws-amplify/auth/lib-esm/Auth.js
./node_modules/@aws-amplify/auth/lib-esm/index.js

./node_modules/@aws-amplify/auth/lib-esm/OAuth/OAuth.js
A Node.js module is loaded ('url' at line 4) which is not supported in the Edge Runtime.
Learn More: https://nextjs.org/docs/messages/node-module-in-edge-runtime

Import trace for requested module:
./node_modules/@aws-amplify/auth/lib-esm/OAuth/OAuth.js
./node_modules/@aws-amplify/auth/lib-esm/Auth.js
./node_modules/@aws-amplify/auth/lib-esm/index.js

./node_modules/@aws-amplify/auth/lib-esm/OAuth/OAuth.js
A Node.js module is loaded ('buffer' at line 7) which is not supported in the Edge Runtime.
Learn More: https://nextjs.org/docs/messages/node-module-in-edge-runtime

Import trace for requested module:
./node_modules/@aws-amplify/auth/lib-esm/OAuth/OAuth.js
./node_modules/@aws-amplify/auth/lib-esm/Auth.js
./node_modules/@aws-amplify/auth/lib-esm/index.js

./node_modules/@aws-amplify/core/lib-esm/JS.js
A Node.js API is used (process.versions at line: 139) which is not supported in the Edge Runtime.
Learn more: https://nextjs.org/docs/api-reference/edge-runtime

Import trace for requested module:
./node_modules/@aws-amplify/core/lib-esm/JS.js
./node_modules/@aws-amplify/core/lib-esm/index.js
./node_modules/@aws-amplify/auth/lib-esm/Auth.js
./node_modules/@aws-amplify/auth/lib-esm/index.js

./node_modules/@aws-amplify/core/lib-esm/JS.js
A Node.js API is used (process.versions at line: 140) which is not supported in the Edge Runtime.
Learn more: https://nextjs.org/docs/api-reference/edge-runtime

Import trace for requested module:
./node_modules/@aws-amplify/core/lib-esm/JS.js
./node_modules/@aws-amplify/core/lib-esm/index.js
./node_modules/@aws-amplify/auth/lib-esm/Auth.js
./node_modules/@aws-amplify/auth/lib-esm/index.js

./node_modules/@aws-amplify/core/lib-esm/Signer.js
A Node.js module is loaded ('url' at line 7) which is not supported in the Edge Runtime.
Learn More: https://nextjs.org/docs/messages/node-module-in-edge-runtime

Import trace for requested module:
./node_modules/@aws-amplify/core/lib-esm/Signer.js
./node_modules/@aws-amplify/core/lib-esm/index.js
./node_modules/@aws-amplify/auth/lib-esm/Auth.js
./node_modules/@aws-amplify/auth/lib-esm/index.js

./node_modules/@aws-amplify/core/node_modules/@aws-crypto/util/build/convertToBuffer.js
A Node.js API is used (Buffer at line: 8) which is not supported in the Edge Runtime.
Learn more: https://nextjs.org/docs/api-reference/edge-runtime

Import trace for requested module:
./node_modules/@aws-amplify/core/node_modules/@aws-crypto/util/build/convertToBuffer.js
./node_modules/@aws-amplify/core/node_modules/@aws-crypto/util/build/index.js
./node_modules/@aws-amplify/core/node_modules/@aws-crypto/sha256-js/build/jsSha256.js
./node_modules/@aws-amplify/core/node_modules/@aws-crypto/sha256-js/build/index.js
./node_modules/@aws-amplify/core/lib-esm/Signer.js
./node_modules/@aws-amplify/core/lib-esm/index.js
./node_modules/@aws-amplify/auth/lib-esm/Auth.js
./node_modules/@aws-amplify/auth/lib-esm/index.js

./node_modules/@aws-amplify/core/node_modules/@aws-crypto/util/build/convertToBuffer.js
A Node.js API is used (Buffer at line: 9) which is not supported in the Edge Runtime.
Learn more: https://nextjs.org/docs/api-reference/edge-runtime

Import trace for requested module:
./node_modules/@aws-amplify/core/node_modules/@aws-crypto/util/build/convertToBuffer.js
./node_modules/@aws-amplify/core/node_modules/@aws-crypto/util/build/index.js
./node_modules/@aws-amplify/core/node_modules/@aws-crypto/sha256-js/build/jsSha256.js
./node_modules/@aws-amplify/core/node_modules/@aws-crypto/sha256-js/build/index.js
./node_modules/@aws-amplify/core/lib-esm/Signer.js
./node_modules/@aws-amplify/core/lib-esm/index.js
./node_modules/@aws-amplify/auth/lib-esm/Auth.js
./node_modules/@aws-amplify/auth/lib-esm/index.js

./node_modules/@aws-crypto/util/build/convertToBuffer.js
A Node.js API is used (Buffer at line: 8) which is not supported in the Edge Runtime.
Learn more: https://nextjs.org/docs/api-reference/edge-runtime

Import trace for requested module:
./node_modules/@aws-crypto/util/build/convertToBuffer.js
./node_modules/@aws-crypto/util/build/index.js
./node_modules/@aws-crypto/sha256-js/build/jsSha256.js
./node_modules/@aws-crypto/sha256-js/build/index.js
./node_modules/@aws-amplify/auth/lib-esm/OAuth/OAuth.js
./node_modules/@aws-amplify/auth/lib-esm/Auth.js
./node_modules/@aws-amplify/auth/lib-esm/index.js

./node_modules/@aws-crypto/util/build/convertToBuffer.js
A Node.js API is used (Buffer at line: 9) which is not supported in the Edge Runtime.
Learn more: https://nextjs.org/docs/api-reference/edge-runtime

Import trace for requested module:
./node_modules/@aws-crypto/util/build/convertToBuffer.js
./node_modules/@aws-crypto/util/build/index.js
./node_modules/@aws-crypto/sha256-js/build/jsSha256.js
./node_modules/@aws-crypto/sha256-js/build/index.js
./node_modules/@aws-amplify/auth/lib-esm/OAuth/OAuth.js
./node_modules/@aws-amplify/auth/lib-esm/Auth.js
./node_modules/@aws-amplify/auth/lib-esm/index.js

./node_modules/@aws-sdk/client-cloudwatch-logs/node_modules/@aws-crypto/util/build/convertToBuffer.js
A Node.js API is used (Buffer at line: 8) which is not supported in the Edge Runtime.
Learn more: https://nextjs.org/docs/api-reference/edge-runtime

Import trace for requested module:
./node_modules/@aws-sdk/client-cloudwatch-logs/node_modules/@aws-crypto/util/build/convertToBuffer.js
./node_modules/@aws-sdk/client-cloudwatch-logs/node_modules/@aws-crypto/util/build/index.js
./node_modules/@aws-sdk/client-cloudwatch-logs/node_modules/@aws-crypto/sha256-browser/build/webCryptoSha256.js
./node_modules/@aws-sdk/client-cloudwatch-logs/node_modules/@aws-crypto/sha256-browser/build/index.js
./node_modules/@aws-sdk/client-cloudwatch-logs/dist/es/runtimeConfig.browser.js
./node_modules/@aws-sdk/client-cloudwatch-logs/dist/es/CloudWatchLogsClient.js
./node_modules/@aws-sdk/client-cloudwatch-logs/dist/es/index.js
./node_modules/@aws-amplify/core/lib-esm/Providers/AWSCloudWatchProvider.js
./node_modules/@aws-amplify/core/lib-esm/Providers/index.js
./node_modules/@aws-amplify/core/lib-esm/index.js
./node_modules/@aws-amplify/auth/lib-esm/Auth.js
./node_modules/@aws-amplify/auth/lib-esm/index.js

./node_modules/@aws-sdk/client-cloudwatch-logs/node_modules/@aws-crypto/util/build/convertToBuffer.js
A Node.js API is used (Buffer at line: 9) which is not supported in the Edge Runtime.
Learn more: https://nextjs.org/docs/api-reference/edge-runtime

Import trace for requested module:
./node_modules/@aws-sdk/client-cloudwatch-logs/node_modules/@aws-crypto/util/build/convertToBuffer.js
./node_modules/@aws-sdk/client-cloudwatch-logs/node_modules/@aws-crypto/util/build/index.js
./node_modules/@aws-sdk/client-cloudwatch-logs/node_modules/@aws-crypto/sha256-browser/build/webCryptoSha256.js
./node_modules/@aws-sdk/client-cloudwatch-logs/node_modules/@aws-crypto/sha256-browser/build/index.js
./node_modules/@aws-sdk/client-cloudwatch-logs/dist/es/runtimeConfig.browser.js
./node_modules/@aws-sdk/client-cloudwatch-logs/dist/es/CloudWatchLogsClient.js
./node_modules/@aws-sdk/client-cloudwatch-logs/dist/es/index.js
./node_modules/@aws-amplify/core/lib-esm/Providers/AWSCloudWatchProvider.js
./node_modules/@aws-amplify/core/lib-esm/Providers/index.js
./node_modules/@aws-amplify/core/lib-esm/index.js
./node_modules/@aws-amplify/auth/lib-esm/Auth.js
./node_modules/@aws-amplify/auth/lib-esm/index.js

./node_modules/@aws-sdk/client-cognito-identity/node_modules/@aws-crypto/util/build/convertToBuffer.js
A Node.js API is used (Buffer at line: 8) which is not supported in the Edge Runtime.
Learn more: https://nextjs.org/docs/api-reference/edge-runtime

Import trace for requested module:
./node_modules/@aws-sdk/client-cognito-identity/node_modules/@aws-crypto/util/build/convertToBuffer.js
./node_modules/@aws-sdk/client-cognito-identity/node_modules/@aws-crypto/util/build/index.js
./node_modules/@aws-sdk/client-cognito-identity/node_modules/@aws-crypto/sha256-browser/build/webCryptoSha256.js
./node_modules/@aws-sdk/client-cognito-identity/node_modules/@aws-crypto/sha256-browser/build/index.js
./node_modules/@aws-sdk/client-cognito-identity/dist/es/runtimeConfig.browser.js
./node_modules/@aws-sdk/client-cognito-identity/dist/es/CognitoIdentityClient.js
./node_modules/@aws-sdk/client-cognito-identity/dist/es/index.js
./node_modules/@aws-amplify/core/lib-esm/Credentials.js
./node_modules/@aws-amplify/core/lib-esm/index.js
./node_modules/@aws-amplify/auth/lib-esm/Auth.js
./node_modules/@aws-amplify/auth/lib-esm/index.js

./node_modules/@aws-sdk/client-cognito-identity/node_modules/@aws-crypto/util/build/convertToBuffer.js
A Node.js API is used (Buffer at line: 9) which is not supported in the Edge Runtime.
Learn more: https://nextjs.org/docs/api-reference/edge-runtime

Import trace for requested module:
./node_modules/@aws-sdk/client-cognito-identity/node_modules/@aws-crypto/util/build/convertToBuffer.js
./node_modules/@aws-sdk/client-cognito-identity/node_modules/@aws-crypto/util/build/index.js
./node_modules/@aws-sdk/client-cognito-identity/node_modules/@aws-crypto/sha256-browser/build/webCryptoSha256.js
./node_modules/@aws-sdk/client-cognito-identity/node_modules/@aws-crypto/sha256-browser/build/index.js
./node_modules/@aws-sdk/client-cognito-identity/dist/es/runtimeConfig.browser.js
./node_modules/@aws-sdk/client-cognito-identity/dist/es/CognitoIdentityClient.js
./node_modules/@aws-sdk/client-cognito-identity/dist/es/index.js
./node_modules/@aws-amplify/core/lib-esm/Credentials.js
./node_modules/@aws-amplify/core/lib-esm/index.js
./node_modules/@aws-amplify/auth/lib-esm/Auth.js
./node_modules/@aws-amplify/auth/lib-esm/index.js

./node_modules/amazon-cognito-identity-js/es/AuthenticationHelper.js
A Node.js module is loaded ('buffer' at line 6) which is not supported in the Edge Runtime.
Learn More: https://nextjs.org/docs/messages/node-module-in-edge-runtime

Import trace for requested module:
./node_modules/amazon-cognito-identity-js/es/AuthenticationHelper.js
./node_modules/amazon-cognito-identity-js/es/index.js
./node_modules/@aws-amplify/auth/lib-esm/index.js

./node_modules/amazon-cognito-identity-js/es/CognitoJwtToken.js
A Node.js module is loaded ('buffer' at line 6) which is not supported in the Edge Runtime.
Learn More: https://nextjs.org/docs/messages/node-module-in-edge-runtime

Import trace for requested module:
./node_modules/amazon-cognito-identity-js/es/CognitoJwtToken.js
./node_modules/amazon-cognito-identity-js/es/CognitoIdToken.js
./node_modules/amazon-cognito-identity-js/es/index.js
./node_modules/@aws-amplify/auth/lib-esm/index.js

./node_modules/amazon-cognito-identity-js/es/CognitoUser.js
A Node.js module is loaded ('buffer' at line 6) which is not supported in the Edge Runtime.
Learn More: https://nextjs.org/docs/messages/node-module-in-edge-runtime

Import trace for requested module:
./node_modules/amazon-cognito-identity-js/es/CognitoUser.js
./node_modules/amazon-cognito-identity-js/es/index.js
./node_modules/@aws-amplify/auth/lib-esm/index.js

./node_modules/amazon-cognito-identity-js/node_modules/@aws-crypto/util/build/convertToBuffer.js
A Node.js API is used (Buffer at line: 8) which is not supported in the Edge Runtime.
Learn more: https://nextjs.org/docs/api-reference/edge-runtime

Import trace for requested module:
./node_modules/amazon-cognito-identity-js/node_modules/@aws-crypto/util/build/convertToBuffer.js
./node_modules/amazon-cognito-identity-js/node_modules/@aws-crypto/util/build/index.js
./node_modules/amazon-cognito-identity-js/node_modules/@aws-crypto/sha256-js/build/jsSha256.js
./node_modules/amazon-cognito-identity-js/node_modules/@aws-crypto/sha256-js/build/index.js
./node_modules/amazon-cognito-identity-js/es/AuthenticationHelper.js
./node_modules/amazon-cognito-identity-js/es/index.js
./node_modules/@aws-amplify/auth/lib-esm/index.js

./node_modules/amazon-cognito-identity-js/node_modules/@aws-crypto/util/build/convertToBuffer.js
A Node.js API is used (Buffer at line: 9) which is not supported in the Edge Runtime.
Learn more: https://nextjs.org/docs/api-reference/edge-runtime

Import trace for requested module:
./node_modules/amazon-cognito-identity-js/node_modules/@aws-crypto/util/build/convertToBuffer.js
./node_modules/amazon-cognito-identity-js/node_modules/@aws-crypto/util/build/index.js
./node_modules/amazon-cognito-identity-js/node_modules/@aws-crypto/sha256-js/build/jsSha256.js
./node_modules/amazon-cognito-identity-js/node_modules/@aws-crypto/sha256-js/build/index.js
./node_modules/amazon-cognito-identity-js/es/AuthenticationHelper.js
./node_modules/amazon-cognito-identity-js/es/index.js
./node_modules/@aws-amplify/auth/lib-esm/index.js

ryanwalters on Mar 31, 2023

I made a comment here where I’ve changed the variable type of SSR to resolve issues I was having with next12 WEB_COMPUTE getServerSideProps and Auth.

Changing

  const SSR = withSSRContext({ req });

  let SSR = withSSRContext({ req });

blackmouth on Feb 19, 2023

Hi @abdallahshaban557, this is now a blocker for us and we need to find a solution/alternative . How close are you guys to release a fix? thanks

cuginoAle on Jan 11, 2023

Any update on this? Any workaround?

kumar0 on Dec 15, 2022

Can anyone help me with this? https://stackoverflow.com/questions/74462640/how-to-handle-dynamic-list-json-of-redirects-on-nextjs-aws-amplify

caiodounis on Nov 16, 2022