How do I troubleshoot issues that I encounter when I use the AWS CLI to manage my service quota requests?

Resolution

Note: If you receive errors when you run AWS CLI commands, then see Troubleshooting errors for the AWS CLI. Also, make sure that you're using the most recent AWS CLI version. For information about AWS CLI errors that aren't related to service quotas, see Why do I receive errors when I run AWS CLI commands?

Take the following actions based on the issue that you encounter.

The list-service-quotas command doesn't list all available quotas

The list-service-quotas command shows only quotas that have applied quota values. To view all default values, run the list-aws-default-service-quotas command.

Example list-service-quotas command:

aws service-quotas list-service-quotas --service-code vpc --region eu-west-1 --query "Quotas[*].{ServiceName:ServiceName,QuotaName:QuotaName,QuotaCode:QuotaCode,Value:Value}" --output table

Example output:

# aws service-quotas list-service-quotas --service-code vpc --region eu-west-1 --query "Quotas[*].{ServiceName:ServiceName,QuotaName:QuotaName,QuotaCode:QuotaCode,Value:Value}" --output table------------------------------------------------------------------------------------------------------
| ListServiceQuotas |
+------------+--------------------------------+---------------------------------------------+--------+
| QuotaCode | QuotaName | ServiceName | Value |
+------------+--------------------------------+---------------------------------------------+--------+
| L-A4707A72| Internet gateways per Region | Amazon Virtual Private Cloud (Amazon VPC) | 10.0 |
| L-F678F1CE| VPCs per Region | Amazon Virtual Private Cloud (Amazon VPC) | 10.0 |
+------------+--------------------------------+---------------------------------------------+--------+

Note: The output shows the two Amazon Virtual Private Cloud (Amazon VPC) service quotas that have applied values.

Example list-aws-default-service-quotas command:

aws service-quotas list-aws-default-service-quotas --service-code vpc --region eu-west-1 --query "Quotas[*].{ServiceName:ServiceName,QuotaName:QuotaName,QuotaCode:QuotaCode,Value:Value}" --output table

Example output:

# aws service-quotas list-aws-default-service-quotas --service-code vpc --region eu-west-1 --query "Quotas[*].{ServiceName:ServiceName,QuotaName:QuotaName,QuotaCode:QuotaCode,Value:Value}" --output table-----------------------------------------------------------------------------------------------------------------------
| ListAWSDefaultServiceQuotas |
+------------+------------------------------------------------+---------------------------------------------+---------+
| QuotaCode | QuotaName | ServiceName | Value |
+------------+------------------------------------------------+---------------------------------------------+---------+
| L-7E9ECCDB| Active VPC peering connections per VPC | Amazon Virtual Private Cloud (Amazon VPC) | 50.0 |
| L-45FE3B85| Egress-only internet gateways per Region | Amazon Virtual Private Cloud (Amazon VPC) | 5.0 |
| L-1B52E74A| Gateway VPC endpoints per Region | Amazon Virtual Private Cloud (Amazon VPC) | 20.0 |
| L-83CA0A9D| IPv4 CIDR blocks per VPC | Amazon Virtual Private Cloud (Amazon VPC) | 5.0 |
| L-085A6257| IPv6 CIDR blocks per VPC | Amazon Virtual Private Cloud (Amazon VPC) | 1.0 |
| L-0EA8095F| Inbound or outbound rules per security group | Amazon Virtual Private Cloud (Amazon VPC) | 60.0 |
| L-29B6F2EB| Interface VPC endpoints per VPC | Amazon Virtual Private Cloud (Amazon VPC) | 50.0 |
| L-A4707A72| Internet gateways per Region | Amazon Virtual Private Cloud (Amazon VPC) | 5.0 |
| L-FE5A380F| NAT gateways per Availability Zone | Amazon Virtual Private Cloud (Amazon VPC) | 5.0 |
| L-B4A6D682| Network ACLs per VPC | Amazon Virtual Private Cloud (Amazon VPC) | 200.0 |
| L-DF5E4CA3| Network interfaces per Region | Amazon Virtual Private Cloud (Amazon VPC) | 5000.0 |
| L-DC9F7029| Outstanding VPC peering connection requests | Amazon Virtual Private Cloud (Amazon VPC) | 25.0 |
| L-2C462E13| Participant accounts per VPC | Amazon Virtual Private Cloud (Amazon VPC) | 100.0 |
| L-589F43AA| Route tables per VPC | Amazon Virtual Private Cloud (Amazon VPC) | 200.0 |
| L-93826ACB| Routes per route table | Amazon Virtual Private Cloud (Amazon VPC) | 50.0 |
| L-2AEEBF1A| Rules per network ACL | Amazon Virtual Private Cloud (Amazon VPC) | 20.0 |
| L-2AFB9258| Security groups per network interface | Amazon Virtual Private Cloud (Amazon VPC) | 5.0 |
| L-407747CB| Subnets per VPC | Amazon Virtual Private Cloud (Amazon VPC) | 200.0 |
| L-44499CD2| Subnets that can be shared with an account | Amazon Virtual Private Cloud (Amazon VPC) | 100.0 |
| L-8312C5BB| VPC peering connection request expiry hours | Amazon Virtual Private Cloud (Amazon VPC) | 168.0 |
| L-E79EC296| VPC security groups per Region | Amazon Virtual Private Cloud (Amazon VPC) | 2500.0 |
| L-F678F1CE| VPCs per Region | Amazon Virtual Private Cloud (Amazon VPC) | 5.0 |
+------------+------------------------------------------------+---------------------------------------------+---------+

Note: The output shows all quotas that are associated with Amazon VPC, along with their default quota values.

You receive the "ResourceAlreadyExistsException" error message

Each quota allows only one open service quota increase request. If you submit another request before the previous one completes, then you receive the following error message:

"An error occurred (ResourceAlreadyExistsException) when calling the RequestServiceQuotaIncrease operation: Only one open service quota increase request is allowed per quota."

Before you submit a quota increase request, run the following list-requested-service-quota-change-history command to check for pending service quota requests:

aws service-quotas list-requested-service-quota-change-history --service-code example-service-code

Note: Replace example-service-code with your service code. To check for quota increase requests that have a specific status, such as Pending, use the --status option.

You receive the "NoSuchResourceException" error message

If the service that you ran a command for doesn't have an associated service quota, then you receive the following error message:

"An error occurred (NoSuchResourceException) when calling the ListAWSDefaultServiceQuotas operation: The request failed because the specified service does not exist."

To resolve this issue, run the following list-services command to verify that your service has the service quota that you searched for:

aws service-quotas list-services

Also, make sure that you used the correct case in your command. Service codes are case sensitive. For example, the service code for Amazon Elastic Compute Cloud (Amazon EC2) is ec2 not EC2.

For a list of all the APIs related to service quotas, see Actions.

Related information

How do I use AWS CLI commands to request, view, and manage service quota increases?

What is Service Quotas?