{"id":984,"date":"2022-12-07T21:29:58","date_gmt":"2022-12-07T21:29:58","guid":{"rendered":"http:\/\/oqtacore-blog-473533498.us-east-1.elb.amazonaws.com\/?p=984"},"modified":"2023-01-18T10:42:57","modified_gmt":"2023-01-18T10:42:57","slug":"fixing-a-failing-monorepo-build-on-the-new-aws-amplify","status":"publish","type":"post","link":"https:\/\/oqtacore.com\/blog\/fixing-a-failing-monorepo-build-on-the-new-aws-amplify\/","title":{"rendered":"Fixing a failing monorepo build on the new AWS Amplify’s Web Compute platform"},"content":{"rendered":"

AWS Amplify has recently introduced a new platform called “Web Compute” that claims better support and performance for Next.js 12 and higher. But for us, it proved to be a disaster.<\/p>\n

We have migrated to it and our website went down, and we spent many hours trying to get things working back again. If you have been using AWS Amplify for the last few years, you probably have the same problem as we do. The build completes, but then the website does not work.<\/p>\n

 <\/p>\n

<\/span>How did it happen?<\/span><\/h2>\n

Long story short, AWS has moved to the new platform called “Web Compute”. It is opposed to the old platform “Web Dynamic” that probably did not have a name just a few months ago.<\/p>\n

It is possible that either you created a new Amplify app, or just migrated the old one<\/p>\n

\"A

A button to migrate AWS Amplify to Web Compute<\/p><\/div>\n

 <\/p>\n

\"Popup

Popup when migrating an AWS Amplify app from Web Dynamic to Web Compute<\/p><\/div>\n

 <\/p>\n

<\/span>The problem<\/span><\/h2>\n

The build succeeds<\/p>\n

\"AWS

AWS Amplify successful build and deploy<\/p><\/div>\n

but then it fails when rendering the page:<\/p>\n

\"503

The Lambda function associated with the CloudFront distribution is invalid or doesn’t have the required permissions.<\/p><\/div>\n

 <\/p>\n

<\/span>What’s the reason of the failure?<\/span><\/h2>\n

The underlying reason of the failure is that the build process changed, and if your monorepo build has various manual steps with different paths in amplify.yml<\/strong>, some files will not get into the package. You can just compare the lambdas generated bu the old build and the new build<\/p>\n

 <\/p>\n

<\/span>Simple solution<\/span><\/h2>\n

If you don’t have time to fix the build, you can create the old-fashioned Web Dynamic app. It will work just as it has worked before. The important thing here – IT can only be done via the AWS CLI or other API client.<\/p>\n

Here is my solution:<\/p>\n

    \n
  1. Create (or get already existing) security credentials for an AWS user<\/a> with sufficient permissions. Remember the Access key ID<\/strong> and Secret Key<\/strong><\/li>\n
  2. Create (or find an already existing) role to be used with Amplify. The easiest would be to get a service role from an already existing Amplify app. You need the ARN of this role, remember it as %ROLE_ARN%<\/li>\n
  3. Get the repository URL that you want to use. Do not include `\/tree\/main` (opposed to what you see in the AWS Amplify’s UI). Remember the repo URL as %REPO_URL%. Also remember the branch that you want to use as %BRANCH%<\/li>\n
  4. This one is tricky. I will suppose that you use github, so you will need to create an access token for github. The best part is, AWS Amplify will replace it with its own token as soon as you are done, but you will still need to create one first.\n