Build settings UI states max build time is 8 hours

walmartshopper commented 1 year ago

Before opening, please confirm:

[X] I have checked to see if my question is addressed in the FAQ.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

App Id

N/A

AWS Region

us-east-2

Amplify Hosting feature

Build settings

Frontend framework

Next.js

Next.js version

13

Next.js router

App Router

Describe the bug

The build settings UI states "The maximum build timeout is 8 hours." However if you try to save anything higher than 120 minutes, it says "Updating build settings failed. Build timeout cannot exceed 120 minutes."

I have a project that needs to build 2738 SSR pages. The build is expected to take very close to 120 minutes and possibly slightly more. If I cannot extend my build timeout beyond 120 minutes, Ampllify may not work for me. Maybe it could be a quota that defaults to 120 but could be increased.

Expected behavior

Entering 480 minute build timeout should work based on stated 8-hour maximum.

Reproduction steps

Open build settings.
Note that it says "The maximum build timeout is 8 hours."
Try to enter a value higher than 120 minutes and save

Build Settings

No response

Log output

``` # Put your logs below this line ```

Additional information

No response

Jay2113 commented 8 months ago

Hi @walmartshopper 👋 , thanks for reaching out. The build timeout of 120 mins or 2 hours is a hard limit and we have updated the Build image settings UI in the Amplify console to reflect the same. That being said, I am curious to know about your use case and would like to explore any opportunity that could help reduce your Amplify build times.

walmartshopper commented 8 months ago

The app is The Hockey News Archive which is a full archive of every issue of the magazine. The build includes doing server-side rendering for around 3000 pages, and the images for each page are being pulled in from the Zinio CDN. Each page takes an average of 3 seconds to generate, resulting in a build time of around 150 minutes. Throwing more cpu or ram at the build server doesn't improve the build time at all. I ended up having to use CodePipeline / Codebuild / CodeDeploy which has an 8 hour build time limit, and then deploying to ec2 instances behind a load balancer and using cloudfront for static assets.

walmartshopper commented 8 months ago

@Jay2113 I would love to see the max build time bumped up to at least 4 hours, because it's the only thing preventing me from running this app on Amplify. Maybe it could be a quota that defaults to 2 hours but could be requested to increase to 4 or 8 hours for special use cases like this. Now that we are getting charged for using IPv4 addresses, the cost of our current infrastructure increased dramatically, so it would be great if we could switch to Amplify.

aws-amplify / amplify-hosting