import { DynamoDBClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../DynamoDBClient"; import { DescribeLimitsInput, DescribeLimitsOutput } from "../models/models_0"; import { deserializeAws_json1_0DescribeLimitsCommand, serializeAws_json1_0DescribeLimitsCommand, } from "../protocols/Aws_json1_0"; import { getSerdePlugin } from "@aws-sdk/middleware-serde"; import { HttpRequest as __HttpRequest, HttpResponse as __HttpResponse } from "@aws-sdk/protocol-http"; import { Command as $Command } from "@aws-sdk/smithy-client"; import { FinalizeHandlerArguments, Handler, HandlerExecutionContext, MiddlewareStack, HttpHandlerOptions as __HttpHandlerOptions, MetadataBearer as __MetadataBearer, SerdeContext as __SerdeContext, } from "@aws-sdk/types"; export interface DescribeLimitsCommandInput extends DescribeLimitsInput {} export interface DescribeLimitsCommandOutput extends DescribeLimitsOutput, __MetadataBearer {} /** *
Returns the current provisioned-capacity quotas for your AWS account in a Region, both * for the Region as a whole and for any one DynamoDB table that you create there.
*When you establish an AWS account, the account has initial quotas on the maximum read * capacity units and write capacity units that you can provision across all of your * DynamoDB tables in a given Region. Also, there are per-table quotas that apply when you * create a table there. For more information, see Service, Account, and Table * Quotas page in the Amazon DynamoDB Developer * Guide.
* *Although you can increase these quotas by filing a case at AWS Support Center, obtaining the increase is not
* instantaneous. The DescribeLimits action lets you write code to compare the
* capacity you are currently using to those quotas imposed by your account so that you
* have enough time to apply for an increase before you hit a quota.
For example, you could use one of the AWS SDKs to do the following:
* *Call DescribeLimits for a particular Region to obtain your current
* account quotas on provisioned capacity there.
Create a variable to hold the aggregate read capacity units provisioned for all * your tables in that Region, and one to hold the aggregate write capacity units. * Zero them both.
*Call ListTables to obtain a list of all your DynamoDB tables.
For each table name listed by ListTables, do the following:
Call DescribeTable with the table name.
Use the data returned by DescribeTable to add the read capacity units and write capacity
* units provisioned for the table itself to your variables.
If the table has one or more global secondary indexes (GSIs), loop over these GSIs and add their provisioned capacity values to your variables as well.
*Report the account quotas for that Region returned by DescribeLimits, along with
* the total current provisioned capacity levels you have calculated.
This will let you see whether you are getting close to your account-level quotas.
*The per-table quotas apply only when you are creating a new table. They restrict the sum * of the provisioned capacity of the new table itself and all its global secondary * indexes.
*For existing tables and their GSIs, DynamoDB doesn't let you increase provisioned * capacity extremely rapidly, but the only quota that applies is that the aggregate * provisioned capacity over all your tables and GSIs cannot exceed either of the * per-account quotas.
*
* DescribeLimits should only be called periodically. You can expect throttling
* errors if you call it more than once in a minute.
The DescribeLimits Request element has no content.