Jarrod Watts Finally, It's 9.x.x that worked but still would wait AWS response because that means NextJS latest version vs AWS supported will lag behind to use features like Image component from the latest NextJS version.

Jarrod Watts Using Amplify just wanted more control rather using third party. In next.config.js, when reference to const withPWA = require(next-pwa) is removed, the issue is gone but loosing pwa support. Amplify frustration is; it shows as 'internal error' within its logs and hence tough to identify the cause with insufficient documentation on Amplify pwa. I even used 'next' version 10 that's as per docs is supported (limited).

Jarrod Watts Thanks mate for the reply. I even removed the image code and simply followed: yarn create next-app --typescript Configure Amplify and AWS Use CI CD option to deploy to AWS via Amplify and link repository for the frontend app (ALL WORKS) Configure next.config.js for PWA support using NextJS plugin called next-pwa Deploy again (BUILD FAILS)

A nice article. I recently faced a weird issue relevant to this and raised in stack overflow along with a support ticket to AWS. Do you think you can give some opinion on this. StackOverflowPost