The quota for capacity groups or launch configurations for this customer has already been reached.
Quota for the resource has already been reached.
The request was rejected because a resource limit has already been met.
The request was rejected because a resource limit has already been met.
The quota for alarms for this customer has already been reached.
Thrown when the total number of user pools has exceeded a preset limit.
This exception is thrown when the subscriber exceeded the limits on the number of objects or operations.
The number of concurrent table requests (cumulative number of tables in the CREATING
, DELETING
or UPDATING
state) exceeds the maximum allowed of 10.
Also, for tables with secondary indexes, only one of those tables can be in the CREATING
state at any point in time. Do not attempt to create more than one such table simultaneously.
The total limit of tables in the ACTIVE
state is 250.
Too many operations for a given AWS account. For example, the number of pipelines exceeds the maximum allowed.
Returned if the request results in a vault or account limit being exceeded.
The request was rejected because it attempted to create resources beyond the current AWS account limits. The error message describes the limit exceeded.
The requested resource exceeds the maximum number allowed, or the number of concurrent stream requests exceeds the maximum number allowed (5).
The request was rejected because a quota was exceeded.
Returned if you have reached the maximum number of resources that can be created.
Returned by any operation if a system imposed limitation has been reached. To address this fault you should either clean up unused resources or increase the limit by contacting AWS.
Examples of these limits include client and server configuration limits such as size, time, number of hops, etc.
Synchronization and serialization issues that apply to NamingException apply directly here. @author Rosanna Lee @author Scott Seligman @since 1.3
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|