aws-amplify / amplify-hosting

AWS Amplify Hosting provides a Git-based workflow for deploying and hosting fullstack serverless web applications.
https://aws.amazon.com/amplify/hosting/
Apache License 2.0
460 stars 116 forks source link

Subdomain limit of 50 #3279

Closed scottmanny closed 1 year ago

scottmanny commented 1 year ago

Before opening, please confirm:

App Id

d3f0vp9f8i81gz

Region

us-east-1

Step

Domain management

Status

Failed

Issue or question

I use AWS Amplify for managing my app (https://pickleplanner.com), and I love it. Every time a customer signs up they get their very own web address (e.g. https://my-club-name.pickleplanner.com). My latest customer just tried to sign up but received an error because it exceed the 50 subdomain limit (that I was unaware of). Please help me to get this subdomain limit increased, I'll do anything. Thanks.

Error message

Too many sub domains requested, the maximum allowed in your account is 50

Additional information

Feel free to call me at 618.980.3277

scottmanny commented 1 year ago

I seemed to have found the place to request an increase to the quota. https://us-east-1.console.aws.amazon.com/servicequotas/home/services/amplify/quotas/L-A6716586

ghost commented 1 year ago

Hi @scottmanny 👋🏽 thanks for raising this question. There is a default limit of 50 subdomains for each domain used in a region. You can proceed to request a limit increase here if you have not already.

For additional documentation on our service limits, feel free to reference our Amplify service quotas. Thank you!

github-actions[bot] commented 1 year ago

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see. If you need more assistance, please either tag a team member or open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so.

github-actions[bot] commented 1 year ago

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.