Amplify next.js multi-zone setup w/ assetPrefix

When deploying a Next.js application with a multi-zone setup using assetPrefix on AWS Amplify, you're encountering an issue where the static folder is being omitted from the build artifacts, resulting in 500 errors due to missing files.

This appears to be a known issue with AWS Amplify's handling of Next.js applications that use assetPrefix. Based on the information available, when you specify an assetPrefix (like "/zone-b"), Amplify may be incorrectly interpreting this configuration and not properly including the static assets in the deployment artifacts.

For a short-term workaround, you might try:

1. Modifying your amplify.yml configuration to explicitly include the static files in the artifacts section
2. Adjusting your build process to ensure the static files are copied to the expected location
3. Opening a support case with AWS under "Account and billing" (which can be done free of charge) to get specific assistance with this issue

Since this appears to be a known issue based on the GitHub issues you referenced, the AWS Amplify team may be working on a fix. In the meantime, reaching out to AWS Support could provide you with a more tailored workaround for your specific setup.
Sources
Unable to deploy Next JS app on Amplify (Please reach out to your support representative.) | AWS re:Post
Deploy React and Server Side Rendered Apps and Static Sites - Amplify Hosting - AWS