Service Quotas: User Guide
Service Quotas: User Guide
User Guide
Service Quotas User Guide
Amazon's trademarks and trade dress may not be used in connection with any product or service that is not
Amazon's, in any manner that is likely to cause confusion among customers, or in any manner that disparages or
discredits Amazon. All other trademarks not owned by Amazon are the property of their respective owners, who may
or may not be affiliated with, connected to, or sponsored by Amazon.
Service Quotas User Guide
Table of Contents
What is Service Quotas? ..................................................................................................................... 1
Features .................................................................................................................................... 1
Terms ....................................................................................................................................... 1
Accessing Service Quotas ............................................................................................................ 2
Getting started .................................................................................................................................. 3
Viewing service quotas ....................................................................................................................... 4
Requesting a quota increase ................................................................................................................ 5
Using CloudWatch alarms ................................................................................................................... 6
Using request templates ..................................................................................................................... 7
Security ............................................................................................................................................ 9
Data protection .......................................................................................................................... 9
Identity and access management ............................................................................................... 10
Grant permissions using IAM policies .................................................................................. 10
API actions for Service Quotas ........................................................................................... 11
Service Quotas resources ................................................................................................... 11
Resource-level permissions for Service Quotas ..................................................................... 12
Condition keys for Service Quotas ...................................................................................... 12
Predefined AWS managed policies for Service Quotas ........................................................... 12
Compliance validation ............................................................................................................... 12
Resilience ................................................................................................................................ 13
Infrastructure security ............................................................................................................... 13
Service quotas ................................................................................................................................. 14
Document history ............................................................................................................................. 16
iii
Service Quotas User Guide
Features
Contents
• Features (p. 1)
• Terms (p. 1)
• Accessing Service Quotas (p. 2)
Features
The following features are available.
The Service Quotas console provides quick access to the AWS default quota values for your account,
across all commercial Regions. When you select a service in the Service Quotas console, you'll see
the quotas and whether the quota is adjustable. Applied quotas are overrides, or increases for a
particular quota, over the AWS default value.
Request a service quota increase
For any adjustable service quotas, you can use Service Quotas to request a quota increase. To
request a quota increase, in the console simply select the service and the specific quota, and choose
Request quota increase. You can also use the API or command line interface (CLI) tools to request
service quota increases.
View current utilization
After your account has been active a while, you can view a graph of your resource utilization.
Terms
The following terms are important for understanding Service Quotas and how it works.
service quota
The maximum number of service resources or operations that apply to an account or a Region.
The number of IAM roles per account is an example of account-based quota. The number of virtual
private clouds (VPCs) per Region is an example of a Region-based quota. Check the description of a
service quota to determine whether it is Region-specific.
adjustable value
1
Service Quotas User Guide
Accessing Service Quotas
default value
A service quota applied at an account level. Global quotas are available in all Regions. You can
request an increase to a global quota from any Region, and can track the status of the increase from
the Region where you requested the increase. If you request a quota increase for a global you can't
request an increase for the same quota from a different Region until the first request is complete.
After the initial request is completed, the applied quota value is visible in all Regions where applied
quotas are available.
usage
The percentage of a service quota in use. For example, if the quota value is 200 resources and 150
resources are in use, the utilization is 75%.
The Service Quotas console is a browser-based interface that you can use to view and manage
your service quotas. You can perform almost any task that's related to your service quotas by using
the console. You can access Service Quotas from any AWS console page by choosing on the top
navigation bar, or by searching for Service Quotas in the AWS Management Console.
AWS Command Line Tools
The AWS command line tools let you issue commands at your system's command line to perform
Service Quotas and other AWS tasks. This can be faster and more convenient than using the console.
The command line tools also are useful if you want to build scripts that perform AWS tasks.
AWS provides two sets of command line tools: the AWS Command Line Interface (AWS CLI) and the
AWS Tools for Windows PowerShell. For information about installing and using the AWS CLI, see
the AWS Command Line Interface User Guide. For information about installing and using the Tools
for Windows PowerShell, see the AWS Tools for Windows PowerShell User Guide.
AWS SDKs
The AWS SDKs consist of libraries and sample code for various programming languages and
platforms (for example, Java, Python, Ruby, .NET, iOS and Android, and others). The SDKs
include tasks such as cryptographically signing requests, managing errors, and retrying requests
automatically. For more information about the AWS SDKs, including how to download and install
them, see Tools for Amazon Web Services.
2
Service Quotas User Guide
Next steps
3
Service Quotas User Guide
4
Service Quotas User Guide
5
Service Quotas User Guide
If you have utilization, it appears beneath the quota description. The CloudWatch alarms section
appears at the bottom of the page.
4. In Amazon CloudWatch alarms, choose Create.
5. For Alarm threshold, choose a threshold.
6. For Alarm name, enter a name for the alarm. This name must be unique within the AWS account.
7. Choose Create.
8. To add a notification to the CloudWatch alarm, see Creating a CloudWatch Alarm Based on a
CloudWatch Metric in the Amazon CloudWatch User Guide.
6
Service Quotas User Guide
To use a request template, you must use AWS Organizations and the new accounts must be created in
the same organization. Your organization must use the features set, all features. If you use consolidated
billing features, you can't use quota request templates.
You can update the request template by adding or deleting service quotas. You can also increase the
values for any adjustable quotas. As soon as you adjust the template, those service quota values are
requested for new accounts. Updating a request template does not update quota values for existing
accounts.
To add more quota increase requests to the template, choose Repeat the previous step.
4. To associate the template with your organization, choose Associate.
If you disassociate the template from the organization, new accounts receive the AWS default quota
values for all quotas. Disassociating the template from the organization doesn't delete the service quota
requests from the template. You can edit the service quotas in the template.
You can remove, or delete, service quota requests from the template whether the template is associated
with an organization, or not. If you reach the maximum number of service quota requests, it may be
necessary to delete some service quota requests.
7
Service Quotas User Guide
8
Service Quotas User Guide
Data protection
Security is a shared responsibility between AWS and you. The shared responsibility model describes this
as security of the cloud and security in the cloud:
• Security of the cloud – AWS is responsible for protecting the infrastructure that runs AWS services in
the AWS Cloud. AWS also provides you with services that you can use securely. Third-party auditors
regularly test and verify the effectiveness of our security as part of the AWS Compliance Programs.
To learn about the compliance programs that apply to Service Quotas, see AWS Services in Scope by
Compliance Program.
• Security in the cloud – Your responsibility is determined by the AWS service that you use. You are also
responsible for other factors including the sensitivity of your data, your company’s requirements, and
applicable laws and regulations.
This documentation helps you understand how to apply the shared responsibility model when using
Service Quotas. The following topics show you how to configure Service Quotas to meet your security
and compliance objectives. You also learn how to use other AWS services that help you to monitor and
secure your Service Quotas resources.
Contents
• Data protection in AWS Service Quotas (p. 9)
• Identity and access management for Service Quotas (p. 10)
• Compliance validation for AWS Service Quotas (p. 12)
• Resilience in AWS Service Quotas (p. 13)
• Infrastructure security in AWS Service Quotas (p. 13)
For data protection purposes, we recommend that you protect AWS account credentials and set up
individual user accounts with AWS Identity and Access Management (IAM), so that each user is given only
the permissions necessary to fulfill their job duties. We also recommend that you secure your data in the
following ways:
9
Service Quotas User Guide
Identity and access management
• Use AWS encryption solutions, along with all default security controls within AWS services.
• Use advanced managed security services such as Amazon Macie, which assists in discovering and
securing personal data that is stored in Amazon S3.
We strongly recommend that you never put sensitive identifying information, such as your customers'
account numbers, into free-form fields such as a Name field. This includes when you work with Service
Quotas or other AWS services using the console, API, AWS CLI, or AWS SDKs. Any data that you enter into
Service Quotas or other services might get picked up for inclusion in diagnostic logs. When you provide
a URL to an external server, don't include credentials information in the URL to validate your request to
that server.
For more information about data protection, see the AWS Shared Responsibility Model and GDPR blog
post on the AWS Security Blog.
By default, IAM users don't have permission to create, view, or modify AWS resources. To allow an IAM
user to access resources such as a load balancer, and to perform tasks, you:
1. Create an IAM policy that grants the IAM user permission to use the specific resources and API actions
they need.
2. Attach the policy to the IAM user or the group that the IAM user belongs to.
When you attach a policy to a user or group of users, it allows or denies the users permission to perform
the specified tasks on the specified resources.
For example, you can use IAM to create users and groups under your AWS account. An IAM user can be
a person, a system, or an application. Then you grant permissions to the users and groups to perform
specific actions on the specified resources using an IAM policy.
An IAM policy is a JSON document that consists of one or more statements. Each statement is structured
as shown in the following example.
{
"Version": "2012-10-17",
"Statement":[{
"Effect": "effect",
"Action": "action",
"Resource": "resource-arn",
"Condition": {
"condition": {
"key":"value"
10
Service Quotas User Guide
API actions for Service Quotas
}
}
}]
}
• Effect— The effect can be Allow or Deny. By default, IAM users don't have permission to use resources
and API actions, so all requests are denied. An explicit allow overrides the default. An explicit deny
overrides any allows.
• Action— The action is the specific API action for which you are granting or denying permission. For
more information about specifying action, see API actions for Service Quotas (p. 11).
• Resource— The resource that's affected by the action. With some Service Quotas API actions, you can
restrict the permissions granted or denied to a specific quota. To do so, specify its Amazon Resource
Name (ARN) in this statement. Otherwise, you can use the * wildcard to specify all Service Quotas
resources. For more information, see Service Quotas resources (p. 11).
• Condition— You can optionally use conditions to control when your policy is in effect. For more
information, see Condition keys for Service Quotas (p. 12).
"Action": "servicequotas:GetServiceQuota"
To specify multiple actions in a single statement, enclose them in square brackets and separate them
with a comma, as shown in the following example.
"Action": [
"servicequotas:ListRequestedServiceQuotaChangeHistory",
"servicequotas:ListRequestedServiceQuotaChangeHistoryByQuota"
]
You can also specify multiple actions using the * wildcard. The following example specifies all API action
names for Service Quotas that start with Get.
"Action": "servicequotas:Get*"
To specify all API actions for Service Quotas, use the * wildcard, as shown in the following example.
"Action": "servicequotas:*"
For the list of API actions for Service Quotas, see Service Quotas Actions.
11
Service Quotas User Guide
Resource-level permissions for Service Quotas
The ARN for a quota has the format shown in the following example.
arn:aws:servicequotas:region-code:account-id:service-code/quota-code
For API actions that don't support resource-level permissions, you must specify the resource statement
shown in the following example.
"Resource": "*"
• PutServiceQuotaIncreaseRequestIntoTemplate
• RequestServiceQuotaIncrease
For more information, see Actions Defined by Service Quotas in the IAM User Guide.
The servicequotas:service key is specific to Service Quotas. The following Service Quotas API
actions support this key:
• PutServiceQuotaIncreaseRequestIntoTemplate
• RequestServiceQuotaIncrease
For more information about global condition keys, see AWS Global Condition Context Keys in the IAM
User Guide.
For a list of AWS services in scope of specific compliance programs, see AWS Services in Scope by
Compliance Program. For general information, see AWS Compliance Programs.
You can download third-party audit reports using AWS Artifact. For more information, see Downloading
Reports in AWS Artifact.
12
Service Quotas User Guide
Resilience
Your compliance responsibility when using Service Quotas is determined by the sensitivity of your data,
your company's compliance objectives, and applicable laws and regulations. AWS provides the following
resources to help with compliance:
• Security and Compliance Quick Start Guides – These deployment guides discuss architectural
considerations and provide steps for deploying security- and compliance-focused baseline
environments on AWS.
• Architecting for HIPAA Security and Compliance Whitepaper – This whitepaper describes how
companies can use AWS to create HIPAA-compliant applications.
• AWS Compliance Resources – This collection of workbooks and guides might apply to your industry
and location.
• Evaluating Resources with Rules in the AWS Config Developer Guide – The AWS Config service assesses
how well your resource configurations comply with internal practices, industry guidelines, and
regulations.
• AWS Security Hub – This AWS service provides a comprehensive view of your security state within AWS
that helps you check your compliance with security industry standards and best practices.
For more information about AWS Regions and Availability Zones, see AWS Global Infrastructure.
You use AWS published API calls to access Service Quotas through the network. Clients must support
Transport Layer Security (TLS) 1.0 or later. We recommend TLS 1.2 or later. Clients must also support
cipher suites with perfect forward secrecy (PFS) such as Ephemeral Diffie-Hellman (DHE) or Elliptic Curve
Ephemeral Diffie-Hellman (ECDHE). Most modern systems such as Java 7 and later support these modes.
Additionally, requests must be signed by using an access key ID and a secret access key that is associated
with an IAM principal. Or you can use the AWS Security Token Service (AWS STS) to generate temporary
security credentials to sign requests.
13
Service Quotas User Guide
Increase requests
Quota Default
Quota Default
Additional ListRequestedServiceQuotaChangeHistoryByQuota 5
requests per second sent in one burst
14
Service Quotas User Guide
Quota Default
Quota Default
Additional DeleteServiceQuotaIncreaseRequestFromTemplate 1
requests per second sent in one burst
15
Service Quotas User Guide
16