AWS API配额上限查询及资源扩展可行性咨询

Hey there! Let’s tackle your questions clearly, assuming you’re working with AWS API Gateway (the most common service for this kind of resource quota error):

1. What’s the maximum quota limit for AWS APIs? #

It depends on the API type you’re using:

• For REST APIs: The default per-API resource quota is 500, and you can request an increase up to 10,000 resources per API via AWS Support.
• For HTTP APIs: The default per-API resource quota is 1,000, with a maximum possible increase to 10,000 as well.
• For WebSocket APIs: The default is 100 resources per API, with a max increase to 1,000.

2. Why am I hitting the limit at 400 resources, and is my quota in the 500-800 range? #

The error Maximum number of Resources for this API has been reached means your current API’s resource quota is exactly 400—not in the 500-800 range. This could happen for a few reasons:

• Your AWS account might have a custom quota applied (maybe from a previous support request that adjusted it downward, or a regional restriction).
• You might be using a legacy API configuration that has lower default limits.

To confirm your exact current quota, you can:

• Check the Settings tab of your API in the AWS API Gateway Console (look for "Resource count" and "Quota limit").
• Run this AWS CLI command (replace REGION with your API’s region):

  aws apigateway get-account --region REGION
  

  The response will include limits details, including the maximum number of resources per API.

3. Can I extend the quota by 200-300, or do I need to create a new API? #

You absolutely can request a quota increase! Here’s how:

1. Go to the AWS Support Center in your AWS Console.
2. Create a new case, select Service Limit Increase as the case type.
3. Choose API Gateway as the service, then select the specific quota (e.g., "Resources per REST API").
4. Enter your desired new limit (e.g., 600-700, since you need 200-300 more than your current 400) and explain your use case briefly.

AWS Support typically approves reasonable quota increases if your use case is valid. If for some reason the increase is denied (unlikely for this range), splitting your resources into a new API is a solid alternative—this also helps with organizing your API by business domains or functionality, making maintenance easier.

内容的提问来源于stack exchange，提问作者Hulubina