1 個回答
- 最新
- 最多得票
- 最多評論
0
Hello there,
This error usually happens if the API configuration is too large. For example, if the number of VPC links, routes or any other resource or operation quota is exceeded. The suggested workaround is to reduce the size of API configuration or increase the resource/operation quota if it supports quota increase.
[+] HTTP API quotas - https://docs.aws.amazon.com/apigateway/latest/developerguide/limits.html#http-api-quotas
However, I would suggest that you reach out to Premium Support over a case in order to further dive deeper into the issue.
相關內容
- AWS 官方已更新 2 年前