Quotas for your IPAM - Amazon Virtual Private Cloud

Quotas for your IPAM

This section lists the quotas related to IPAM. The Service Quotas console also provides information about IPAM quotas. You can use the Service Quotas console to view default quotas and request quota increases for adjustable quotas. For more information, see Requesting a quota increase in the Service Quotas User Guide.

Name Default Adjustable
Amazon-provided contiguous public IPv4 CIDR blocks 2 Yes. Contact the AWS Support Center as described in AWS service quotas in the AWS General Reference.
Amazon-provided contiguous public IPv4 CIDR block netmask length /29 Acceptable size is between /29 and /30. To request an increase, contact the AWS Support Center as described in AWS service quotas in the AWS General Reference.
Amazon-provided IPv6 CIDR block netmask length /52 Yes. Contact the AWS Support Center as described in AWS service quotas in the AWS General Reference.
Amazon-provided IPv6 CIDR blocks per Regional pool 1 Yes. Contact the AWS Support Center as described in AWS service quotas in the AWS General Reference.
Autonomous System Numbers (ASNs) that you can bring to IPAM 5 Yes. Contact the AWS Support Center as described in AWS service quotas in the AWS General Reference.
CIDRs per pool 50 Yes
Enabled targets per IPAM policy 100 Yes. To request an adjustment to the quota, contact the AWS Support Center as described in AWS service quotas in the AWS General Reference.
IPAM administrators per organization 1 No
IPAMs per Region 1 No
IPAM policies per IPAM 10 Yes. To request an adjustment to the quota, contact the AWS Support Center as described in AWS service quotas in the AWS General Reference.
IPAM policy allocation rules per resource-locale pair* 10 Yes. To request an adjustment to the quota, contact the AWS Support Center as described in AWS service quotas in the AWS General Reference.
Organizational unit exclusions per resource discovery 10 Yes. Contact the AWS Support Center as described in AWS service quotas in the AWS General Reference.
Pool depth (the number of pools within pools) 10 Yes
Pools per scope 50 Yes
Prefix list resolvers per IPAM 10 Yes
Prefix list resolver targets per prefix list resolver 50 Yes. Contact the AWS Support Center as described in AWS service quotas in the AWS General Reference.
Rules per prefix list resolver 100 Yes. Contact the AWS Support Center as described in AWS service quotas in the AWS General Reference.
CIDR entries per prefix list resolver version 1000 Yes. Contact the AWS Support Center as described in AWS service quotas in the AWS General Reference.
Resource discovery associations per IPAM 5 Yes
Resource discoveries per Region 1 No
Resource utilization metrics 50 Yes. Contact the AWS Support Center as described in AWS service quotas in the AWS General Reference.
Scopes per IPAM 5 Yes. When you create an IPAM, a private and public default scope are created for you. If you want to create additional scopes, they will be private scopes. You cannot create additional public scopes.

* Resource-locale pair: When setting allocation rules, you must specify both a resource type (the AWS resource like EIPs, ALBs, or RDS clusters) and a locale (the AWS Region or Local Zone where the rule applies). Allocation rules are scoped to this resource type and locale combination. For example, if you're setting a policy for EIPs in us-east-1, you can set up to 10 rules for that specific resource-locale pair*.