aws-amplify / aws-amplify/amplify-hosting
Amplify console page is unresponsive when adding bulk Redirect Rules.
- Dominant language
- Dockerfile
- Stars
- 481
- Forks
- 123
- PR merge metrics
- No merged PRs in 30d
Description
### Before opening, please confirm:
- [X] I have checked to see if my question is addressed in the [FAQ](https://github.com/aws-amplify/amplify-hosting/blob/master/FAQ.md).
- [X] I have [searched for duplicate or closed issues](https://github.com/aws-amplify/amplify-hosting/issues?q=is%3Aissue+).
- [X] I have read the guide for [submitting questions](https://github.com/aws-amplify/amplify-hosting/blob/master/CONTRIBUTING.md).
- [X] I have removed any sensitive information from my code snippets and submission.
### App Id
-
### AWS Region
us-east-1
### Amplify Hosting feature
Redirects
### Is your feature request related to a problem? Please describe:
When trying to add bulk Redirect URL's (50K) via the console for a Next.js Amplify app, the console page is getting unresponsive and the Redirect rules are never added.
Also tried adding the Redirect rules using the AWS CLI, but was not able to add atleast 5K and got the below error message.
*****************
An error occurred (LimitExceededException) when calling the UpdateApp operation (reached max retries: 2): You've reached the maximum configuration storage limit for this app, either remove some branches or reduce the number of redirects, rewrites or custom headers associated with this app.
*****************
### Describe how you'd like this feature to work
Amplify should support adding bulk Redirect URL's (almost 50K URL's). But currently 5K Redirect URL's are also throwing the LimitExceededException error.
Contributor guide
Research direction
The issue describes bulk Redirect Rules through the Amplify console and AWS CLI for a Next.js app. Start by investigating the console unresponsiveness and the reported UpdateApp LimitExceededException at roughly 5K rules. Done means Amplify can accept the requested bulk redirects without the page becoming unresponsive or hitting the stated limit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, next.js
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100