Resource quotas
AWS KMS establishes resource quotas to ensure that it can provide fast and resilient service to all of our customers. Some resource quotas apply only to resources that you create, but not to resources that AWS services create for you. Resources that you use, but that aren't in your AWS account, such as AWS owned keys, do not count against these quotas.
If you have exceeded a resource limit, requests to create an additional resource of
that
type generate an LimitExceededException error message.
The following table lists and describes the AWS KMS resource quotas in each AWS account
and
Region. If you need to exceed a quota, you can request a quota increase in Service
Quotas. Use the
Service Quotas console
For help requesting an increase in an AWS KMS quota, see Requesting an AWS KMS quota Increase.
| Quota name | Default value | Applies to |
|---|---|---|
| AWS KMS keys | 10,000 | Customer managed keys |
| Aliases per KMS key | 50 | Customer created aliases |
| Grants per KMS key | 50,000 | Customer managed keys |
| Key policy document size | 32 KB (32,768 bytes) |
Customer managed keys AWS managed keys |
In addition to resource quotas, AWS KMS uses request quotas to ensure the responsiveness of the service. For details, see Request quotas.
AWS KMS keys: 10,000
You can have up to 10,000 customer managed keys in each Region of your AWS account. This quota applies to all symmetric and asymmetric customer managed keys regardless of their key state. Each KMS key — whether symmetric or asymmetric — is considered to be one resource. AWS managed keys and AWS owned keys do not count against this quota.
Aliases per KMS key: 50
You can associate up to 50 aliases with each customer managed key. Aliases that AWS associates with AWS managed keys do not count against this quota. You might encounter this quota when you create or update an alias.
The kms:ResourceAliases condition
is effective only when the KMS key conforms to this quota. If a KMS key exceeds this
quota,
principals who are authorized to use the KMS key by the kms:ResourceAliases
condition are denied access to the KMS key. For details, see Access denied due to alias quota.
The Aliases per KMS key quota replaces the Aliases per Region quota that limited the total number of aliases in each Region of an AWS account. AWS KMS has eliminated the Aliases per Region quota.
Grants per KMS key: 50,000
Each customer managed key can have up to 50,000
grants, including the grants created by AWS services that are integrated with AWS KMS
One effect of this quota is that you cannot perform more than 50,000 grant-authorized operations that use the same KMS key at the same time. After you reach the quota, you can create new grants on the KMS key only when an active grant is retired or revoked.
For example, when you attach an Amazon Elastic Block Store (Amazon EBS) volume to an Amazon Elastic Compute Cloud (Amazon EC2) instance, the volume is decrypted so you can read it. To get permission to decrypt the data, Amazon EBS creates a grant for each volume. Therefore, if all of your Amazon EBS volumes use the same KMS key, you cannot attach more than 50,000 volumes at one time.
Key policy document size: 32 KB
The maximum length of each key policy document is 32 KB (32,768 bytes). If you use a larger policy document to create or update the key policy for a KMS key, the operation fails.
Unlike other AWS KMS quotas, this quota is not adjustable. You cannot increase it by using Service Quotas or by creating a case in AWS Support. If your key policy is approaching the limit, consider using grants instead of policy statements. Grants are particularly well suited to temporary or very specific permissions.
You use a key policy document whenever you create or change a key policy by using the default view or policy view in the AWS Management Console, or the PutKeyPolicy operation. This quota applies to your key policy document, even if you use the default view in the AWS KMS console, where you don't edit the JSON statements directly.
