is there any way to increase timeout time? next.js server.

[yshaish1]

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 questions.
• [X] I have removed any sensitive information from my code snippets and submission.

App Id

NEW_APP

AWS Region

us-east-2

Amplify Hosting feature

SSR

Question

is there any way to increase the 30s timeout when I am using next.js node server? I have some long tasks, and they take more than 30s. is there any way to make it 60s or some?

thanks

[Jay2113]

@yshaish1 👋 , thanks for raising this question. Unfortunately, increasing the timeout of the Lambda functions hosting SSR apps using the Compute platform is not supported at this time. We will keep this open as a feature request instead.

[github-actions[bot]]

This has been identified as a feature request. If this feature is important to you, we strongly encourage you to give a 👍 reaction on the request. This helps us prioritize new features most important to you. Thank you!

[espenbye]

Would be great to be able to override this

[LTMenezes]

It would be great to have this configuration available in Amplify

[indiejoseph]

Cloudfront configuration is hosted by AWS, I know Amplify is a high level product, but 30s timeout is doesn't make sense, and no way to configurate...

[elitar]

The 30s timeout on Amplify limits our quick demos and may force architecture changes, counter to why we chose Amplify. Essential to have adjustable or significantly increased timeouts—please prioritize. Thanks!

[mustafadalga]

Is there any solution. I have same issue!

[KPOINT-Team]

This is becoming a blocker now and its forcing us to move away from hosting the application from the Amplify to somewhere else. There are many requests which takes more than 30 seconds to process them in the backend. Limiting the timeout to 30 seconds is not helping us.

[StevenBarnett1]

This issue has killed our production app as well. Will need to rewrite a lot of our code to poll for changes or need to move to vercel where we can have greater than 30 second timeout.

[flaviokicis]

We are going to finish the request normally because of this max 30 seconds timeout, then poll for results to work around this issue.

The experience remains the same for the user, we just have to poll and add a manual timeout on our end.