UNPKG

261 kBTypeScriptView Raw
1import {Request} from '../lib/request';
2import {Response} from '../lib/response';
3import {AWSError} from '../lib/error';
4import {DynamoDBCustomizations} from '../lib/services/dynamodb';
5import {WaiterConfiguration} from '../lib/service';
6import {ServiceConfigurationOptions} from '../lib/service';
7import {ConfigBase as Config} from '../lib/config';
8import {DocumentClient as document_client} from '../lib/dynamodb/document_client';
9import {Converter as converter} from '../lib/dynamodb/converter';
10interface Blob {}
11declare class DynamoDB extends DynamoDBCustomizations {
12 /**
13 * Constructs a service object. This object has one method for each API operation.
14 */
15 constructor(options?: DynamoDB.Types.ClientConfiguration)
16 config: Config & DynamoDB.Types.ClientConfiguration;
17 /**
18 * The BatchGetItem operation returns the attributes of one or more items from one or more tables. You identify requested items by primary key. A single operation can retrieve up to 16 MB of data, which can contain as many as 100 items. BatchGetItem returns a partial result if the response size limit is exceeded, the table's provisioned throughput is exceeded, or an internal processing failure occurs. If a partial result is returned, the operation returns a value for UnprocessedKeys. You can use this value to retry the operation starting with the next item to get. If you request more than 100 items, BatchGetItem returns a ValidationException with the message "Too many items requested for the BatchGetItem call." For example, if you ask to retrieve 100 items, but each individual item is 300 KB in size, the system returns 52 items (so as not to exceed the 16 MB limit). It also returns an appropriate UnprocessedKeys value so you can get the next page of results. If desired, your application can include its own logic to assemble the pages of results into one dataset. If none of the items can be processed due to insufficient provisioned throughput on all of the tables in the request, then BatchGetItem returns a ProvisionedThroughputExceededException. If at least one of the items is successfully processed, then BatchGetItem completes successfully, while returning the keys of the unread items in UnprocessedKeys. If DynamoDB returns any unprocessed items, you should retry the batch operation on those items. However, we strongly recommend that you use an exponential backoff algorithm. If you retry the batch operation immediately, the underlying read or write requests can still fail due to throttling on the individual tables. If you delay the batch operation using exponential backoff, the individual requests in the batch are much more likely to succeed. For more information, see Batch Operations and Error Handling in the Amazon DynamoDB Developer Guide. By default, BatchGetItem performs eventually consistent reads on every table in the request. If you want strongly consistent reads instead, you can set ConsistentRead to true for any or all tables. In order to minimize response latency, BatchGetItem retrieves items in parallel. When designing your application, keep in mind that DynamoDB does not return items in any particular order. To help parse the response by item, include the primary key values for the items in your request in the ProjectionExpression parameter. If a requested item does not exist, it is not returned in the result. Requests for nonexistent items consume the minimum read capacity units according to the type of read. For more information, see Working with Tables in the Amazon DynamoDB Developer Guide.
19 */
20 batchGetItem(params: DynamoDB.Types.BatchGetItemInput, callback?: (err: AWSError, data: DynamoDB.Types.BatchGetItemOutput) => void): Request<DynamoDB.Types.BatchGetItemOutput, AWSError>;
21 /**
22 * The BatchGetItem operation returns the attributes of one or more items from one or more tables. You identify requested items by primary key. A single operation can retrieve up to 16 MB of data, which can contain as many as 100 items. BatchGetItem returns a partial result if the response size limit is exceeded, the table's provisioned throughput is exceeded, or an internal processing failure occurs. If a partial result is returned, the operation returns a value for UnprocessedKeys. You can use this value to retry the operation starting with the next item to get. If you request more than 100 items, BatchGetItem returns a ValidationException with the message "Too many items requested for the BatchGetItem call." For example, if you ask to retrieve 100 items, but each individual item is 300 KB in size, the system returns 52 items (so as not to exceed the 16 MB limit). It also returns an appropriate UnprocessedKeys value so you can get the next page of results. If desired, your application can include its own logic to assemble the pages of results into one dataset. If none of the items can be processed due to insufficient provisioned throughput on all of the tables in the request, then BatchGetItem returns a ProvisionedThroughputExceededException. If at least one of the items is successfully processed, then BatchGetItem completes successfully, while returning the keys of the unread items in UnprocessedKeys. If DynamoDB returns any unprocessed items, you should retry the batch operation on those items. However, we strongly recommend that you use an exponential backoff algorithm. If you retry the batch operation immediately, the underlying read or write requests can still fail due to throttling on the individual tables. If you delay the batch operation using exponential backoff, the individual requests in the batch are much more likely to succeed. For more information, see Batch Operations and Error Handling in the Amazon DynamoDB Developer Guide. By default, BatchGetItem performs eventually consistent reads on every table in the request. If you want strongly consistent reads instead, you can set ConsistentRead to true for any or all tables. In order to minimize response latency, BatchGetItem retrieves items in parallel. When designing your application, keep in mind that DynamoDB does not return items in any particular order. To help parse the response by item, include the primary key values for the items in your request in the ProjectionExpression parameter. If a requested item does not exist, it is not returned in the result. Requests for nonexistent items consume the minimum read capacity units according to the type of read. For more information, see Working with Tables in the Amazon DynamoDB Developer Guide.
23 */
24 batchGetItem(callback?: (err: AWSError, data: DynamoDB.Types.BatchGetItemOutput) => void): Request<DynamoDB.Types.BatchGetItemOutput, AWSError>;
25 /**
26 * The BatchWriteItem operation puts or deletes multiple items in one or more tables. A single call to BatchWriteItem can write up to 16 MB of data, which can comprise as many as 25 put or delete requests. Individual items to be written can be as large as 400 KB. BatchWriteItem cannot update items. To update items, use the UpdateItem action. The individual PutItem and DeleteItem operations specified in BatchWriteItem are atomic; however BatchWriteItem as a whole is not. If any requested operations fail because the table's provisioned throughput is exceeded or an internal processing failure occurs, the failed operations are returned in the UnprocessedItems response parameter. You can investigate and optionally resend the requests. Typically, you would call BatchWriteItem in a loop. Each iteration would check for unprocessed items and submit a new BatchWriteItem request with those unprocessed items until all items have been processed. If none of the items can be processed due to insufficient provisioned throughput on all of the tables in the request, then BatchWriteItem returns a ProvisionedThroughputExceededException. If DynamoDB returns any unprocessed items, you should retry the batch operation on those items. However, we strongly recommend that you use an exponential backoff algorithm. If you retry the batch operation immediately, the underlying read or write requests can still fail due to throttling on the individual tables. If you delay the batch operation using exponential backoff, the individual requests in the batch are much more likely to succeed. For more information, see Batch Operations and Error Handling in the Amazon DynamoDB Developer Guide. With BatchWriteItem, you can efficiently write or delete large amounts of data, such as from Amazon EMR, or copy data from another database into DynamoDB. In order to improve performance with these large-scale operations, BatchWriteItem does not behave in the same way as individual PutItem and DeleteItem calls would. For example, you cannot specify conditions on individual put and delete requests, and BatchWriteItem does not return deleted items in the response. If you use a programming language that supports concurrency, you can use threads to write items in parallel. Your application must include the necessary logic to manage the threads. With languages that don't support threading, you must update or delete the specified items one at a time. In both situations, BatchWriteItem performs the specified put and delete operations in parallel, giving you the power of the thread pool approach without having to introduce complexity into your application. Parallel processing reduces latency, but each specified put and delete request consumes the same number of write capacity units whether it is processed in parallel or not. Delete operations on nonexistent items consume one write capacity unit. If one or more of the following is true, DynamoDB rejects the entire batch write operation: One or more tables specified in the BatchWriteItem request does not exist. Primary key attributes specified on an item in the request do not match those in the corresponding table's primary key schema. You try to perform multiple operations on the same item in the same BatchWriteItem request. For example, you cannot put and delete the same item in the same BatchWriteItem request. Your request contains at least two items with identical hash and range keys (which essentially is two put operations). There are more than 25 requests in the batch. Any individual item in a batch exceeds 400 KB. The total request size exceeds 16 MB.
27 */
28 batchWriteItem(params: DynamoDB.Types.BatchWriteItemInput, callback?: (err: AWSError, data: DynamoDB.Types.BatchWriteItemOutput) => void): Request<DynamoDB.Types.BatchWriteItemOutput, AWSError>;
29 /**
30 * The BatchWriteItem operation puts or deletes multiple items in one or more tables. A single call to BatchWriteItem can write up to 16 MB of data, which can comprise as many as 25 put or delete requests. Individual items to be written can be as large as 400 KB. BatchWriteItem cannot update items. To update items, use the UpdateItem action. The individual PutItem and DeleteItem operations specified in BatchWriteItem are atomic; however BatchWriteItem as a whole is not. If any requested operations fail because the table's provisioned throughput is exceeded or an internal processing failure occurs, the failed operations are returned in the UnprocessedItems response parameter. You can investigate and optionally resend the requests. Typically, you would call BatchWriteItem in a loop. Each iteration would check for unprocessed items and submit a new BatchWriteItem request with those unprocessed items until all items have been processed. If none of the items can be processed due to insufficient provisioned throughput on all of the tables in the request, then BatchWriteItem returns a ProvisionedThroughputExceededException. If DynamoDB returns any unprocessed items, you should retry the batch operation on those items. However, we strongly recommend that you use an exponential backoff algorithm. If you retry the batch operation immediately, the underlying read or write requests can still fail due to throttling on the individual tables. If you delay the batch operation using exponential backoff, the individual requests in the batch are much more likely to succeed. For more information, see Batch Operations and Error Handling in the Amazon DynamoDB Developer Guide. With BatchWriteItem, you can efficiently write or delete large amounts of data, such as from Amazon EMR, or copy data from another database into DynamoDB. In order to improve performance with these large-scale operations, BatchWriteItem does not behave in the same way as individual PutItem and DeleteItem calls would. For example, you cannot specify conditions on individual put and delete requests, and BatchWriteItem does not return deleted items in the response. If you use a programming language that supports concurrency, you can use threads to write items in parallel. Your application must include the necessary logic to manage the threads. With languages that don't support threading, you must update or delete the specified items one at a time. In both situations, BatchWriteItem performs the specified put and delete operations in parallel, giving you the power of the thread pool approach without having to introduce complexity into your application. Parallel processing reduces latency, but each specified put and delete request consumes the same number of write capacity units whether it is processed in parallel or not. Delete operations on nonexistent items consume one write capacity unit. If one or more of the following is true, DynamoDB rejects the entire batch write operation: One or more tables specified in the BatchWriteItem request does not exist. Primary key attributes specified on an item in the request do not match those in the corresponding table's primary key schema. You try to perform multiple operations on the same item in the same BatchWriteItem request. For example, you cannot put and delete the same item in the same BatchWriteItem request. Your request contains at least two items with identical hash and range keys (which essentially is two put operations). There are more than 25 requests in the batch. Any individual item in a batch exceeds 400 KB. The total request size exceeds 16 MB.
31 */
32 batchWriteItem(callback?: (err: AWSError, data: DynamoDB.Types.BatchWriteItemOutput) => void): Request<DynamoDB.Types.BatchWriteItemOutput, AWSError>;
33 /**
34 * Creates a backup for an existing table. Each time you create an on-demand backup, the entire table data is backed up. There is no limit to the number of on-demand backups that can be taken. When you create an on-demand backup, a time marker of the request is cataloged, and the backup is created asynchronously, by applying all changes until the time of the request to the last full table snapshot. Backup requests are processed instantaneously and become available for restore within minutes. You can call CreateBackup at a maximum rate of 50 times per second. All backups in DynamoDB work without consuming any provisioned throughput on the table. If you submit a backup request on 2018-12-14 at 14:25:00, the backup is guaranteed to contain all data committed to the table up to 14:24:00, and data committed after 14:26:00 will not be. The backup might contain data modifications made between 14:24:00 and 14:26:00. On-demand backup does not support causal consistency. Along with data, the following are also included on the backups: Global secondary indexes (GSIs) Local secondary indexes (LSIs) Streams Provisioned read and write capacity
35 */
36 createBackup(params: DynamoDB.Types.CreateBackupInput, callback?: (err: AWSError, data: DynamoDB.Types.CreateBackupOutput) => void): Request<DynamoDB.Types.CreateBackupOutput, AWSError>;
37 /**
38 * Creates a backup for an existing table. Each time you create an on-demand backup, the entire table data is backed up. There is no limit to the number of on-demand backups that can be taken. When you create an on-demand backup, a time marker of the request is cataloged, and the backup is created asynchronously, by applying all changes until the time of the request to the last full table snapshot. Backup requests are processed instantaneously and become available for restore within minutes. You can call CreateBackup at a maximum rate of 50 times per second. All backups in DynamoDB work without consuming any provisioned throughput on the table. If you submit a backup request on 2018-12-14 at 14:25:00, the backup is guaranteed to contain all data committed to the table up to 14:24:00, and data committed after 14:26:00 will not be. The backup might contain data modifications made between 14:24:00 and 14:26:00. On-demand backup does not support causal consistency. Along with data, the following are also included on the backups: Global secondary indexes (GSIs) Local secondary indexes (LSIs) Streams Provisioned read and write capacity
39 */
40 createBackup(callback?: (err: AWSError, data: DynamoDB.Types.CreateBackupOutput) => void): Request<DynamoDB.Types.CreateBackupOutput, AWSError>;
41 /**
42 * Creates a global table from an existing table. A global table creates a replication relationship between two or more DynamoDB tables with the same table name in the provided Regions. If you want to add a new replica table to a global table, each of the following conditions must be true: The table must have the same primary key as all of the other replicas. The table must have the same name as all of the other replicas. The table must have DynamoDB Streams enabled, with the stream containing both the new and the old images of the item. None of the replica tables in the global table can contain any data. If global secondary indexes are specified, then the following conditions must also be met: The global secondary indexes must have the same name. The global secondary indexes must have the same hash key and sort key (if present). Write capacity settings should be set consistently across your replica tables and secondary indexes. DynamoDB strongly recommends enabling auto scaling to manage the write capacity settings for all of your global tables replicas and indexes. If you prefer to manage write capacity settings manually, you should provision equal replicated write capacity units to your replica tables. You should also provision equal replicated write capacity units to matching secondary indexes across your global table.
43 */
44 createGlobalTable(params: DynamoDB.Types.CreateGlobalTableInput, callback?: (err: AWSError, data: DynamoDB.Types.CreateGlobalTableOutput) => void): Request<DynamoDB.Types.CreateGlobalTableOutput, AWSError>;
45 /**
46 * Creates a global table from an existing table. A global table creates a replication relationship between two or more DynamoDB tables with the same table name in the provided Regions. If you want to add a new replica table to a global table, each of the following conditions must be true: The table must have the same primary key as all of the other replicas. The table must have the same name as all of the other replicas. The table must have DynamoDB Streams enabled, with the stream containing both the new and the old images of the item. None of the replica tables in the global table can contain any data. If global secondary indexes are specified, then the following conditions must also be met: The global secondary indexes must have the same name. The global secondary indexes must have the same hash key and sort key (if present). Write capacity settings should be set consistently across your replica tables and secondary indexes. DynamoDB strongly recommends enabling auto scaling to manage the write capacity settings for all of your global tables replicas and indexes. If you prefer to manage write capacity settings manually, you should provision equal replicated write capacity units to your replica tables. You should also provision equal replicated write capacity units to matching secondary indexes across your global table.
47 */
48 createGlobalTable(callback?: (err: AWSError, data: DynamoDB.Types.CreateGlobalTableOutput) => void): Request<DynamoDB.Types.CreateGlobalTableOutput, AWSError>;
49 /**
50 * The CreateTable operation adds a new table to your account. In an AWS account, table names must be unique within each Region. That is, you can have two tables with same name if you create the tables in different Regions. CreateTable is an asynchronous operation. Upon receiving a CreateTable request, DynamoDB immediately returns a response with a TableStatus of CREATING. After the table is created, DynamoDB sets the TableStatus to ACTIVE. You can perform read and write operations only on an ACTIVE table. You can optionally define secondary indexes on the new table, as part of the CreateTable operation. If you want to create multiple tables with secondary indexes on them, you must create the tables sequentially. Only one table with secondary indexes can be in the CREATING state at any given time. You can use the DescribeTable action to check the table status.
51 */
52 createTable(params: DynamoDB.Types.CreateTableInput, callback?: (err: AWSError, data: DynamoDB.Types.CreateTableOutput) => void): Request<DynamoDB.Types.CreateTableOutput, AWSError>;
53 /**
54 * The CreateTable operation adds a new table to your account. In an AWS account, table names must be unique within each Region. That is, you can have two tables with same name if you create the tables in different Regions. CreateTable is an asynchronous operation. Upon receiving a CreateTable request, DynamoDB immediately returns a response with a TableStatus of CREATING. After the table is created, DynamoDB sets the TableStatus to ACTIVE. You can perform read and write operations only on an ACTIVE table. You can optionally define secondary indexes on the new table, as part of the CreateTable operation. If you want to create multiple tables with secondary indexes on them, you must create the tables sequentially. Only one table with secondary indexes can be in the CREATING state at any given time. You can use the DescribeTable action to check the table status.
55 */
56 createTable(callback?: (err: AWSError, data: DynamoDB.Types.CreateTableOutput) => void): Request<DynamoDB.Types.CreateTableOutput, AWSError>;
57 /**
58 * Deletes an existing backup of a table. You can call DeleteBackup at a maximum rate of 10 times per second.
59 */
60 deleteBackup(params: DynamoDB.Types.DeleteBackupInput, callback?: (err: AWSError, data: DynamoDB.Types.DeleteBackupOutput) => void): Request<DynamoDB.Types.DeleteBackupOutput, AWSError>;
61 /**
62 * Deletes an existing backup of a table. You can call DeleteBackup at a maximum rate of 10 times per second.
63 */
64 deleteBackup(callback?: (err: AWSError, data: DynamoDB.Types.DeleteBackupOutput) => void): Request<DynamoDB.Types.DeleteBackupOutput, AWSError>;
65 /**
66 * Deletes a single item in a table by primary key. You can perform a conditional delete operation that deletes the item if it exists, or if it has an expected attribute value. In addition to deleting an item, you can also return the item's attribute values in the same operation, using the ReturnValues parameter. Unless you specify conditions, the DeleteItem is an idempotent operation; running it multiple times on the same item or attribute does not result in an error response. Conditional deletes are useful for deleting items only if specific conditions are met. If those conditions are met, DynamoDB performs the delete. Otherwise, the item is not deleted.
67 */
68 deleteItem(params: DynamoDB.Types.DeleteItemInput, callback?: (err: AWSError, data: DynamoDB.Types.DeleteItemOutput) => void): Request<DynamoDB.Types.DeleteItemOutput, AWSError>;
69 /**
70 * Deletes a single item in a table by primary key. You can perform a conditional delete operation that deletes the item if it exists, or if it has an expected attribute value. In addition to deleting an item, you can also return the item's attribute values in the same operation, using the ReturnValues parameter. Unless you specify conditions, the DeleteItem is an idempotent operation; running it multiple times on the same item or attribute does not result in an error response. Conditional deletes are useful for deleting items only if specific conditions are met. If those conditions are met, DynamoDB performs the delete. Otherwise, the item is not deleted.
71 */
72 deleteItem(callback?: (err: AWSError, data: DynamoDB.Types.DeleteItemOutput) => void): Request<DynamoDB.Types.DeleteItemOutput, AWSError>;
73 /**
74 * The DeleteTable operation deletes a table and all of its items. After a DeleteTable request, the specified table is in the DELETING state until DynamoDB completes the deletion. If the table is in the ACTIVE state, you can delete it. If a table is in CREATING or UPDATING states, then DynamoDB returns a ResourceInUseException. If the specified table does not exist, DynamoDB returns a ResourceNotFoundException. If table is already in the DELETING state, no error is returned. DynamoDB might continue to accept data read and write operations, such as GetItem and PutItem, on a table in the DELETING state until the table deletion is complete. When you delete a table, any indexes on that table are also deleted. If you have DynamoDB Streams enabled on the table, then the corresponding stream on that table goes into the DISABLED state, and the stream is automatically deleted after 24 hours. Use the DescribeTable action to check the status of the table.
75 */
76 deleteTable(params: DynamoDB.Types.DeleteTableInput, callback?: (err: AWSError, data: DynamoDB.Types.DeleteTableOutput) => void): Request<DynamoDB.Types.DeleteTableOutput, AWSError>;
77 /**
78 * The DeleteTable operation deletes a table and all of its items. After a DeleteTable request, the specified table is in the DELETING state until DynamoDB completes the deletion. If the table is in the ACTIVE state, you can delete it. If a table is in CREATING or UPDATING states, then DynamoDB returns a ResourceInUseException. If the specified table does not exist, DynamoDB returns a ResourceNotFoundException. If table is already in the DELETING state, no error is returned. DynamoDB might continue to accept data read and write operations, such as GetItem and PutItem, on a table in the DELETING state until the table deletion is complete. When you delete a table, any indexes on that table are also deleted. If you have DynamoDB Streams enabled on the table, then the corresponding stream on that table goes into the DISABLED state, and the stream is automatically deleted after 24 hours. Use the DescribeTable action to check the status of the table.
79 */
80 deleteTable(callback?: (err: AWSError, data: DynamoDB.Types.DeleteTableOutput) => void): Request<DynamoDB.Types.DeleteTableOutput, AWSError>;
81 /**
82 * Describes an existing backup of a table. You can call DescribeBackup at a maximum rate of 10 times per second.
83 */
84 describeBackup(params: DynamoDB.Types.DescribeBackupInput, callback?: (err: AWSError, data: DynamoDB.Types.DescribeBackupOutput) => void): Request<DynamoDB.Types.DescribeBackupOutput, AWSError>;
85 /**
86 * Describes an existing backup of a table. You can call DescribeBackup at a maximum rate of 10 times per second.
87 */
88 describeBackup(callback?: (err: AWSError, data: DynamoDB.Types.DescribeBackupOutput) => void): Request<DynamoDB.Types.DescribeBackupOutput, AWSError>;
89 /**
90 * Checks the status of continuous backups and point in time recovery on the specified table. Continuous backups are ENABLED on all tables at table creation. If point in time recovery is enabled, PointInTimeRecoveryStatus will be set to ENABLED. After continuous backups and point in time recovery are enabled, you can restore to any point in time within EarliestRestorableDateTime and LatestRestorableDateTime. LatestRestorableDateTime is typically 5 minutes before the current time. You can restore your table to any point in time during the last 35 days. You can call DescribeContinuousBackups at a maximum rate of 10 times per second.
91 */
92 describeContinuousBackups(params: DynamoDB.Types.DescribeContinuousBackupsInput, callback?: (err: AWSError, data: DynamoDB.Types.DescribeContinuousBackupsOutput) => void): Request<DynamoDB.Types.DescribeContinuousBackupsOutput, AWSError>;
93 /**
94 * Checks the status of continuous backups and point in time recovery on the specified table. Continuous backups are ENABLED on all tables at table creation. If point in time recovery is enabled, PointInTimeRecoveryStatus will be set to ENABLED. After continuous backups and point in time recovery are enabled, you can restore to any point in time within EarliestRestorableDateTime and LatestRestorableDateTime. LatestRestorableDateTime is typically 5 minutes before the current time. You can restore your table to any point in time during the last 35 days. You can call DescribeContinuousBackups at a maximum rate of 10 times per second.
95 */
96 describeContinuousBackups(callback?: (err: AWSError, data: DynamoDB.Types.DescribeContinuousBackupsOutput) => void): Request<DynamoDB.Types.DescribeContinuousBackupsOutput, AWSError>;
97 /**
98 * Returns the regional endpoint information.
99 */
100 describeEndpoints(params: DynamoDB.Types.DescribeEndpointsRequest, callback?: (err: AWSError, data: DynamoDB.Types.DescribeEndpointsResponse) => void): Request<DynamoDB.Types.DescribeEndpointsResponse, AWSError>;
101 /**
102 * Returns the regional endpoint information.
103 */
104 describeEndpoints(callback?: (err: AWSError, data: DynamoDB.Types.DescribeEndpointsResponse) => void): Request<DynamoDB.Types.DescribeEndpointsResponse, AWSError>;
105 /**
106 * Returns information about the specified global table.
107 */
108 describeGlobalTable(params: DynamoDB.Types.DescribeGlobalTableInput, callback?: (err: AWSError, data: DynamoDB.Types.DescribeGlobalTableOutput) => void): Request<DynamoDB.Types.DescribeGlobalTableOutput, AWSError>;
109 /**
110 * Returns information about the specified global table.
111 */
112 describeGlobalTable(callback?: (err: AWSError, data: DynamoDB.Types.DescribeGlobalTableOutput) => void): Request<DynamoDB.Types.DescribeGlobalTableOutput, AWSError>;
113 /**
114 * Describes Region-specific settings for a global table.
115 */
116 describeGlobalTableSettings(params: DynamoDB.Types.DescribeGlobalTableSettingsInput, callback?: (err: AWSError, data: DynamoDB.Types.DescribeGlobalTableSettingsOutput) => void): Request<DynamoDB.Types.DescribeGlobalTableSettingsOutput, AWSError>;
117 /**
118 * Describes Region-specific settings for a global table.
119 */
120 describeGlobalTableSettings(callback?: (err: AWSError, data: DynamoDB.Types.DescribeGlobalTableSettingsOutput) => void): Request<DynamoDB.Types.DescribeGlobalTableSettingsOutput, AWSError>;
121 /**
122 * Returns the current provisioned-capacity limits 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 limits 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 limits that apply when you create a table there. For more information, see Limits page in the Amazon DynamoDB Developer Guide. Although you can increase these limits 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 limits imposed by your account so that you have enough time to apply for an increase before you hit a limit. 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 limits 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 limits 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 limits. The per-table limits 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 upper limit that applies is that the aggregate provisioned capacity over all your tables and GSIs cannot exceed either of the per-account limits. 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.
123 */
124 describeLimits(params: DynamoDB.Types.DescribeLimitsInput, callback?: (err: AWSError, data: DynamoDB.Types.DescribeLimitsOutput) => void): Request<DynamoDB.Types.DescribeLimitsOutput, AWSError>;
125 /**
126 * Returns the current provisioned-capacity limits 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 limits 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 limits that apply when you create a table there. For more information, see Limits page in the Amazon DynamoDB Developer Guide. Although you can increase these limits 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 limits imposed by your account so that you have enough time to apply for an increase before you hit a limit. 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 limits 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 limits 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 limits. The per-table limits 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 upper limit that applies is that the aggregate provisioned capacity over all your tables and GSIs cannot exceed either of the per-account limits. 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.
127 */
128 describeLimits(callback?: (err: AWSError, data: DynamoDB.Types.DescribeLimitsOutput) => void): Request<DynamoDB.Types.DescribeLimitsOutput, AWSError>;
129 /**
130 * Returns information about the table, including the current status of the table, when it was created, the primary key schema, and any indexes on the table. If you issue a DescribeTable request immediately after a CreateTable request, DynamoDB might return a ResourceNotFoundException. This is because DescribeTable uses an eventually consistent query, and the metadata for your table might not be available at that moment. Wait for a few seconds, and then try the DescribeTable request again.
131 */
132 describeTable(params: DynamoDB.Types.DescribeTableInput, callback?: (err: AWSError, data: DynamoDB.Types.DescribeTableOutput) => void): Request<DynamoDB.Types.DescribeTableOutput, AWSError>;
133 /**
134 * Returns information about the table, including the current status of the table, when it was created, the primary key schema, and any indexes on the table. If you issue a DescribeTable request immediately after a CreateTable request, DynamoDB might return a ResourceNotFoundException. This is because DescribeTable uses an eventually consistent query, and the metadata for your table might not be available at that moment. Wait for a few seconds, and then try the DescribeTable request again.
135 */
136 describeTable(callback?: (err: AWSError, data: DynamoDB.Types.DescribeTableOutput) => void): Request<DynamoDB.Types.DescribeTableOutput, AWSError>;
137 /**
138 * Gives a description of the Time to Live (TTL) status on the specified table.
139 */
140 describeTimeToLive(params: DynamoDB.Types.DescribeTimeToLiveInput, callback?: (err: AWSError, data: DynamoDB.Types.DescribeTimeToLiveOutput) => void): Request<DynamoDB.Types.DescribeTimeToLiveOutput, AWSError>;
141 /**
142 * Gives a description of the Time to Live (TTL) status on the specified table.
143 */
144 describeTimeToLive(callback?: (err: AWSError, data: DynamoDB.Types.DescribeTimeToLiveOutput) => void): Request<DynamoDB.Types.DescribeTimeToLiveOutput, AWSError>;
145 /**
146 * The GetItem operation returns a set of attributes for the item with the given primary key. If there is no matching item, GetItem does not return any data and there will be no Item element in the response. GetItem provides an eventually consistent read by default. If your application requires a strongly consistent read, set ConsistentRead to true. Although a strongly consistent read might take more time than an eventually consistent read, it always returns the last updated value.
147 */
148 getItem(params: DynamoDB.Types.GetItemInput, callback?: (err: AWSError, data: DynamoDB.Types.GetItemOutput) => void): Request<DynamoDB.Types.GetItemOutput, AWSError>;
149 /**
150 * The GetItem operation returns a set of attributes for the item with the given primary key. If there is no matching item, GetItem does not return any data and there will be no Item element in the response. GetItem provides an eventually consistent read by default. If your application requires a strongly consistent read, set ConsistentRead to true. Although a strongly consistent read might take more time than an eventually consistent read, it always returns the last updated value.
151 */
152 getItem(callback?: (err: AWSError, data: DynamoDB.Types.GetItemOutput) => void): Request<DynamoDB.Types.GetItemOutput, AWSError>;
153 /**
154 * List backups associated with an AWS account. To list backups for a given table, specify TableName. ListBackups returns a paginated list of results with at most 1 MB worth of items in a page. You can also specify a limit for the maximum number of entries to be returned in a page. In the request, start time is inclusive, but end time is exclusive. Note that these limits are for the time at which the original backup was requested. You can call ListBackups a maximum of five times per second.
155 */
156 listBackups(params: DynamoDB.Types.ListBackupsInput, callback?: (err: AWSError, data: DynamoDB.Types.ListBackupsOutput) => void): Request<DynamoDB.Types.ListBackupsOutput, AWSError>;
157 /**
158 * List backups associated with an AWS account. To list backups for a given table, specify TableName. ListBackups returns a paginated list of results with at most 1 MB worth of items in a page. You can also specify a limit for the maximum number of entries to be returned in a page. In the request, start time is inclusive, but end time is exclusive. Note that these limits are for the time at which the original backup was requested. You can call ListBackups a maximum of five times per second.
159 */
160 listBackups(callback?: (err: AWSError, data: DynamoDB.Types.ListBackupsOutput) => void): Request<DynamoDB.Types.ListBackupsOutput, AWSError>;
161 /**
162 * Lists all global tables that have a replica in the specified Region.
163 */
164 listGlobalTables(params: DynamoDB.Types.ListGlobalTablesInput, callback?: (err: AWSError, data: DynamoDB.Types.ListGlobalTablesOutput) => void): Request<DynamoDB.Types.ListGlobalTablesOutput, AWSError>;
165 /**
166 * Lists all global tables that have a replica in the specified Region.
167 */
168 listGlobalTables(callback?: (err: AWSError, data: DynamoDB.Types.ListGlobalTablesOutput) => void): Request<DynamoDB.Types.ListGlobalTablesOutput, AWSError>;
169 /**
170 * Returns an array of table names associated with the current account and endpoint. The output from ListTables is paginated, with each page returning a maximum of 100 table names.
171 */
172 listTables(params: DynamoDB.Types.ListTablesInput, callback?: (err: AWSError, data: DynamoDB.Types.ListTablesOutput) => void): Request<DynamoDB.Types.ListTablesOutput, AWSError>;
173 /**
174 * Returns an array of table names associated with the current account and endpoint. The output from ListTables is paginated, with each page returning a maximum of 100 table names.
175 */
176 listTables(callback?: (err: AWSError, data: DynamoDB.Types.ListTablesOutput) => void): Request<DynamoDB.Types.ListTablesOutput, AWSError>;
177 /**
178 * List all tags on an Amazon DynamoDB resource. You can call ListTagsOfResource up to 10 times per second, per account. For an overview on tagging DynamoDB resources, see Tagging for DynamoDB in the Amazon DynamoDB Developer Guide.
179 */
180 listTagsOfResource(params: DynamoDB.Types.ListTagsOfResourceInput, callback?: (err: AWSError, data: DynamoDB.Types.ListTagsOfResourceOutput) => void): Request<DynamoDB.Types.ListTagsOfResourceOutput, AWSError>;
181 /**
182 * List all tags on an Amazon DynamoDB resource. You can call ListTagsOfResource up to 10 times per second, per account. For an overview on tagging DynamoDB resources, see Tagging for DynamoDB in the Amazon DynamoDB Developer Guide.
183 */
184 listTagsOfResource(callback?: (err: AWSError, data: DynamoDB.Types.ListTagsOfResourceOutput) => void): Request<DynamoDB.Types.ListTagsOfResourceOutput, AWSError>;
185 /**
186 * Creates a new item, or replaces an old item with a new item. If an item that has the same primary key as the new item already exists in the specified table, the new item completely replaces the existing item. You can perform a conditional put operation (add a new item if one with the specified primary key doesn't exist), or replace an existing item if it has certain attribute values. You can return the item's attribute values in the same operation, using the ReturnValues parameter. This topic provides general information about the PutItem API. For information on how to call the PutItem API using the AWS SDK in specific languages, see the following: PutItem in the AWS Command Line Interface PutItem in the AWS SDK for .NET PutItem in the AWS SDK for C++ PutItem in the AWS SDK for Go PutItem in the AWS SDK for Java PutItem in the AWS SDK for JavaScript PutItem in the AWS SDK for PHP V3 PutItem in the AWS SDK for Python PutItem in the AWS SDK for Ruby V2 When you add an item, the primary key attributes are the only required attributes. Attribute values cannot be null. String and Binary type attributes must have lengths greater than zero. Set type attributes cannot be empty. Requests with empty values will be rejected with a ValidationException exception. To prevent a new item from replacing an existing item, use a conditional expression that contains the attribute_not_exists function with the name of the attribute being used as the partition key for the table. Since every record must contain that attribute, the attribute_not_exists function will only succeed if no matching item exists. For more information about PutItem, see Working with Items in the Amazon DynamoDB Developer Guide.
187 */
188 putItem(params: DynamoDB.Types.PutItemInput, callback?: (err: AWSError, data: DynamoDB.Types.PutItemOutput) => void): Request<DynamoDB.Types.PutItemOutput, AWSError>;
189 /**
190 * Creates a new item, or replaces an old item with a new item. If an item that has the same primary key as the new item already exists in the specified table, the new item completely replaces the existing item. You can perform a conditional put operation (add a new item if one with the specified primary key doesn't exist), or replace an existing item if it has certain attribute values. You can return the item's attribute values in the same operation, using the ReturnValues parameter. This topic provides general information about the PutItem API. For information on how to call the PutItem API using the AWS SDK in specific languages, see the following: PutItem in the AWS Command Line Interface PutItem in the AWS SDK for .NET PutItem in the AWS SDK for C++ PutItem in the AWS SDK for Go PutItem in the AWS SDK for Java PutItem in the AWS SDK for JavaScript PutItem in the AWS SDK for PHP V3 PutItem in the AWS SDK for Python PutItem in the AWS SDK for Ruby V2 When you add an item, the primary key attributes are the only required attributes. Attribute values cannot be null. String and Binary type attributes must have lengths greater than zero. Set type attributes cannot be empty. Requests with empty values will be rejected with a ValidationException exception. To prevent a new item from replacing an existing item, use a conditional expression that contains the attribute_not_exists function with the name of the attribute being used as the partition key for the table. Since every record must contain that attribute, the attribute_not_exists function will only succeed if no matching item exists. For more information about PutItem, see Working with Items in the Amazon DynamoDB Developer Guide.
191 */
192 putItem(callback?: (err: AWSError, data: DynamoDB.Types.PutItemOutput) => void): Request<DynamoDB.Types.PutItemOutput, AWSError>;
193 /**
194 * The Query operation finds items based on primary key values. You can query any table or secondary index that has a composite primary key (a partition key and a sort key). Use the KeyConditionExpression parameter to provide a specific value for the partition key. The Query operation will return all of the items from the table or index with that partition key value. You can optionally narrow the scope of the Query operation by specifying a sort key value and a comparison operator in KeyConditionExpression. To further refine the Query results, you can optionally provide a FilterExpression. A FilterExpression determines which items within the results should be returned to you. All of the other results are discarded. A Query operation always returns a result set. If no matching items are found, the result set will be empty. Queries that do not return results consume the minimum number of read capacity units for that type of read operation. DynamoDB calculates the number of read capacity units consumed based on item size, not on the amount of data that is returned to an application. The number of capacity units consumed will be the same whether you request all of the attributes (the default behavior) or just some of them (using a projection expression). The number will also be the same whether or not you use a FilterExpression. Query results are always sorted by the sort key value. If the data type of the sort key is Number, the results are returned in numeric order; otherwise, the results are returned in order of UTF-8 bytes. By default, the sort order is ascending. To reverse the order, set the ScanIndexForward parameter to false. A single Query operation will read up to the maximum number of items set (if using the Limit parameter) or a maximum of 1 MB of data and then apply any filtering to the results using FilterExpression. If LastEvaluatedKey is present in the response, you will need to paginate the result set. For more information, see Paginating the Results in the Amazon DynamoDB Developer Guide. FilterExpression is applied after a Query finishes, but before the results are returned. A FilterExpression cannot contain partition key or sort key attributes. You need to specify those attributes in the KeyConditionExpression. A Query operation can return an empty result set and a LastEvaluatedKey if all the items read for the page of results are filtered out. You can query a table, a local secondary index, or a global secondary index. For a query on a table or on a local secondary index, you can set the ConsistentRead parameter to true and obtain a strongly consistent result. Global secondary indexes support eventually consistent reads only, so do not specify ConsistentRead when querying a global secondary index.
195 */
196 query(params: DynamoDB.Types.QueryInput, callback?: (err: AWSError, data: DynamoDB.Types.QueryOutput) => void): Request<DynamoDB.Types.QueryOutput, AWSError>;
197 /**
198 * The Query operation finds items based on primary key values. You can query any table or secondary index that has a composite primary key (a partition key and a sort key). Use the KeyConditionExpression parameter to provide a specific value for the partition key. The Query operation will return all of the items from the table or index with that partition key value. You can optionally narrow the scope of the Query operation by specifying a sort key value and a comparison operator in KeyConditionExpression. To further refine the Query results, you can optionally provide a FilterExpression. A FilterExpression determines which items within the results should be returned to you. All of the other results are discarded. A Query operation always returns a result set. If no matching items are found, the result set will be empty. Queries that do not return results consume the minimum number of read capacity units for that type of read operation. DynamoDB calculates the number of read capacity units consumed based on item size, not on the amount of data that is returned to an application. The number of capacity units consumed will be the same whether you request all of the attributes (the default behavior) or just some of them (using a projection expression). The number will also be the same whether or not you use a FilterExpression. Query results are always sorted by the sort key value. If the data type of the sort key is Number, the results are returned in numeric order; otherwise, the results are returned in order of UTF-8 bytes. By default, the sort order is ascending. To reverse the order, set the ScanIndexForward parameter to false. A single Query operation will read up to the maximum number of items set (if using the Limit parameter) or a maximum of 1 MB of data and then apply any filtering to the results using FilterExpression. If LastEvaluatedKey is present in the response, you will need to paginate the result set. For more information, see Paginating the Results in the Amazon DynamoDB Developer Guide. FilterExpression is applied after a Query finishes, but before the results are returned. A FilterExpression cannot contain partition key or sort key attributes. You need to specify those attributes in the KeyConditionExpression. A Query operation can return an empty result set and a LastEvaluatedKey if all the items read for the page of results are filtered out. You can query a table, a local secondary index, or a global secondary index. For a query on a table or on a local secondary index, you can set the ConsistentRead parameter to true and obtain a strongly consistent result. Global secondary indexes support eventually consistent reads only, so do not specify ConsistentRead when querying a global secondary index.
199 */
200 query(callback?: (err: AWSError, data: DynamoDB.Types.QueryOutput) => void): Request<DynamoDB.Types.QueryOutput, AWSError>;
201 /**
202 * Creates a new table from an existing backup. Any number of users can execute up to 4 concurrent restores (any type of restore) in a given account. You can call RestoreTableFromBackup at a maximum rate of 10 times per second. You must manually set up the following on the restored table: Auto scaling policies IAM policies Amazon CloudWatch metrics and alarms Tags Stream settings Time to Live (TTL) settings
203 */
204 restoreTableFromBackup(params: DynamoDB.Types.RestoreTableFromBackupInput, callback?: (err: AWSError, data: DynamoDB.Types.RestoreTableFromBackupOutput) => void): Request<DynamoDB.Types.RestoreTableFromBackupOutput, AWSError>;
205 /**
206 * Creates a new table from an existing backup. Any number of users can execute up to 4 concurrent restores (any type of restore) in a given account. You can call RestoreTableFromBackup at a maximum rate of 10 times per second. You must manually set up the following on the restored table: Auto scaling policies IAM policies Amazon CloudWatch metrics and alarms Tags Stream settings Time to Live (TTL) settings
207 */
208 restoreTableFromBackup(callback?: (err: AWSError, data: DynamoDB.Types.RestoreTableFromBackupOutput) => void): Request<DynamoDB.Types.RestoreTableFromBackupOutput, AWSError>;
209 /**
210 * Restores the specified table to the specified point in time within EarliestRestorableDateTime and LatestRestorableDateTime. You can restore your table to any point in time during the last 35 days. Any number of users can execute up to 4 concurrent restores (any type of restore) in a given account. When you restore using point in time recovery, DynamoDB restores your table data to the state based on the selected date and time (day:hour:minute:second) to a new table. Along with data, the following are also included on the new restored table using point in time recovery: Global secondary indexes (GSIs) Local secondary indexes (LSIs) Provisioned read and write capacity Encryption settings All these settings come from the current settings of the source table at the time of restore. You must manually set up the following on the restored table: Auto scaling policies IAM policies Amazon CloudWatch metrics and alarms Tags Stream settings Time to Live (TTL) settings Point in time recovery settings
211 */
212 restoreTableToPointInTime(params: DynamoDB.Types.RestoreTableToPointInTimeInput, callback?: (err: AWSError, data: DynamoDB.Types.RestoreTableToPointInTimeOutput) => void): Request<DynamoDB.Types.RestoreTableToPointInTimeOutput, AWSError>;
213 /**
214 * Restores the specified table to the specified point in time within EarliestRestorableDateTime and LatestRestorableDateTime. You can restore your table to any point in time during the last 35 days. Any number of users can execute up to 4 concurrent restores (any type of restore) in a given account. When you restore using point in time recovery, DynamoDB restores your table data to the state based on the selected date and time (day:hour:minute:second) to a new table. Along with data, the following are also included on the new restored table using point in time recovery: Global secondary indexes (GSIs) Local secondary indexes (LSIs) Provisioned read and write capacity Encryption settings All these settings come from the current settings of the source table at the time of restore. You must manually set up the following on the restored table: Auto scaling policies IAM policies Amazon CloudWatch metrics and alarms Tags Stream settings Time to Live (TTL) settings Point in time recovery settings
215 */
216 restoreTableToPointInTime(callback?: (err: AWSError, data: DynamoDB.Types.RestoreTableToPointInTimeOutput) => void): Request<DynamoDB.Types.RestoreTableToPointInTimeOutput, AWSError>;
217 /**
218 * The Scan operation returns one or more items and item attributes by accessing every item in a table or a secondary index. To have DynamoDB return fewer items, you can provide a FilterExpression operation. If the total number of scanned items exceeds the maximum dataset size limit of 1 MB, the scan stops and results are returned to the user as a LastEvaluatedKey value to continue the scan in a subsequent operation. The results also include the number of items exceeding the limit. A scan can result in no table data meeting the filter criteria. A single Scan operation reads up to the maximum number of items set (if using the Limit parameter) or a maximum of 1 MB of data and then apply any filtering to the results using FilterExpression. If LastEvaluatedKey is present in the response, you need to paginate the result set. For more information, see Paginating the Results in the Amazon DynamoDB Developer Guide. Scan operations proceed sequentially; however, for faster performance on a large table or secondary index, applications can request a parallel Scan operation by providing the Segment and TotalSegments parameters. For more information, see Parallel Scan in the Amazon DynamoDB Developer Guide. Scan uses eventually consistent reads when accessing the data in a table; therefore, the result set might not include the changes to data in the table immediately before the operation began. If you need a consistent copy of the data, as of the time that the Scan begins, you can set the ConsistentRead parameter to true.
219 */
220 scan(params: DynamoDB.Types.ScanInput, callback?: (err: AWSError, data: DynamoDB.Types.ScanOutput) => void): Request<DynamoDB.Types.ScanOutput, AWSError>;
221 /**
222 * The Scan operation returns one or more items and item attributes by accessing every item in a table or a secondary index. To have DynamoDB return fewer items, you can provide a FilterExpression operation. If the total number of scanned items exceeds the maximum dataset size limit of 1 MB, the scan stops and results are returned to the user as a LastEvaluatedKey value to continue the scan in a subsequent operation. The results also include the number of items exceeding the limit. A scan can result in no table data meeting the filter criteria. A single Scan operation reads up to the maximum number of items set (if using the Limit parameter) or a maximum of 1 MB of data and then apply any filtering to the results using FilterExpression. If LastEvaluatedKey is present in the response, you need to paginate the result set. For more information, see Paginating the Results in the Amazon DynamoDB Developer Guide. Scan operations proceed sequentially; however, for faster performance on a large table or secondary index, applications can request a parallel Scan operation by providing the Segment and TotalSegments parameters. For more information, see Parallel Scan in the Amazon DynamoDB Developer Guide. Scan uses eventually consistent reads when accessing the data in a table; therefore, the result set might not include the changes to data in the table immediately before the operation began. If you need a consistent copy of the data, as of the time that the Scan begins, you can set the ConsistentRead parameter to true.
223 */
224 scan(callback?: (err: AWSError, data: DynamoDB.Types.ScanOutput) => void): Request<DynamoDB.Types.ScanOutput, AWSError>;
225 /**
226 * Associate a set of tags with an Amazon DynamoDB resource. You can then activate these user-defined tags so that they appear on the Billing and Cost Management console for cost allocation tracking. You can call TagResource up to five times per second, per account. For an overview on tagging DynamoDB resources, see Tagging for DynamoDB in the Amazon DynamoDB Developer Guide.
227 */
228 tagResource(params: DynamoDB.Types.TagResourceInput, callback?: (err: AWSError, data: {}) => void): Request<{}, AWSError>;
229 /**
230 * Associate a set of tags with an Amazon DynamoDB resource. You can then activate these user-defined tags so that they appear on the Billing and Cost Management console for cost allocation tracking. You can call TagResource up to five times per second, per account. For an overview on tagging DynamoDB resources, see Tagging for DynamoDB in the Amazon DynamoDB Developer Guide.
231 */
232 tagResource(callback?: (err: AWSError, data: {}) => void): Request<{}, AWSError>;
233 /**
234 * TransactGetItems is a synchronous operation that atomically retrieves multiple items from one or more tables (but not from indexes) in a single account and Region. A TransactGetItems call can contain up to 25 TransactGetItem objects, each of which contains a Get structure that specifies an item to retrieve from a table in the account and Region. A call to TransactGetItems cannot retrieve items from tables in more than one AWS account or Region. The aggregate size of the items in the transaction cannot exceed 4 MB. All AWS Regions and AWS GovCloud (US) support up to 25 items per transaction with up to 4 MB of data, except the following AWS Regions: China (Beijing) China (Ningxia) The China (Beijing) and China (Ningxia) Regions support up to 10 items per transaction with up to 4 MB of data. DynamoDB rejects the entire TransactGetItems request if any of the following is true: A conflicting operation is in the process of updating an item to be read. There is insufficient provisioned capacity for the transaction to be completed. There is a user error, such as an invalid data format. The aggregate size of the items in the transaction cannot exceed 4 MB.
235 */
236 transactGetItems(params: DynamoDB.Types.TransactGetItemsInput, callback?: (err: AWSError, data: DynamoDB.Types.TransactGetItemsOutput) => void): Request<DynamoDB.Types.TransactGetItemsOutput, AWSError>;
237 /**
238 * TransactGetItems is a synchronous operation that atomically retrieves multiple items from one or more tables (but not from indexes) in a single account and Region. A TransactGetItems call can contain up to 25 TransactGetItem objects, each of which contains a Get structure that specifies an item to retrieve from a table in the account and Region. A call to TransactGetItems cannot retrieve items from tables in more than one AWS account or Region. The aggregate size of the items in the transaction cannot exceed 4 MB. All AWS Regions and AWS GovCloud (US) support up to 25 items per transaction with up to 4 MB of data, except the following AWS Regions: China (Beijing) China (Ningxia) The China (Beijing) and China (Ningxia) Regions support up to 10 items per transaction with up to 4 MB of data. DynamoDB rejects the entire TransactGetItems request if any of the following is true: A conflicting operation is in the process of updating an item to be read. There is insufficient provisioned capacity for the transaction to be completed. There is a user error, such as an invalid data format. The aggregate size of the items in the transaction cannot exceed 4 MB.
239 */
240 transactGetItems(callback?: (err: AWSError, data: DynamoDB.Types.TransactGetItemsOutput) => void): Request<DynamoDB.Types.TransactGetItemsOutput, AWSError>;
241 /**
242 * TransactWriteItems is a synchronous write operation that groups up to 25 action requests. These actions can target items in different tables, but not in different AWS accounts or Regions, and no two actions can target the same item. For example, you cannot both ConditionCheck and Update the same item. The aggregate size of the items in the transaction cannot exceed 4 MB. All AWS Regions and AWS GovCloud (US) support up to 25 items per transaction with up to 4 MB of data, except the following AWS Regions: China (Beijing) China (Ningxia) The China (Beijing) and China (Ningxia) Regions support up to 10 items per transaction with up to 4 MB of data. The actions are completed atomically so that either all of them succeed, or all of them fail. They are defined by the following objects: Put  &#x97;   Initiates a PutItem operation to write a new item. This structure specifies the primary key of the item to be written, the name of the table to write it in, an optional condition expression that must be satisfied for the write to succeed, a list of the item's attributes, and a field indicating whether to retrieve the item's attributes if the condition is not met. Update  &#x97;   Initiates an UpdateItem operation to update an existing item. This structure specifies the primary key of the item to be updated, the name of the table where it resides, an optional condition expression that must be satisfied for the update to succeed, an expression that defines one or more attributes to be updated, and a field indicating whether to retrieve the item's attributes if the condition is not met. Delete  &#x97;   Initiates a DeleteItem operation to delete an existing item. This structure specifies the primary key of the item to be deleted, the name of the table where it resides, an optional condition expression that must be satisfied for the deletion to succeed, and a field indicating whether to retrieve the item's attributes if the condition is not met. ConditionCheck  &#x97;   Applies a condition to an item that is not being modified by the transaction. This structure specifies the primary key of the item to be checked, the name of the table where it resides, a condition expression that must be satisfied for the transaction to succeed, and a field indicating whether to retrieve the item's attributes if the condition is not met. DynamoDB rejects the entire TransactWriteItems request if any of the following is true: A condition in one of the condition expressions is not met. An ongoing operation is in the process of updating the same item. There is insufficient provisioned capacity for the transaction to be completed. An item size becomes too large (bigger than 400 KB), a local secondary index (LSI) becomes too large, or a similar validation error occurs because of changes made by the transaction. The aggregate size of the items in the transaction exceeds 4 MB. There is a user error, such as an invalid data format.
243 */
244 transactWriteItems(params: DynamoDB.Types.TransactWriteItemsInput, callback?: (err: AWSError, data: DynamoDB.Types.TransactWriteItemsOutput) => void): Request<DynamoDB.Types.TransactWriteItemsOutput, AWSError>;
245 /**
246 * TransactWriteItems is a synchronous write operation that groups up to 25 action requests. These actions can target items in different tables, but not in different AWS accounts or Regions, and no two actions can target the same item. For example, you cannot both ConditionCheck and Update the same item. The aggregate size of the items in the transaction cannot exceed 4 MB. All AWS Regions and AWS GovCloud (US) support up to 25 items per transaction with up to 4 MB of data, except the following AWS Regions: China (Beijing) China (Ningxia) The China (Beijing) and China (Ningxia) Regions support up to 10 items per transaction with up to 4 MB of data. The actions are completed atomically so that either all of them succeed, or all of them fail. They are defined by the following objects: Put  &#x97;   Initiates a PutItem operation to write a new item. This structure specifies the primary key of the item to be written, the name of the table to write it in, an optional condition expression that must be satisfied for the write to succeed, a list of the item's attributes, and a field indicating whether to retrieve the item's attributes if the condition is not met. Update  &#x97;   Initiates an UpdateItem operation to update an existing item. This structure specifies the primary key of the item to be updated, the name of the table where it resides, an optional condition expression that must be satisfied for the update to succeed, an expression that defines one or more attributes to be updated, and a field indicating whether to retrieve the item's attributes if the condition is not met. Delete  &#x97;   Initiates a DeleteItem operation to delete an existing item. This structure specifies the primary key of the item to be deleted, the name of the table where it resides, an optional condition expression that must be satisfied for the deletion to succeed, and a field indicating whether to retrieve the item's attributes if the condition is not met. ConditionCheck  &#x97;   Applies a condition to an item that is not being modified by the transaction. This structure specifies the primary key of the item to be checked, the name of the table where it resides, a condition expression that must be satisfied for the transaction to succeed, and a field indicating whether to retrieve the item's attributes if the condition is not met. DynamoDB rejects the entire TransactWriteItems request if any of the following is true: A condition in one of the condition expressions is not met. An ongoing operation is in the process of updating the same item. There is insufficient provisioned capacity for the transaction to be completed. An item size becomes too large (bigger than 400 KB), a local secondary index (LSI) becomes too large, or a similar validation error occurs because of changes made by the transaction. The aggregate size of the items in the transaction exceeds 4 MB. There is a user error, such as an invalid data format.
247 */
248 transactWriteItems(callback?: (err: AWSError, data: DynamoDB.Types.TransactWriteItemsOutput) => void): Request<DynamoDB.Types.TransactWriteItemsOutput, AWSError>;
249 /**
250 * Removes the association of tags from an Amazon DynamoDB resource. You can call UntagResource up to five times per second, per account. For an overview on tagging DynamoDB resources, see Tagging for DynamoDB in the Amazon DynamoDB Developer Guide.
251 */
252 untagResource(params: DynamoDB.Types.UntagResourceInput, callback?: (err: AWSError, data: {}) => void): Request<{}, AWSError>;
253 /**
254 * Removes the association of tags from an Amazon DynamoDB resource. You can call UntagResource up to five times per second, per account. For an overview on tagging DynamoDB resources, see Tagging for DynamoDB in the Amazon DynamoDB Developer Guide.
255 */
256 untagResource(callback?: (err: AWSError, data: {}) => void): Request<{}, AWSError>;
257 /**
258 * UpdateContinuousBackups enables or disables point in time recovery for the specified table. A successful UpdateContinuousBackups call returns the current ContinuousBackupsDescription. Continuous backups are ENABLED on all tables at table creation. If point in time recovery is enabled, PointInTimeRecoveryStatus will be set to ENABLED. Once continuous backups and point in time recovery are enabled, you can restore to any point in time within EarliestRestorableDateTime and LatestRestorableDateTime. LatestRestorableDateTime is typically 5 minutes before the current time. You can restore your table to any point in time during the last 35 days.
259 */
260 updateContinuousBackups(params: DynamoDB.Types.UpdateContinuousBackupsInput, callback?: (err: AWSError, data: DynamoDB.Types.UpdateContinuousBackupsOutput) => void): Request<DynamoDB.Types.UpdateContinuousBackupsOutput, AWSError>;
261 /**
262 * UpdateContinuousBackups enables or disables point in time recovery for the specified table. A successful UpdateContinuousBackups call returns the current ContinuousBackupsDescription. Continuous backups are ENABLED on all tables at table creation. If point in time recovery is enabled, PointInTimeRecoveryStatus will be set to ENABLED. Once continuous backups and point in time recovery are enabled, you can restore to any point in time within EarliestRestorableDateTime and LatestRestorableDateTime. LatestRestorableDateTime is typically 5 minutes before the current time. You can restore your table to any point in time during the last 35 days.
263 */
264 updateContinuousBackups(callback?: (err: AWSError, data: DynamoDB.Types.UpdateContinuousBackupsOutput) => void): Request<DynamoDB.Types.UpdateContinuousBackupsOutput, AWSError>;
265 /**
266 * Adds or removes replicas in the specified global table. The global table must already exist to be able to use this operation. Any replica to be added must be empty, have the same name as the global table, have the same key schema, have DynamoDB Streams enabled, and have the same provisioned and maximum write capacity units. Although you can use UpdateGlobalTable to add replicas and remove replicas in a single request, for simplicity we recommend that you issue separate requests for adding or removing replicas. If global secondary indexes are specified, then the following conditions must also be met: The global secondary indexes must have the same name. The global secondary indexes must have the same hash key and sort key (if present). The global secondary indexes must have the same provisioned and maximum write capacity units.
267 */
268 updateGlobalTable(params: DynamoDB.Types.UpdateGlobalTableInput, callback?: (err: AWSError, data: DynamoDB.Types.UpdateGlobalTableOutput) => void): Request<DynamoDB.Types.UpdateGlobalTableOutput, AWSError>;
269 /**
270 * Adds or removes replicas in the specified global table. The global table must already exist to be able to use this operation. Any replica to be added must be empty, have the same name as the global table, have the same key schema, have DynamoDB Streams enabled, and have the same provisioned and maximum write capacity units. Although you can use UpdateGlobalTable to add replicas and remove replicas in a single request, for simplicity we recommend that you issue separate requests for adding or removing replicas. If global secondary indexes are specified, then the following conditions must also be met: The global secondary indexes must have the same name. The global secondary indexes must have the same hash key and sort key (if present). The global secondary indexes must have the same provisioned and maximum write capacity units.
271 */
272 updateGlobalTable(callback?: (err: AWSError, data: DynamoDB.Types.UpdateGlobalTableOutput) => void): Request<DynamoDB.Types.UpdateGlobalTableOutput, AWSError>;
273 /**
274 * Updates settings for a global table.
275 */
276 updateGlobalTableSettings(params: DynamoDB.Types.UpdateGlobalTableSettingsInput, callback?: (err: AWSError, data: DynamoDB.Types.UpdateGlobalTableSettingsOutput) => void): Request<DynamoDB.Types.UpdateGlobalTableSettingsOutput, AWSError>;
277 /**
278 * Updates settings for a global table.
279 */
280 updateGlobalTableSettings(callback?: (err: AWSError, data: DynamoDB.Types.UpdateGlobalTableSettingsOutput) => void): Request<DynamoDB.Types.UpdateGlobalTableSettingsOutput, AWSError>;
281 /**
282 * Edits an existing item's attributes, or adds a new item to the table if it does not already exist. You can put, delete, or add attribute values. You can also perform a conditional update on an existing item (insert a new attribute name-value pair if it doesn't exist, or replace an existing name-value pair if it has certain expected attribute values). You can also return the item's attribute values in the same UpdateItem operation using the ReturnValues parameter.
283 */
284 updateItem(params: DynamoDB.Types.UpdateItemInput, callback?: (err: AWSError, data: DynamoDB.Types.UpdateItemOutput) => void): Request<DynamoDB.Types.UpdateItemOutput, AWSError>;
285 /**
286 * Edits an existing item's attributes, or adds a new item to the table if it does not already exist. You can put, delete, or add attribute values. You can also perform a conditional update on an existing item (insert a new attribute name-value pair if it doesn't exist, or replace an existing name-value pair if it has certain expected attribute values). You can also return the item's attribute values in the same UpdateItem operation using the ReturnValues parameter.
287 */
288 updateItem(callback?: (err: AWSError, data: DynamoDB.Types.UpdateItemOutput) => void): Request<DynamoDB.Types.UpdateItemOutput, AWSError>;
289 /**
290 * Modifies the provisioned throughput settings, global secondary indexes, or DynamoDB Streams settings for a given table. You can only perform one of the following operations at once: Modify the provisioned throughput settings of the table. Enable or disable DynamoDB Streams on the table. Remove a global secondary index from the table. Create a new global secondary index on the table. After the index begins backfilling, you can use UpdateTable to perform other operations. UpdateTable is an asynchronous operation; while it is executing, the table status changes from ACTIVE to UPDATING. While it is UPDATING, you cannot issue another UpdateTable request. When the table returns to the ACTIVE state, the UpdateTable operation is complete.
291 */
292 updateTable(params: DynamoDB.Types.UpdateTableInput, callback?: (err: AWSError, data: DynamoDB.Types.UpdateTableOutput) => void): Request<DynamoDB.Types.UpdateTableOutput, AWSError>;
293 /**
294 * Modifies the provisioned throughput settings, global secondary indexes, or DynamoDB Streams settings for a given table. You can only perform one of the following operations at once: Modify the provisioned throughput settings of the table. Enable or disable DynamoDB Streams on the table. Remove a global secondary index from the table. Create a new global secondary index on the table. After the index begins backfilling, you can use UpdateTable to perform other operations. UpdateTable is an asynchronous operation; while it is executing, the table status changes from ACTIVE to UPDATING. While it is UPDATING, you cannot issue another UpdateTable request. When the table returns to the ACTIVE state, the UpdateTable operation is complete.
295 */
296 updateTable(callback?: (err: AWSError, data: DynamoDB.Types.UpdateTableOutput) => void): Request<DynamoDB.Types.UpdateTableOutput, AWSError>;
297 /**
298 * The UpdateTimeToLive method enables or disables Time to Live (TTL) for the specified table. A successful UpdateTimeToLive call returns the current TimeToLiveSpecification. It can take up to one hour for the change to fully process. Any additional UpdateTimeToLive calls for the same table during this one hour duration result in a ValidationException. TTL compares the current time in epoch time format to the time stored in the TTL attribute of an item. If the epoch time value stored in the attribute is less than the current time, the item is marked as expired and subsequently deleted. The epoch time format is the number of seconds elapsed since 12:00:00 AM January 1, 1970 UTC. DynamoDB deletes expired items on a best-effort basis to ensure availability of throughput for other data operations. DynamoDB typically deletes expired items within two days of expiration. The exact duration within which an item gets deleted after expiration is specific to the nature of the workload. Items that have expired and not been deleted will still show up in reads, queries, and scans. As items are deleted, they are removed from any local secondary index and global secondary index immediately in the same eventually consistent way as a standard delete operation. For more information, see Time To Live in the Amazon DynamoDB Developer Guide.
299 */
300 updateTimeToLive(params: DynamoDB.Types.UpdateTimeToLiveInput, callback?: (err: AWSError, data: DynamoDB.Types.UpdateTimeToLiveOutput) => void): Request<DynamoDB.Types.UpdateTimeToLiveOutput, AWSError>;
301 /**
302 * The UpdateTimeToLive method enables or disables Time to Live (TTL) for the specified table. A successful UpdateTimeToLive call returns the current TimeToLiveSpecification. It can take up to one hour for the change to fully process. Any additional UpdateTimeToLive calls for the same table during this one hour duration result in a ValidationException. TTL compares the current time in epoch time format to the time stored in the TTL attribute of an item. If the epoch time value stored in the attribute is less than the current time, the item is marked as expired and subsequently deleted. The epoch time format is the number of seconds elapsed since 12:00:00 AM January 1, 1970 UTC. DynamoDB deletes expired items on a best-effort basis to ensure availability of throughput for other data operations. DynamoDB typically deletes expired items within two days of expiration. The exact duration within which an item gets deleted after expiration is specific to the nature of the workload. Items that have expired and not been deleted will still show up in reads, queries, and scans. As items are deleted, they are removed from any local secondary index and global secondary index immediately in the same eventually consistent way as a standard delete operation. For more information, see Time To Live in the Amazon DynamoDB Developer Guide.
303 */
304 updateTimeToLive(callback?: (err: AWSError, data: DynamoDB.Types.UpdateTimeToLiveOutput) => void): Request<DynamoDB.Types.UpdateTimeToLiveOutput, AWSError>;
305 /**
306 * Waits for the tableExists state by periodically calling the underlying DynamoDB.describeTableoperation every 20 seconds (at most 25 times).
307 */
308 waitFor(state: "tableExists", params: DynamoDB.Types.DescribeTableInput & {$waiter?: WaiterConfiguration}, callback?: (err: AWSError, data: DynamoDB.Types.DescribeTableOutput) => void): Request<DynamoDB.Types.DescribeTableOutput, AWSError>;
309 /**
310 * Waits for the tableExists state by periodically calling the underlying DynamoDB.describeTableoperation every 20 seconds (at most 25 times).
311 */
312 waitFor(state: "tableExists", callback?: (err: AWSError, data: DynamoDB.Types.DescribeTableOutput) => void): Request<DynamoDB.Types.DescribeTableOutput, AWSError>;
313 /**
314 * Waits for the tableNotExists state by periodically calling the underlying DynamoDB.describeTableoperation every 20 seconds (at most 25 times).
315 */
316 waitFor(state: "tableNotExists", params: DynamoDB.Types.DescribeTableInput & {$waiter?: WaiterConfiguration}, callback?: (err: AWSError, data: DynamoDB.Types.DescribeTableOutput) => void): Request<DynamoDB.Types.DescribeTableOutput, AWSError>;
317 /**
318 * Waits for the tableNotExists state by periodically calling the underlying DynamoDB.describeTableoperation every 20 seconds (at most 25 times).
319 */
320 waitFor(state: "tableNotExists", callback?: (err: AWSError, data: DynamoDB.Types.DescribeTableOutput) => void): Request<DynamoDB.Types.DescribeTableOutput, AWSError>;
321}
322declare namespace DynamoDB {
323 export import DocumentClient = document_client;
324 export import Converter = converter;
325}
326declare namespace DynamoDB {
327 export type AttributeAction = "ADD"|"PUT"|"DELETE"|string;
328 export interface AttributeDefinition {
329 /**
330 * A name for the attribute.
331 */
332 AttributeName: KeySchemaAttributeName;
333 /**
334 * The data type for the attribute, where: S - the attribute is of type String N - the attribute is of type Number B - the attribute is of type Binary
335 */
336 AttributeType: ScalarAttributeType;
337 }
338 export type AttributeDefinitions = AttributeDefinition[];
339 export type AttributeMap = {[key: string]: AttributeValue};
340 export type AttributeName = string;
341 export type AttributeNameList = AttributeName[];
342 export type AttributeUpdates = {[key: string]: AttributeValueUpdate};
343 export interface AttributeValue {
344 /**
345 * An attribute of type String. For example: "S": "Hello"
346 */
347 S?: StringAttributeValue;
348 /**
349 * An attribute of type Number. For example: "N": "123.45" Numbers are sent across the network to DynamoDB as strings, to maximize compatibility across languages and libraries. However, DynamoDB treats them as number type attributes for mathematical operations.
350 */
351 N?: NumberAttributeValue;
352 /**
353 * An attribute of type Binary. For example: "B": "dGhpcyB0ZXh0IGlzIGJhc2U2NC1lbmNvZGVk"
354 */
355 B?: BinaryAttributeValue;
356 /**
357 * An attribute of type String Set. For example: "SS": ["Giraffe", "Hippo" ,"Zebra"]
358 */
359 SS?: StringSetAttributeValue;
360 /**
361 * An attribute of type Number Set. For example: "NS": ["42.2", "-19", "7.5", "3.14"] Numbers are sent across the network to DynamoDB as strings, to maximize compatibility across languages and libraries. However, DynamoDB treats them as number type attributes for mathematical operations.
362 */
363 NS?: NumberSetAttributeValue;
364 /**
365 * An attribute of type Binary Set. For example: "BS": ["U3Vubnk=", "UmFpbnk=", "U25vd3k="]
366 */
367 BS?: BinarySetAttributeValue;
368 /**
369 * An attribute of type Map. For example: "M": {"Name": {"S": "Joe"}, "Age": {"N": "35"}}
370 */
371 M?: MapAttributeValue;
372 /**
373 * An attribute of type List. For example: "L": [ {"S": "Cookies"} , {"S": "Coffee"}, {"N", "3.14159"}]
374 */
375 L?: ListAttributeValue;
376 /**
377 * An attribute of type Null. For example: "NULL": true
378 */
379 NULL?: NullAttributeValue;
380 /**
381 * An attribute of type Boolean. For example: "BOOL": true
382 */
383 BOOL?: BooleanAttributeValue;
384 }
385 export type AttributeValueList = AttributeValue[];
386 export interface AttributeValueUpdate {
387 /**
388 * Represents the data for an attribute. Each attribute value is described as a name-value pair. The name is the data type, and the value is the data itself. For more information, see Data Types in the Amazon DynamoDB Developer Guide.
389 */
390 Value?: AttributeValue;
391 /**
392 * Specifies how to perform the update. Valid values are PUT (default), DELETE, and ADD. The behavior depends on whether the specified primary key already exists in the table. If an item with the specified Key is found in the table: PUT - Adds the specified attribute to the item. If the attribute already exists, it is replaced by the new value. DELETE - If no value is specified, the attribute and its value are removed from the item. The data type of the specified value must match the existing value's data type. If a set of values is specified, then those values are subtracted from the old set. For example, if the attribute value was the set [a,b,c] and the DELETE action specified [a,c], then the final attribute value would be [b]. Specifying an empty set is an error. ADD - If the attribute does not already exist, then the attribute and its values are added to the item. If the attribute does exist, then the behavior of ADD depends on the data type of the attribute: If the existing attribute is a number, and if Value is also a number, then the Value is mathematically added to the existing attribute. If Value is a negative number, then it is subtracted from the existing attribute. If you use ADD to increment or decrement a number value for an item that doesn't exist before the update, DynamoDB uses 0 as the initial value. In addition, if you use ADD to update an existing item, and intend to increment or decrement an attribute value which does not yet exist, DynamoDB uses 0 as the initial value. For example, suppose that the item you want to update does not yet have an attribute named itemcount, but you decide to ADD the number 3 to this attribute anyway, even though it currently does not exist. DynamoDB will create the itemcount attribute, set its initial value to 0, and finally add 3 to it. The result will be a new itemcount attribute in the item, with a value of 3. If the existing data type is a set, and if the Value is also a set, then the Value is added to the existing set. (This is a set operation, not mathematical addition.) For example, if the attribute value was the set [1,2], and the ADD action specified [3], then the final attribute value would be [1,2,3]. An error occurs if an Add action is specified for a set attribute and the attribute type specified does not match the existing set type. Both sets must have the same primitive data type. For example, if the existing data type is a set of strings, the Value must also be a set of strings. The same holds true for number sets and binary sets. This action is only valid for an existing attribute whose data type is number or is a set. Do not use ADD for any other data types. If no item with the specified Key is found: PUT - DynamoDB creates a new item with the specified primary key, and then adds the attribute. DELETE - Nothing happens; there is no attribute to delete. ADD - DynamoDB creates an item with the supplied primary key and number (or set of numbers) for the attribute value. The only data types allowed are number and number set; no other data types can be specified.
393 */
394 Action?: AttributeAction;
395 }
396 export interface AutoScalingPolicyDescription {
397 /**
398 * The name of the scaling policy.
399 */
400 PolicyName?: AutoScalingPolicyName;
401 /**
402 * Represents a target tracking scaling policy configuration.
403 */
404 TargetTrackingScalingPolicyConfiguration?: AutoScalingTargetTrackingScalingPolicyConfigurationDescription;
405 }
406 export type AutoScalingPolicyDescriptionList = AutoScalingPolicyDescription[];
407 export type AutoScalingPolicyName = string;
408 export interface AutoScalingPolicyUpdate {
409 /**
410 * The name of the scaling policy.
411 */
412 PolicyName?: AutoScalingPolicyName;
413 /**
414 * Represents a target tracking scaling policy configuration.
415 */
416 TargetTrackingScalingPolicyConfiguration: AutoScalingTargetTrackingScalingPolicyConfigurationUpdate;
417 }
418 export type AutoScalingRoleArn = string;
419 export interface AutoScalingSettingsDescription {
420 /**
421 * The minimum capacity units that a global table or global secondary index should be scaled down to.
422 */
423 MinimumUnits?: PositiveLongObject;
424 /**
425 * The maximum capacity units that a global table or global secondary index should be scaled up to.
426 */
427 MaximumUnits?: PositiveLongObject;
428 /**
429 * Disabled autoscaling for this global table or global secondary index.
430 */
431 AutoScalingDisabled?: BooleanObject;
432 /**
433 * Role ARN used for configuring autoScaling policy.
434 */
435 AutoScalingRoleArn?: String;
436 /**
437 * Information about the scaling policies.
438 */
439 ScalingPolicies?: AutoScalingPolicyDescriptionList;
440 }
441 export interface AutoScalingSettingsUpdate {
442 /**
443 * The minimum capacity units that a global table or global secondary index should be scaled down to.
444 */
445 MinimumUnits?: PositiveLongObject;
446 /**
447 * The maximum capacity units that a global table or global secondary index should be scaled up to.
448 */
449 MaximumUnits?: PositiveLongObject;
450 /**
451 * Disabled autoscaling for this global table or global secondary index.
452 */
453 AutoScalingDisabled?: BooleanObject;
454 /**
455 * Role ARN used for configuring autoscaling policy.
456 */
457 AutoScalingRoleArn?: AutoScalingRoleArn;
458 /**
459 * The scaling policy to apply for scaling target global table or global secondary index capacity units.
460 */
461 ScalingPolicyUpdate?: AutoScalingPolicyUpdate;
462 }
463 export interface AutoScalingTargetTrackingScalingPolicyConfigurationDescription {
464 /**
465 * Indicates whether scale in by the target tracking policy is disabled. If the value is true, scale in is disabled and the target tracking policy won't remove capacity from the scalable resource. Otherwise, scale in is enabled and the target tracking policy can remove capacity from the scalable resource. The default value is false.
466 */
467 DisableScaleIn?: BooleanObject;
468 /**
469 * The amount of time, in seconds, after a scale in activity completes before another scale in activity can start. The cooldown period is used to block subsequent scale in requests until it has expired. You should scale in conservatively to protect your application's availability. However, if another alarm triggers a scale out policy during the cooldown period after a scale-in, application autoscaling scales out your scalable target immediately.
470 */
471 ScaleInCooldown?: IntegerObject;
472 /**
473 * The amount of time, in seconds, after a scale out activity completes before another scale out activity can start. While the cooldown period is in effect, the capacity that has been added by the previous scale out event that initiated the cooldown is calculated as part of the desired capacity for the next scale out. You should continuously (but not excessively) scale out.
474 */
475 ScaleOutCooldown?: IntegerObject;
476 /**
477 * The target value for the metric. The range is 8.515920e-109 to 1.174271e+108 (Base 10) or 2e-360 to 2e360 (Base 2).
478 */
479 TargetValue: Double;
480 }
481 export interface AutoScalingTargetTrackingScalingPolicyConfigurationUpdate {
482 /**
483 * Indicates whether scale in by the target tracking policy is disabled. If the value is true, scale in is disabled and the target tracking policy won't remove capacity from the scalable resource. Otherwise, scale in is enabled and the target tracking policy can remove capacity from the scalable resource. The default value is false.
484 */
485 DisableScaleIn?: BooleanObject;
486 /**
487 * The amount of time, in seconds, after a scale in activity completes before another scale in activity can start. The cooldown period is used to block subsequent scale in requests until it has expired. You should scale in conservatively to protect your application's availability. However, if another alarm triggers a scale out policy during the cooldown period after a scale-in, application autoscaling scales out your scalable target immediately.
488 */
489 ScaleInCooldown?: IntegerObject;
490 /**
491 * The amount of time, in seconds, after a scale out activity completes before another scale out activity can start. While the cooldown period is in effect, the capacity that has been added by the previous scale out event that initiated the cooldown is calculated as part of the desired capacity for the next scale out. You should continuously (but not excessively) scale out.
492 */
493 ScaleOutCooldown?: IntegerObject;
494 /**
495 * The target value for the metric. The range is 8.515920e-109 to 1.174271e+108 (Base 10) or 2e-360 to 2e360 (Base 2).
496 */
497 TargetValue: Double;
498 }
499 export type Backfilling = boolean;
500 export type BackupArn = string;
501 export type BackupCreationDateTime = Date;
502 export interface BackupDescription {
503 /**
504 * Contains the details of the backup created for the table.
505 */
506 BackupDetails?: BackupDetails;
507 /**
508 * Contains the details of the table when the backup was created.
509 */
510 SourceTableDetails?: SourceTableDetails;
511 /**
512 * Contains the details of the features enabled on the table when the backup was created. For example, LSIs, GSIs, streams, TTL.
513 */
514 SourceTableFeatureDetails?: SourceTableFeatureDetails;
515 }
516 export interface BackupDetails {
517 /**
518 * ARN associated with the backup.
519 */
520 BackupArn: BackupArn;
521 /**
522 * Name of the requested backup.
523 */
524 BackupName: BackupName;
525 /**
526 * Size of the backup in bytes.
527 */
528 BackupSizeBytes?: BackupSizeBytes;
529 /**
530 * Backup can be in one of the following states: CREATING, ACTIVE, DELETED.
531 */
532 BackupStatus: BackupStatus;
533 /**
534 * BackupType: USER - You create and manage these using the on-demand backup feature. SYSTEM - If you delete a table with point-in-time recovery enabled, a SYSTEM backup is automatically created and is retained for 35 days (at no additional cost). System backups allow you to restore the deleted table to the state it was in just before the point of deletion. AWS_BACKUP - On-demand backup created by you from AWS Backup service.
535 */
536 BackupType: BackupType;
537 /**
538 * Time at which the backup was created. This is the request time of the backup.
539 */
540 BackupCreationDateTime: BackupCreationDateTime;
541 /**
542 * Time at which the automatic on-demand backup created by DynamoDB will expire. This SYSTEM on-demand backup expires automatically 35 days after its creation.
543 */
544 BackupExpiryDateTime?: _Date;
545 }
546 export type BackupName = string;
547 export type BackupSizeBytes = number;
548 export type BackupStatus = "CREATING"|"DELETED"|"AVAILABLE"|string;
549 export type BackupSummaries = BackupSummary[];
550 export interface BackupSummary {
551 /**
552 * Name of the table.
553 */
554 TableName?: TableName;
555 /**
556 * Unique identifier for the table.
557 */
558 TableId?: TableId;
559 /**
560 * ARN associated with the table.
561 */
562 TableArn?: TableArn;
563 /**
564 * ARN associated with the backup.
565 */
566 BackupArn?: BackupArn;
567 /**
568 * Name of the specified backup.
569 */
570 BackupName?: BackupName;
571 /**
572 * Time at which the backup was created.
573 */
574 BackupCreationDateTime?: BackupCreationDateTime;
575 /**
576 * Time at which the automatic on-demand backup created by DynamoDB will expire. This SYSTEM on-demand backup expires automatically 35 days after its creation.
577 */
578 BackupExpiryDateTime?: _Date;
579 /**
580 * Backup can be in one of the following states: CREATING, ACTIVE, DELETED.
581 */
582 BackupStatus?: BackupStatus;
583 /**
584 * BackupType: USER - You create and manage these using the on-demand backup feature. SYSTEM - If you delete a table with point-in-time recovery enabled, a SYSTEM backup is automatically created and is retained for 35 days (at no additional cost). System backups allow you to restore the deleted table to the state it was in just before the point of deletion. AWS_BACKUP - On-demand backup created by you from AWS Backup service.
585 */
586 BackupType?: BackupType;
587 /**
588 * Size of the backup in bytes.
589 */
590 BackupSizeBytes?: BackupSizeBytes;
591 }
592 export type BackupType = "USER"|"SYSTEM"|"AWS_BACKUP"|string;
593 export type BackupTypeFilter = "USER"|"SYSTEM"|"AWS_BACKUP"|"ALL"|string;
594 export type BackupsInputLimit = number;
595 export interface BatchGetItemInput {
596 /**
597 * A map of one or more table names and, for each table, a map that describes one or more items to retrieve from that table. Each table name can be used only once per BatchGetItem request. Each element in the map of items to retrieve consists of the following: ConsistentRead - If true, a strongly consistent read is used; if false (the default), an eventually consistent read is used. ExpressionAttributeNames - One or more substitution tokens for attribute names in the ProjectionExpression parameter. The following are some use cases for using ExpressionAttributeNames: To access an attribute whose name conflicts with a DynamoDB reserved word. To create a placeholder for repeating occurrences of an attribute name in an expression. To prevent special characters in an attribute name from being misinterpreted in an expression. Use the # character in an expression to dereference an attribute name. For example, consider the following attribute name: Percentile The name of this attribute conflicts with a reserved word, so it cannot be used directly in an expression. (For the complete list of reserved words, see Reserved Words in the Amazon DynamoDB Developer Guide). To work around this, you could specify the following for ExpressionAttributeNames: {"#P":"Percentile"} You could then use this substitution in an expression, as in this example: #P = :val Tokens that begin with the : character are expression attribute values, which are placeholders for the actual value at runtime. For more information about expression attribute names, see Accessing Item Attributes in the Amazon DynamoDB Developer Guide. Keys - An array of primary key attribute values that define specific items in the table. For each primary key, you must provide all of the key attributes. For example, with a simple primary key, you only need to provide the partition key value. For a composite key, you must provide both the partition key value and the sort key value. ProjectionExpression - A string that identifies one or more attributes to retrieve from the table. These attributes can include scalars, sets, or elements of a JSON document. The attributes in the expression must be separated by commas. If no attribute names are specified, then all attributes are returned. If any of the requested attributes are not found, they do not appear in the result. For more information, see Accessing Item Attributes in the Amazon DynamoDB Developer Guide. AttributesToGet - This is a legacy parameter. Use ProjectionExpression instead. For more information, see AttributesToGet in the Amazon DynamoDB Developer Guide.
598 */
599 RequestItems: BatchGetRequestMap;
600 ReturnConsumedCapacity?: ReturnConsumedCapacity;
601 }
602 export interface BatchGetItemOutput {
603 /**
604 * A map of table name to a list of items. Each object in Responses consists of a table name, along with a map of attribute data consisting of the data type and attribute value.
605 */
606 Responses?: BatchGetResponseMap;
607 /**
608 * A map of tables and their respective keys that were not processed with the current response. The UnprocessedKeys value is in the same form as RequestItems, so the value can be provided directly to a subsequent BatchGetItem operation. For more information, see RequestItems in the Request Parameters section. Each element consists of: Keys - An array of primary key attribute values that define specific items in the table. ProjectionExpression - One or more attributes to be retrieved from the table or index. By default, all attributes are returned. If a requested attribute is not found, it does not appear in the result. ConsistentRead - The consistency of a read operation. If set to true, then a strongly consistent read is used; otherwise, an eventually consistent read is used. If there are no unprocessed keys remaining, the response contains an empty UnprocessedKeys map.
609 */
610 UnprocessedKeys?: BatchGetRequestMap;
611 /**
612 * The read capacity units consumed by the entire BatchGetItem operation. Each element consists of: TableName - The table that consumed the provisioned throughput. CapacityUnits - The total number of capacity units consumed.
613 */
614 ConsumedCapacity?: ConsumedCapacityMultiple;
615 }
616 export type BatchGetRequestMap = {[key: string]: KeysAndAttributes};
617 export type BatchGetResponseMap = {[key: string]: ItemList};
618 export interface BatchWriteItemInput {
619 /**
620 * A map of one or more table names and, for each table, a list of operations to be performed (DeleteRequest or PutRequest). Each element in the map consists of the following: DeleteRequest - Perform a DeleteItem operation on the specified item. The item to be deleted is identified by a Key subelement: Key - A map of primary key attribute values that uniquely identify the item. Each entry in this map consists of an attribute name and an attribute value. For each primary key, you must provide all of the key attributes. For example, with a simple primary key, you only need to provide a value for the partition key. For a composite primary key, you must provide values for both the partition key and the sort key. PutRequest - Perform a PutItem operation on the specified item. The item to be put is identified by an Item subelement: Item - A map of attributes and their values. Each entry in this map consists of an attribute name and an attribute value. Attribute values must not be null; string and binary type attributes must have lengths greater than zero; and set type attributes must not be empty. Requests that contain empty values are rejected with a ValidationException exception. If you specify any attributes that are part of an index key, then the data types for those attributes must match those of the schema in the table's attribute definition.
621 */
622 RequestItems: BatchWriteItemRequestMap;
623 ReturnConsumedCapacity?: ReturnConsumedCapacity;
624 /**
625 * Determines whether item collection metrics are returned. If set to SIZE, the response includes statistics about item collections, if any, that were modified during the operation are returned in the response. If set to NONE (the default), no statistics are returned.
626 */
627 ReturnItemCollectionMetrics?: ReturnItemCollectionMetrics;
628 }
629 export interface BatchWriteItemOutput {
630 /**
631 * A map of tables and requests against those tables that were not processed. The UnprocessedItems value is in the same form as RequestItems, so you can provide this value directly to a subsequent BatchGetItem operation. For more information, see RequestItems in the Request Parameters section. Each UnprocessedItems entry consists of a table name and, for that table, a list of operations to perform (DeleteRequest or PutRequest). DeleteRequest - Perform a DeleteItem operation on the specified item. The item to be deleted is identified by a Key subelement: Key - A map of primary key attribute values that uniquely identify the item. Each entry in this map consists of an attribute name and an attribute value. PutRequest - Perform a PutItem operation on the specified item. The item to be put is identified by an Item subelement: Item - A map of attributes and their values. Each entry in this map consists of an attribute name and an attribute value. Attribute values must not be null; string and binary type attributes must have lengths greater than zero; and set type attributes must not be empty. Requests that contain empty values will be rejected with a ValidationException exception. If you specify any attributes that are part of an index key, then the data types for those attributes must match those of the schema in the table's attribute definition. If there are no unprocessed items remaining, the response contains an empty UnprocessedItems map.
632 */
633 UnprocessedItems?: BatchWriteItemRequestMap;
634 /**
635 * A list of tables that were processed by BatchWriteItem and, for each table, information about any item collections that were affected by individual DeleteItem or PutItem operations. Each entry consists of the following subelements: ItemCollectionKey - The partition key value of the item collection. This is the same as the partition key value of the item. SizeEstimateRangeGB - An estimate of item collection size, expressed in GB. This is a two-element array containing a lower bound and an upper bound for the estimate. The estimate includes the size of all the items in the table, plus the size of all attributes projected into all of the local secondary indexes on the table. Use this estimate to measure whether a local secondary index is approaching its size limit. The estimate is subject to change over time; therefore, do not rely on the precision or accuracy of the estimate.
636 */
637 ItemCollectionMetrics?: ItemCollectionMetricsPerTable;
638 /**
639 * The capacity units consumed by the entire BatchWriteItem operation. Each element consists of: TableName - The table that consumed the provisioned throughput. CapacityUnits - The total number of capacity units consumed.
640 */
641 ConsumedCapacity?: ConsumedCapacityMultiple;
642 }
643 export type BatchWriteItemRequestMap = {[key: string]: WriteRequests};
644 export type BillingMode = "PROVISIONED"|"PAY_PER_REQUEST"|string;
645 export interface BillingModeSummary {
646 /**
647 * Controls how you are charged for read and write throughput and how you manage capacity. This setting can be changed later. PROVISIONED - Sets the read/write capacity mode to PROVISIONED. We recommend using PROVISIONED for predictable workloads. PAY_PER_REQUEST - Sets the read/write capacity mode to PAY_PER_REQUEST. We recommend using PAY_PER_REQUEST for unpredictable workloads.
648 */
649 BillingMode?: BillingMode;
650 /**
651 * Represents the time when PAY_PER_REQUEST was last set as the read/write capacity mode.
652 */
653 LastUpdateToPayPerRequestDateTime?: _Date;
654 }
655 export type BinaryAttributeValue = Buffer|Uint8Array|Blob|string;
656 export type BinarySetAttributeValue = BinaryAttributeValue[];
657 export type BooleanAttributeValue = boolean;
658 export type BooleanObject = boolean;
659 export interface Capacity {
660 /**
661 * The total number of read capacity units consumed on a table or an index.
662 */
663 ReadCapacityUnits?: ConsumedCapacityUnits;
664 /**
665 * The total number of write capacity units consumed on a table or an index.
666 */
667 WriteCapacityUnits?: ConsumedCapacityUnits;
668 /**
669 * The total number of capacity units consumed on a table or an index.
670 */
671 CapacityUnits?: ConsumedCapacityUnits;
672 }
673 export type ClientRequestToken = string;
674 export type ComparisonOperator = "EQ"|"NE"|"IN"|"LE"|"LT"|"GE"|"GT"|"BETWEEN"|"NOT_NULL"|"NULL"|"CONTAINS"|"NOT_CONTAINS"|"BEGINS_WITH"|string;
675 export interface Condition {
676 /**
677 * One or more values to evaluate against the supplied attribute. The number of values in the list depends on the ComparisonOperator being used. For type Number, value comparisons are numeric. String value comparisons for greater than, equals, or less than are based on ASCII character code values. For example, a is greater than A, and a is greater than B. For a list of code values, see http://en.wikipedia.org/wiki/ASCII#ASCII_printable_characters. For Binary, DynamoDB treats each byte of the binary data as unsigned when it compares binary values.
678 */
679 AttributeValueList?: AttributeValueList;
680 /**
681 * A comparator for evaluating attributes. For example, equals, greater than, less than, etc. The following comparison operators are available: EQ | NE | LE | LT | GE | GT | NOT_NULL | NULL | CONTAINS | NOT_CONTAINS | BEGINS_WITH | IN | BETWEEN The following are descriptions of each comparison operator. EQ : Equal. EQ is supported for all data types, including lists and maps. AttributeValueList can contain only one AttributeValue element of type String, Number, Binary, String Set, Number Set, or Binary Set. If an item contains an AttributeValue element of a different type than the one provided in the request, the value does not match. For example, {"S":"6"} does not equal {"N":"6"}. Also, {"N":"6"} does not equal {"NS":["6", "2", "1"]}. NE : Not equal. NE is supported for all data types, including lists and maps. AttributeValueList can contain only one AttributeValue of type String, Number, Binary, String Set, Number Set, or Binary Set. If an item contains an AttributeValue of a different type than the one provided in the request, the value does not match. For example, {"S":"6"} does not equal {"N":"6"}. Also, {"N":"6"} does not equal {"NS":["6", "2", "1"]}. LE : Less than or equal. AttributeValueList can contain only one AttributeValue element of type String, Number, or Binary (not a set type). If an item contains an AttributeValue element of a different type than the one provided in the request, the value does not match. For example, {"S":"6"} does not equal {"N":"6"}. Also, {"N":"6"} does not compare to {"NS":["6", "2", "1"]}. LT : Less than. AttributeValueList can contain only one AttributeValue of type String, Number, or Binary (not a set type). If an item contains an AttributeValue element of a different type than the one provided in the request, the value does not match. For example, {"S":"6"} does not equal {"N":"6"}. Also, {"N":"6"} does not compare to {"NS":["6", "2", "1"]}. GE : Greater than or equal. AttributeValueList can contain only one AttributeValue element of type String, Number, or Binary (not a set type). If an item contains an AttributeValue element of a different type than the one provided in the request, the value does not match. For example, {"S":"6"} does not equal {"N":"6"}. Also, {"N":"6"} does not compare to {"NS":["6", "2", "1"]}. GT : Greater than. AttributeValueList can contain only one AttributeValue element of type String, Number, or Binary (not a set type). If an item contains an AttributeValue element of a different type than the one provided in the request, the value does not match. For example, {"S":"6"} does not equal {"N":"6"}. Also, {"N":"6"} does not compare to {"NS":["6", "2", "1"]}. NOT_NULL : The attribute exists. NOT_NULL is supported for all data types, including lists and maps. This operator tests for the existence of an attribute, not its data type. If the data type of attribute "a" is null, and you evaluate it using NOT_NULL, the result is a Boolean true. This result is because the attribute "a" exists; its data type is not relevant to the NOT_NULL comparison operator. NULL : The attribute does not exist. NULL is supported for all data types, including lists and maps. This operator tests for the nonexistence of an attribute, not its data type. If the data type of attribute "a" is null, and you evaluate it using NULL, the result is a Boolean false. This is because the attribute "a" exists; its data type is not relevant to the NULL comparison operator. CONTAINS : Checks for a subsequence, or value in a set. AttributeValueList can contain only one AttributeValue element of type String, Number, or Binary (not a set type). If the target attribute of the comparison is of type String, then the operator checks for a substring match. If the target attribute of the comparison is of type Binary, then the operator looks for a subsequence of the target that matches the input. If the target attribute of the comparison is a set ("SS", "NS", or "BS"), then the operator evaluates to true if it finds an exact match with any member of the set. CONTAINS is supported for lists: When evaluating "a CONTAINS b", "a" can be a list; however, "b" cannot be a set, a map, or a list. NOT_CONTAINS : Checks for absence of a subsequence, or absence of a value in a set. AttributeValueList can contain only one AttributeValue element of type String, Number, or Binary (not a set type). If the target attribute of the comparison is a String, then the operator checks for the absence of a substring match. If the target attribute of the comparison is Binary, then the operator checks for the absence of a subsequence of the target that matches the input. If the target attribute of the comparison is a set ("SS", "NS", or "BS"), then the operator evaluates to true if it does not find an exact match with any member of the set. NOT_CONTAINS is supported for lists: When evaluating "a NOT CONTAINS b", "a" can be a list; however, "b" cannot be a set, a map, or a list. BEGINS_WITH : Checks for a prefix. AttributeValueList can contain only one AttributeValue of type String or Binary (not a Number or a set type). The target attribute of the comparison must be of type String or Binary (not a Number or a set type). IN : Checks for matching elements in a list. AttributeValueList can contain one or more AttributeValue elements of type String, Number, or Binary. These attributes are compared against an existing attribute of an item. If any elements of the input are equal to the item attribute, the expression evaluates to true. BETWEEN : Greater than or equal to the first value, and less than or equal to the second value. AttributeValueList must contain two AttributeValue elements of the same type, either String, Number, or Binary (not a set type). A target attribute matches if the target value is greater than, or equal to, the first element and less than, or equal to, the second element. If an item contains an AttributeValue element of a different type than the one provided in the request, the value does not match. For example, {"S":"6"} does not compare to {"N":"6"}. Also, {"N":"6"} does not compare to {"NS":["6", "2", "1"]} For usage examples of AttributeValueList and ComparisonOperator, see Legacy Conditional Parameters in the Amazon DynamoDB Developer Guide.
682 */
683 ComparisonOperator: ComparisonOperator;
684 }
685 export interface ConditionCheck {
686 /**
687 * The primary key of the item to be checked. Each element consists of an attribute name and a value for that attribute.
688 */
689 Key: Key;
690 /**
691 * Name of the table for the check item request.
692 */
693 TableName: TableName;
694 /**
695 * A condition that must be satisfied in order for a conditional update to succeed.
696 */
697 ConditionExpression: ConditionExpression;
698 /**
699 * One or more substitution tokens for attribute names in an expression.
700 */
701 ExpressionAttributeNames?: ExpressionAttributeNameMap;
702 /**
703 * One or more values that can be substituted in an expression.
704 */
705 ExpressionAttributeValues?: ExpressionAttributeValueMap;
706 /**
707 * Use ReturnValuesOnConditionCheckFailure to get the item attributes if the ConditionCheck condition fails. For ReturnValuesOnConditionCheckFailure, the valid values are: NONE and ALL_OLD.
708 */
709 ReturnValuesOnConditionCheckFailure?: ReturnValuesOnConditionCheckFailure;
710 }
711 export type ConditionExpression = string;
712 export type ConditionalOperator = "AND"|"OR"|string;
713 export type ConsistentRead = boolean;
714 export interface ConsumedCapacity {
715 /**
716 * The name of the table that was affected by the operation.
717 */
718 TableName?: TableName;
719 /**
720 * The total number of capacity units consumed by the operation.
721 */
722 CapacityUnits?: ConsumedCapacityUnits;
723 /**
724 * The total number of read capacity units consumed by the operation.
725 */
726 ReadCapacityUnits?: ConsumedCapacityUnits;
727 /**
728 * The total number of write capacity units consumed by the operation.
729 */
730 WriteCapacityUnits?: ConsumedCapacityUnits;
731 /**
732 * The amount of throughput consumed on the table affected by the operation.
733 */
734 Table?: Capacity;
735 /**
736 * The amount of throughput consumed on each local index affected by the operation.
737 */
738 LocalSecondaryIndexes?: SecondaryIndexesCapacityMap;
739 /**
740 * The amount of throughput consumed on each global index affected by the operation.
741 */
742 GlobalSecondaryIndexes?: SecondaryIndexesCapacityMap;
743 }
744 export type ConsumedCapacityMultiple = ConsumedCapacity[];
745 export type ConsumedCapacityUnits = number;
746 export interface ContinuousBackupsDescription {
747 /**
748 * ContinuousBackupsStatus can be one of the following states: ENABLED, DISABLED
749 */
750 ContinuousBackupsStatus: ContinuousBackupsStatus;
751 /**
752 * The description of the point in time recovery settings applied to the table.
753 */
754 PointInTimeRecoveryDescription?: PointInTimeRecoveryDescription;
755 }
756 export type ContinuousBackupsStatus = "ENABLED"|"DISABLED"|string;
757 export interface CreateBackupInput {
758 /**
759 * The name of the table.
760 */
761 TableName: TableName;
762 /**
763 * Specified name for the backup.
764 */
765 BackupName: BackupName;
766 }
767 export interface CreateBackupOutput {
768 /**
769 * Contains the details of the backup created for the table.
770 */
771 BackupDetails?: BackupDetails;
772 }
773 export interface CreateGlobalSecondaryIndexAction {
774 /**
775 * The name of the global secondary index to be created.
776 */
777 IndexName: IndexName;
778 /**
779 * The key schema for the global secondary index.
780 */
781 KeySchema: KeySchema;
782 /**
783 * Represents attributes that are copied (projected) from the table into an index. These are in addition to the primary key attributes and index key attributes, which are automatically projected.
784 */
785 Projection: Projection;
786 /**
787 * Represents the provisioned throughput settings for the specified global secondary index. For current minimum and maximum provisioned throughput values, see Limits in the Amazon DynamoDB Developer Guide.
788 */
789 ProvisionedThroughput?: ProvisionedThroughput;
790 }
791 export interface CreateGlobalTableInput {
792 /**
793 * The global table name.
794 */
795 GlobalTableName: TableName;
796 /**
797 * The Regions where the global table needs to be created.
798 */
799 ReplicationGroup: ReplicaList;
800 }
801 export interface CreateGlobalTableOutput {
802 /**
803 * Contains the details of the global table.
804 */
805 GlobalTableDescription?: GlobalTableDescription;
806 }
807 export interface CreateReplicaAction {
808 /**
809 * The region of the replica to be added.
810 */
811 RegionName: RegionName;
812 }
813 export interface CreateTableInput {
814 /**
815 * An array of attributes that describe the key schema for the table and indexes.
816 */
817 AttributeDefinitions: AttributeDefinitions;
818 /**
819 * The name of the table to create.
820 */
821 TableName: TableName;
822 /**
823 * Specifies the attributes that make up the primary key for a table or an index. The attributes in KeySchema must also be defined in the AttributeDefinitions array. For more information, see Data Model in the Amazon DynamoDB Developer Guide. Each KeySchemaElement in the array is composed of: AttributeName - The name of this key attribute. KeyType - The role that the key attribute will assume: HASH - partition key RANGE - sort key The partition key of an item is also known as its hash attribute. The term "hash attribute" derives from the DynamoDB usage of an internal hash function to evenly distribute data items across partitions, based on their partition key values. The sort key of an item is also known as its range attribute. The term "range attribute" derives from the way DynamoDB stores items with the same partition key physically close together, in sorted order by the sort key value. For a simple primary key (partition key), you must provide exactly one element with a KeyType of HASH. For a composite primary key (partition key and sort key), you must provide exactly two elements, in this order: The first element must have a KeyType of HASH, and the second element must have a KeyType of RANGE. For more information, see Working with Tables in the Amazon DynamoDB Developer Guide.
824 */
825 KeySchema: KeySchema;
826 /**
827 * One or more local secondary indexes (the maximum is 5) to be created on the table. Each index is scoped to a given partition key value. There is a 10 GB size limit per partition key value; otherwise, the size of a local secondary index is unconstrained. Each local secondary index in the array includes the following: IndexName - The name of the local secondary index. Must be unique only for this table. KeySchema - Specifies the key schema for the local secondary index. The key schema must begin with the same partition key as the table. Projection - Specifies attributes that are copied (projected) from the table into the index. These are in addition to the primary key attributes and index key attributes, which are automatically projected. Each attribute specification is composed of: ProjectionType - One of the following: KEYS_ONLY - Only the index and primary keys are projected into the index. INCLUDE - Only the specified table attributes are projected into the index. The list of projected attributes is in NonKeyAttributes. ALL - All of the table attributes are projected into the index. NonKeyAttributes - A list of one or more non-key attribute names that are projected into the secondary index. The total count of attributes provided in NonKeyAttributes, summed across all of the secondary indexes, must not exceed 100. If you project the same attribute into two different indexes, this counts as two distinct attributes when determining the total.
828 */
829 LocalSecondaryIndexes?: LocalSecondaryIndexList;
830 /**
831 * One or more global secondary indexes (the maximum is 20) to be created on the table. Each global secondary index in the array includes the following: IndexName - The name of the global secondary index. Must be unique only for this table. KeySchema - Specifies the key schema for the global secondary index. Projection - Specifies attributes that are copied (projected) from the table into the index. These are in addition to the primary key attributes and index key attributes, which are automatically projected. Each attribute specification is composed of: ProjectionType - One of the following: KEYS_ONLY - Only the index and primary keys are projected into the index. INCLUDE - Only the specified table attributes are projected into the index. The list of projected attributes is in NonKeyAttributes. ALL - All of the table attributes are projected into the index. NonKeyAttributes - A list of one or more non-key attribute names that are projected into the secondary index. The total count of attributes provided in NonKeyAttributes, summed across all of the secondary indexes, must not exceed 100. If you project the same attribute into two different indexes, this counts as two distinct attributes when determining the total. ProvisionedThroughput - The provisioned throughput settings for the global secondary index, consisting of read and write capacity units.
832 */
833 GlobalSecondaryIndexes?: GlobalSecondaryIndexList;
834 /**
835 * Controls how you are charged for read and write throughput and how you manage capacity. This setting can be changed later. PROVISIONED - Sets the billing mode to PROVISIONED. We recommend using PROVISIONED for predictable workloads. PAY_PER_REQUEST - Sets the billing mode to PAY_PER_REQUEST. We recommend using PAY_PER_REQUEST for unpredictable workloads.
836 */
837 BillingMode?: BillingMode;
838 /**
839 * Represents the provisioned throughput settings for a specified table or index. The settings can be modified using the UpdateTable operation. If you set BillingMode as PROVISIONED, you must specify this property. If you set BillingMode as PAY_PER_REQUEST, you cannot specify this property. For current minimum and maximum provisioned throughput values, see Limits in the Amazon DynamoDB Developer Guide.
840 */
841 ProvisionedThroughput?: ProvisionedThroughput;
842 /**
843 * The settings for DynamoDB Streams on the table. These settings consist of: StreamEnabled - Indicates whether DynamoDB Streams is to be enabled (true) or disabled (false). StreamViewType - When an item in the table is modified, StreamViewType determines what information is written to the table's stream. Valid values for StreamViewType are: KEYS_ONLY - Only the key attributes of the modified item are written to the stream. NEW_IMAGE - The entire item, as it appears after it was modified, is written to the stream. OLD_IMAGE - The entire item, as it appeared before it was modified, is written to the stream. NEW_AND_OLD_IMAGES - Both the new and the old item images of the item are written to the stream.
844 */
845 StreamSpecification?: StreamSpecification;
846 /**
847 * Represents the settings used to enable server-side encryption.
848 */
849 SSESpecification?: SSESpecification;
850 /**
851 * A list of key-value pairs to label the table. For more information, see Tagging for DynamoDB.
852 */
853 Tags?: TagList;
854 }
855 export interface CreateTableOutput {
856 /**
857 * Represents the properties of the table.
858 */
859 TableDescription?: TableDescription;
860 }
861 export type _Date = Date;
862 export interface Delete {
863 /**
864 * The primary key of the item to be deleted. Each element consists of an attribute name and a value for that attribute.
865 */
866 Key: Key;
867 /**
868 * Name of the table in which the item to be deleted resides.
869 */
870 TableName: TableName;
871 /**
872 * A condition that must be satisfied in order for a conditional delete to succeed.
873 */
874 ConditionExpression?: ConditionExpression;
875 /**
876 * One or more substitution tokens for attribute names in an expression.
877 */
878 ExpressionAttributeNames?: ExpressionAttributeNameMap;
879 /**
880 * One or more values that can be substituted in an expression.
881 */
882 ExpressionAttributeValues?: ExpressionAttributeValueMap;
883 /**
884 * Use ReturnValuesOnConditionCheckFailure to get the item attributes if the Delete condition fails. For ReturnValuesOnConditionCheckFailure, the valid values are: NONE and ALL_OLD.
885 */
886 ReturnValuesOnConditionCheckFailure?: ReturnValuesOnConditionCheckFailure;
887 }
888 export interface DeleteBackupInput {
889 /**
890 * The ARN associated with the backup.
891 */
892 BackupArn: BackupArn;
893 }
894 export interface DeleteBackupOutput {
895 /**
896 * Contains the description of the backup created for the table.
897 */
898 BackupDescription?: BackupDescription;
899 }
900 export interface DeleteGlobalSecondaryIndexAction {
901 /**
902 * The name of the global secondary index to be deleted.
903 */
904 IndexName: IndexName;
905 }
906 export interface DeleteItemInput {
907 /**
908 * The name of the table from which to delete the item.
909 */
910 TableName: TableName;
911 /**
912 * A map of attribute names to AttributeValue objects, representing the primary key of the item to delete. For the primary key, you must provide all of the attributes. For example, with a simple primary key, you only need to provide a value for the partition key. For a composite primary key, you must provide values for both the partition key and the sort key.
913 */
914 Key: Key;
915 /**
916 * This is a legacy parameter. Use ConditionExpression instead. For more information, see Expected in the Amazon DynamoDB Developer Guide.
917 */
918 Expected?: ExpectedAttributeMap;
919 /**
920 * This is a legacy parameter. Use ConditionExpression instead. For more information, see ConditionalOperator in the Amazon DynamoDB Developer Guide.
921 */
922 ConditionalOperator?: ConditionalOperator;
923 /**
924 * Use ReturnValues if you want to get the item attributes as they appeared before they were deleted. For DeleteItem, the valid values are: NONE - If ReturnValues is not specified, or if its value is NONE, then nothing is returned. (This setting is the default for ReturnValues.) ALL_OLD - The content of the old item is returned. The ReturnValues parameter is used by several DynamoDB operations; however, DeleteItem does not recognize any values other than NONE or ALL_OLD.
925 */
926 ReturnValues?: ReturnValue;
927 ReturnConsumedCapacity?: ReturnConsumedCapacity;
928 /**
929 * Determines whether item collection metrics are returned. If set to SIZE, the response includes statistics about item collections, if any, that were modified during the operation are returned in the response. If set to NONE (the default), no statistics are returned.
930 */
931 ReturnItemCollectionMetrics?: ReturnItemCollectionMetrics;
932 /**
933 * A condition that must be satisfied in order for a conditional DeleteItem to succeed. An expression can contain any of the following: Functions: attribute_exists | attribute_not_exists | attribute_type | contains | begins_with | size These function names are case-sensitive. Comparison operators: = | &lt;&gt; | &lt; | &gt; | &lt;= | &gt;= | BETWEEN | IN Logical operators: AND | OR | NOT For more information about condition expressions, see Condition Expressions in the Amazon DynamoDB Developer Guide.
934 */
935 ConditionExpression?: ConditionExpression;
936 /**
937 * One or more substitution tokens for attribute names in an expression. The following are some use cases for using ExpressionAttributeNames: To access an attribute whose name conflicts with a DynamoDB reserved word. To create a placeholder for repeating occurrences of an attribute name in an expression. To prevent special characters in an attribute name from being misinterpreted in an expression. Use the # character in an expression to dereference an attribute name. For example, consider the following attribute name: Percentile The name of this attribute conflicts with a reserved word, so it cannot be used directly in an expression. (For the complete list of reserved words, see Reserved Words in the Amazon DynamoDB Developer Guide). To work around this, you could specify the following for ExpressionAttributeNames: {"#P":"Percentile"} You could then use this substitution in an expression, as in this example: #P = :val Tokens that begin with the : character are expression attribute values, which are placeholders for the actual value at runtime. For more information on expression attribute names, see Specifying Item Attributes in the Amazon DynamoDB Developer Guide.
938 */
939 ExpressionAttributeNames?: ExpressionAttributeNameMap;
940 /**
941 * One or more values that can be substituted in an expression. Use the : (colon) character in an expression to dereference an attribute value. For example, suppose that you wanted to check whether the value of the ProductStatus attribute was one of the following: Available | Backordered | Discontinued You would first need to specify ExpressionAttributeValues as follows: { ":avail":{"S":"Available"}, ":back":{"S":"Backordered"}, ":disc":{"S":"Discontinued"} } You could then use these values in an expression, such as this: ProductStatus IN (:avail, :back, :disc) For more information on expression attribute values, see Condition Expressions in the Amazon DynamoDB Developer Guide.
942 */
943 ExpressionAttributeValues?: ExpressionAttributeValueMap;
944 }
945 export interface DeleteItemOutput {
946 /**
947 * A map of attribute names to AttributeValue objects, representing the item as it appeared before the DeleteItem operation. This map appears in the response only if ReturnValues was specified as ALL_OLD in the request.
948 */
949 Attributes?: AttributeMap;
950 /**
951 * The capacity units consumed by the DeleteItem operation. The data returned includes the total provisioned throughput consumed, along with statistics for the table and any indexes involved in the operation. ConsumedCapacity is only returned if the ReturnConsumedCapacity parameter was specified. For more information, see Provisioned Mode in the Amazon DynamoDB Developer Guide.
952 */
953 ConsumedCapacity?: ConsumedCapacity;
954 /**
955 * Information about item collections, if any, that were affected by the DeleteItem operation. ItemCollectionMetrics is only returned if the ReturnItemCollectionMetrics parameter was specified. If the table does not have any local secondary indexes, this information is not returned in the response. Each ItemCollectionMetrics element consists of: ItemCollectionKey - The partition key value of the item collection. This is the same as the partition key value of the item itself. SizeEstimateRangeGB - An estimate of item collection size, in gigabytes. This value is a two-element array containing a lower bound and an upper bound for the estimate. The estimate includes the size of all the items in the table, plus the size of all attributes projected into all of the local secondary indexes on that table. Use this estimate to measure whether a local secondary index is approaching its size limit. The estimate is subject to change over time; therefore, do not rely on the precision or accuracy of the estimate.
956 */
957 ItemCollectionMetrics?: ItemCollectionMetrics;
958 }
959 export interface DeleteReplicaAction {
960 /**
961 * The region of the replica to be removed.
962 */
963 RegionName: RegionName;
964 }
965 export interface DeleteRequest {
966 /**
967 * A map of attribute name to attribute values, representing the primary key of the item to delete. All of the table's primary key attributes must be specified, and their data types must match those of the table's key schema.
968 */
969 Key: Key;
970 }
971 export interface DeleteTableInput {
972 /**
973 * The name of the table to delete.
974 */
975 TableName: TableName;
976 }
977 export interface DeleteTableOutput {
978 /**
979 * Represents the properties of a table.
980 */
981 TableDescription?: TableDescription;
982 }
983 export interface DescribeBackupInput {
984 /**
985 * The Amazon Resource Name (ARN) associated with the backup.
986 */
987 BackupArn: BackupArn;
988 }
989 export interface DescribeBackupOutput {
990 /**
991 * Contains the description of the backup created for the table.
992 */
993 BackupDescription?: BackupDescription;
994 }
995 export interface DescribeContinuousBackupsInput {
996 /**
997 * Name of the table for which the customer wants to check the continuous backups and point in time recovery settings.
998 */
999 TableName: TableName;
1000 }
1001 export interface DescribeContinuousBackupsOutput {
1002 /**
1003 * Represents the continuous backups and point in time recovery settings on the table.
1004 */
1005 ContinuousBackupsDescription?: ContinuousBackupsDescription;
1006 }
1007 export interface DescribeEndpointsRequest {
1008 }
1009 export interface DescribeEndpointsResponse {
1010 /**
1011 * List of endpoints.
1012 */
1013 Endpoints: Endpoints;
1014 }
1015 export interface DescribeGlobalTableInput {
1016 /**
1017 * The name of the global table.
1018 */
1019 GlobalTableName: TableName;
1020 }
1021 export interface DescribeGlobalTableOutput {
1022 /**
1023 * Contains the details of the global table.
1024 */
1025 GlobalTableDescription?: GlobalTableDescription;
1026 }
1027 export interface DescribeGlobalTableSettingsInput {
1028 /**
1029 * The name of the global table to describe.
1030 */
1031 GlobalTableName: TableName;
1032 }
1033 export interface DescribeGlobalTableSettingsOutput {
1034 /**
1035 * The name of the global table.
1036 */
1037 GlobalTableName?: TableName;
1038 /**
1039 * The Region-specific settings for the global table.
1040 */
1041 ReplicaSettings?: ReplicaSettingsDescriptionList;
1042 }
1043 export interface DescribeLimitsInput {
1044 }
1045 export interface DescribeLimitsOutput {
1046 /**
1047 * The maximum total read capacity units that your account allows you to provision across all of your tables in this Region.
1048 */
1049 AccountMaxReadCapacityUnits?: PositiveLongObject;
1050 /**
1051 * The maximum total write capacity units that your account allows you to provision across all of your tables in this Region.
1052 */
1053 AccountMaxWriteCapacityUnits?: PositiveLongObject;
1054 /**
1055 * The maximum read capacity units that your account allows you to provision for a new table that you are creating in this Region, including the read capacity units provisioned for its global secondary indexes (GSIs).
1056 */
1057 TableMaxReadCapacityUnits?: PositiveLongObject;
1058 /**
1059 * The maximum write capacity units that your account allows you to provision for a new table that you are creating in this Region, including the write capacity units provisioned for its global secondary indexes (GSIs).
1060 */
1061 TableMaxWriteCapacityUnits?: PositiveLongObject;
1062 }
1063 export interface DescribeTableInput {
1064 /**
1065 * The name of the table to describe.
1066 */
1067 TableName: TableName;
1068 }
1069 export interface DescribeTableOutput {
1070 /**
1071 * The properties of the table.
1072 */
1073 Table?: TableDescription;
1074 }
1075 export interface DescribeTimeToLiveInput {
1076 /**
1077 * The name of the table to be described.
1078 */
1079 TableName: TableName;
1080 }
1081 export interface DescribeTimeToLiveOutput {
1082 /**
1083 *
1084 */
1085 TimeToLiveDescription?: TimeToLiveDescription;
1086 }
1087 export type Double = number;
1088 export interface Endpoint {
1089 /**
1090 * IP address of the endpoint.
1091 */
1092 Address: String;
1093 /**
1094 * Endpoint cache time to live (TTL) value.
1095 */
1096 CachePeriodInMinutes: Long;
1097 }
1098 export type Endpoints = Endpoint[];
1099 export type ExpectedAttributeMap = {[key: string]: ExpectedAttributeValue};
1100 export interface ExpectedAttributeValue {
1101 /**
1102 * Represents the data for the expected attribute. Each attribute value is described as a name-value pair. The name is the data type, and the value is the data itself. For more information, see Data Types in the Amazon DynamoDB Developer Guide.
1103 */
1104 Value?: AttributeValue;
1105 /**
1106 * Causes DynamoDB to evaluate the value before attempting a conditional operation: If Exists is true, DynamoDB will check to see if that attribute value already exists in the table. If it is found, then the operation succeeds. If it is not found, the operation fails with a ConditionCheckFailedException. If Exists is false, DynamoDB assumes that the attribute value does not exist in the table. If in fact the value does not exist, then the assumption is valid and the operation succeeds. If the value is found, despite the assumption that it does not exist, the operation fails with a ConditionCheckFailedException. The default setting for Exists is true. If you supply a Value all by itself, DynamoDB assumes the attribute exists: You don't have to set Exists to true, because it is implied. DynamoDB returns a ValidationException if: Exists is true but there is no Value to check. (You expect a value to exist, but don't specify what that value is.) Exists is false but you also provide a Value. (You cannot expect an attribute to have a value, while also expecting it not to exist.)
1107 */
1108 Exists?: BooleanObject;
1109 /**
1110 * A comparator for evaluating attributes in the AttributeValueList. For example, equals, greater than, less than, etc. The following comparison operators are available: EQ | NE | LE | LT | GE | GT | NOT_NULL | NULL | CONTAINS | NOT_CONTAINS | BEGINS_WITH | IN | BETWEEN The following are descriptions of each comparison operator. EQ : Equal. EQ is supported for all data types, including lists and maps. AttributeValueList can contain only one AttributeValue element of type String, Number, Binary, String Set, Number Set, or Binary Set. If an item contains an AttributeValue element of a different type than the one provided in the request, the value does not match. For example, {"S":"6"} does not equal {"N":"6"}. Also, {"N":"6"} does not equal {"NS":["6", "2", "1"]}. NE : Not equal. NE is supported for all data types, including lists and maps. AttributeValueList can contain only one AttributeValue of type String, Number, Binary, String Set, Number Set, or Binary Set. If an item contains an AttributeValue of a different type than the one provided in the request, the value does not match. For example, {"S":"6"} does not equal {"N":"6"}. Also, {"N":"6"} does not equal {"NS":["6", "2", "1"]}. LE : Less than or equal. AttributeValueList can contain only one AttributeValue element of type String, Number, or Binary (not a set type). If an item contains an AttributeValue element of a different type than the one provided in the request, the value does not match. For example, {"S":"6"} does not equal {"N":"6"}. Also, {"N":"6"} does not compare to {"NS":["6", "2", "1"]}. LT : Less than. AttributeValueList can contain only one AttributeValue of type String, Number, or Binary (not a set type). If an item contains an AttributeValue element of a different type than the one provided in the request, the value does not match. For example, {"S":"6"} does not equal {"N":"6"}. Also, {"N":"6"} does not compare to {"NS":["6", "2", "1"]}. GE : Greater than or equal. AttributeValueList can contain only one AttributeValue element of type String, Number, or Binary (not a set type). If an item contains an AttributeValue element of a different type than the one provided in the request, the value does not match. For example, {"S":"6"} does not equal {"N":"6"}. Also, {"N":"6"} does not compare to {"NS":["6", "2", "1"]}. GT : Greater than. AttributeValueList can contain only one AttributeValue element of type String, Number, or Binary (not a set type). If an item contains an AttributeValue element of a different type than the one provided in the request, the value does not match. For example, {"S":"6"} does not equal {"N":"6"}. Also, {"N":"6"} does not compare to {"NS":["6", "2", "1"]}. NOT_NULL : The attribute exists. NOT_NULL is supported for all data types, including lists and maps. This operator tests for the existence of an attribute, not its data type. If the data type of attribute "a" is null, and you evaluate it using NOT_NULL, the result is a Boolean true. This result is because the attribute "a" exists; its data type is not relevant to the NOT_NULL comparison operator. NULL : The attribute does not exist. NULL is supported for all data types, including lists and maps. This operator tests for the nonexistence of an attribute, not its data type. If the data type of attribute "a" is null, and you evaluate it using NULL, the result is a Boolean false. This is because the attribute "a" exists; its data type is not relevant to the NULL comparison operator. CONTAINS : Checks for a subsequence, or value in a set. AttributeValueList can contain only one AttributeValue element of type String, Number, or Binary (not a set type). If the target attribute of the comparison is of type String, then the operator checks for a substring match. If the target attribute of the comparison is of type Binary, then the operator looks for a subsequence of the target that matches the input. If the target attribute of the comparison is a set ("SS", "NS", or "BS"), then the operator evaluates to true if it finds an exact match with any member of the set. CONTAINS is supported for lists: When evaluating "a CONTAINS b", "a" can be a list; however, "b" cannot be a set, a map, or a list. NOT_CONTAINS : Checks for absence of a subsequence, or absence of a value in a set. AttributeValueList can contain only one AttributeValue element of type String, Number, or Binary (not a set type). If the target attribute of the comparison is a String, then the operator checks for the absence of a substring match. If the target attribute of the comparison is Binary, then the operator checks for the absence of a subsequence of the target that matches the input. If the target attribute of the comparison is a set ("SS", "NS", or "BS"), then the operator evaluates to true if it does not find an exact match with any member of the set. NOT_CONTAINS is supported for lists: When evaluating "a NOT CONTAINS b", "a" can be a list; however, "b" cannot be a set, a map, or a list. BEGINS_WITH : Checks for a prefix. AttributeValueList can contain only one AttributeValue of type String or Binary (not a Number or a set type). The target attribute of the comparison must be of type String or Binary (not a Number or a set type). IN : Checks for matching elements in a list. AttributeValueList can contain one or more AttributeValue elements of type String, Number, or Binary. These attributes are compared against an existing attribute of an item. If any elements of the input are equal to the item attribute, the expression evaluates to true. BETWEEN : Greater than or equal to the first value, and less than or equal to the second value. AttributeValueList must contain two AttributeValue elements of the same type, either String, Number, or Binary (not a set type). A target attribute matches if the target value is greater than, or equal to, the first element and less than, or equal to, the second element. If an item contains an AttributeValue element of a different type than the one provided in the request, the value does not match. For example, {"S":"6"} does not compare to {"N":"6"}. Also, {"N":"6"} does not compare to {"NS":["6", "2", "1"]}
1111 */
1112 ComparisonOperator?: ComparisonOperator;
1113 /**
1114 * One or more values to evaluate against the supplied attribute. The number of values in the list depends on the ComparisonOperator being used. For type Number, value comparisons are numeric. String value comparisons for greater than, equals, or less than are based on ASCII character code values. For example, a is greater than A, and a is greater than B. For a list of code values, see http://en.wikipedia.org/wiki/ASCII#ASCII_printable_characters. For Binary, DynamoDB treats each byte of the binary data as unsigned when it compares binary values. For information on specifying data types in JSON, see JSON Data Format in the Amazon DynamoDB Developer Guide.
1115 */
1116 AttributeValueList?: AttributeValueList;
1117 }
1118 export type ExpressionAttributeNameMap = {[key: string]: AttributeName};
1119 export type ExpressionAttributeNameVariable = string;
1120 export type ExpressionAttributeValueMap = {[key: string]: AttributeValue};
1121 export type ExpressionAttributeValueVariable = string;
1122 export type FilterConditionMap = {[key: string]: Condition};
1123 export interface Get {
1124 /**
1125 * A map of attribute names to AttributeValue objects that specifies the primary key of the item to retrieve.
1126 */
1127 Key: Key;
1128 /**
1129 * The name of the table from which to retrieve the specified item.
1130 */
1131 TableName: TableName;
1132 /**
1133 * A string that identifies one or more attributes of the specified item to retrieve from the table. The attributes in the expression must be separated by commas. If no attribute names are specified, then all attributes of the specified item are returned. If any of the requested attributes are not found, they do not appear in the result.
1134 */
1135 ProjectionExpression?: ProjectionExpression;
1136 /**
1137 * One or more substitution tokens for attribute names in the ProjectionExpression parameter.
1138 */
1139 ExpressionAttributeNames?: ExpressionAttributeNameMap;
1140 }
1141 export interface GetItemInput {
1142 /**
1143 * The name of the table containing the requested item.
1144 */
1145 TableName: TableName;
1146 /**
1147 * A map of attribute names to AttributeValue objects, representing the primary key of the item to retrieve. For the primary key, you must provide all of the attributes. For example, with a simple primary key, you only need to provide a value for the partition key. For a composite primary key, you must provide values for both the partition key and the sort key.
1148 */
1149 Key: Key;
1150 /**
1151 * This is a legacy parameter. Use ProjectionExpression instead. For more information, see AttributesToGet in the Amazon DynamoDB Developer Guide.
1152 */
1153 AttributesToGet?: AttributeNameList;
1154 /**
1155 * Determines the read consistency model: If set to true, then the operation uses strongly consistent reads; otherwise, the operation uses eventually consistent reads.
1156 */
1157 ConsistentRead?: ConsistentRead;
1158 ReturnConsumedCapacity?: ReturnConsumedCapacity;
1159 /**
1160 * A string that identifies one or more attributes to retrieve from the table. These attributes can include scalars, sets, or elements of a JSON document. The attributes in the expression must be separated by commas. If no attribute names are specified, then all attributes are returned. If any of the requested attributes are not found, they do not appear in the result. For more information, see Specifying Item Attributes in the Amazon DynamoDB Developer Guide.
1161 */
1162 ProjectionExpression?: ProjectionExpression;
1163 /**
1164 * One or more substitution tokens for attribute names in an expression. The following are some use cases for using ExpressionAttributeNames: To access an attribute whose name conflicts with a DynamoDB reserved word. To create a placeholder for repeating occurrences of an attribute name in an expression. To prevent special characters in an attribute name from being misinterpreted in an expression. Use the # character in an expression to dereference an attribute name. For example, consider the following attribute name: Percentile The name of this attribute conflicts with a reserved word, so it cannot be used directly in an expression. (For the complete list of reserved words, see Reserved Words in the Amazon DynamoDB Developer Guide). To work around this, you could specify the following for ExpressionAttributeNames: {"#P":"Percentile"} You could then use this substitution in an expression, as in this example: #P = :val Tokens that begin with the : character are expression attribute values, which are placeholders for the actual value at runtime. For more information on expression attribute names, see Specifying Item Attributes in the Amazon DynamoDB Developer Guide.
1165 */
1166 ExpressionAttributeNames?: ExpressionAttributeNameMap;
1167 }
1168 export interface GetItemOutput {
1169 /**
1170 * A map of attribute names to AttributeValue objects, as specified by ProjectionExpression.
1171 */
1172 Item?: AttributeMap;
1173 /**
1174 * The capacity units consumed by the GetItem operation. The data returned includes the total provisioned throughput consumed, along with statistics for the table and any indexes involved in the operation. ConsumedCapacity is only returned if the ReturnConsumedCapacity parameter was specified. For more information, see Read/Write Capacity Mode in the Amazon DynamoDB Developer Guide.
1175 */
1176 ConsumedCapacity?: ConsumedCapacity;
1177 }
1178 export interface GlobalSecondaryIndex {
1179 /**
1180 * The name of the global secondary index. The name must be unique among all other indexes on this table.
1181 */
1182 IndexName: IndexName;
1183 /**
1184 * The complete key schema for a global secondary index, which consists of one or more pairs of attribute names and key types: HASH - partition key RANGE - sort key The partition key of an item is also known as its hash attribute. The term "hash attribute" derives from DynamoDB' usage of an internal hash function to evenly distribute data items across partitions, based on their partition key values. The sort key of an item is also known as its range attribute. The term "range attribute" derives from the way DynamoDB stores items with the same partition key physically close together, in sorted order by the sort key value.
1185 */
1186 KeySchema: KeySchema;
1187 /**
1188 * Represents attributes that are copied (projected) from the table into the global secondary index. These are in addition to the primary key attributes and index key attributes, which are automatically projected.
1189 */
1190 Projection: Projection;
1191 /**
1192 * Represents the provisioned throughput settings for the specified global secondary index. For current minimum and maximum provisioned throughput values, see Limits in the Amazon DynamoDB Developer Guide.
1193 */
1194 ProvisionedThroughput?: ProvisionedThroughput;
1195 }
1196 export interface GlobalSecondaryIndexDescription {
1197 /**
1198 * The name of the global secondary index.
1199 */
1200 IndexName?: IndexName;
1201 /**
1202 * The complete key schema for a global secondary index, which consists of one or more pairs of attribute names and key types: HASH - partition key RANGE - sort key The partition key of an item is also known as its hash attribute. The term "hash attribute" derives from DynamoDB' usage of an internal hash function to evenly distribute data items across partitions, based on their partition key values. The sort key of an item is also known as its range attribute. The term "range attribute" derives from the way DynamoDB stores items with the same partition key physically close together, in sorted order by the sort key value.
1203 */
1204 KeySchema?: KeySchema;
1205 /**
1206 * Represents attributes that are copied (projected) from the table into the global secondary index. These are in addition to the primary key attributes and index key attributes, which are automatically projected.
1207 */
1208 Projection?: Projection;
1209 /**
1210 * The current state of the global secondary index: CREATING - The index is being created. UPDATING - The index is being updated. DELETING - The index is being deleted. ACTIVE - The index is ready for use.
1211 */
1212 IndexStatus?: IndexStatus;
1213 /**
1214 * Indicates whether the index is currently backfilling. Backfilling is the process of reading items from the table and determining whether they can be added to the index. (Not all items will qualify: For example, a partition key cannot have any duplicate values.) If an item can be added to the index, DynamoDB will do so. After all items have been processed, the backfilling operation is complete and Backfilling is false. For indexes that were created during a CreateTable operation, the Backfilling attribute does not appear in the DescribeTable output.
1215 */
1216 Backfilling?: Backfilling;
1217 /**
1218 * Represents the provisioned throughput settings for the specified global secondary index. For current minimum and maximum provisioned throughput values, see Limits in the Amazon DynamoDB Developer Guide.
1219 */
1220 ProvisionedThroughput?: ProvisionedThroughputDescription;
1221 /**
1222 * The total size of the specified index, in bytes. DynamoDB updates this value approximately every six hours. Recent changes might not be reflected in this value.
1223 */
1224 IndexSizeBytes?: Long;
1225 /**
1226 * The number of items in the specified index. DynamoDB updates this value approximately every six hours. Recent changes might not be reflected in this value.
1227 */
1228 ItemCount?: Long;
1229 /**
1230 * The Amazon Resource Name (ARN) that uniquely identifies the index.
1231 */
1232 IndexArn?: String;
1233 }
1234 export type GlobalSecondaryIndexDescriptionList = GlobalSecondaryIndexDescription[];
1235 export interface GlobalSecondaryIndexInfo {
1236 /**
1237 * The name of the global secondary index.
1238 */
1239 IndexName?: IndexName;
1240 /**
1241 * The complete key schema for a global secondary index, which consists of one or more pairs of attribute names and key types: HASH - partition key RANGE - sort key The partition key of an item is also known as its hash attribute. The term "hash attribute" derives from DynamoDB' usage of an internal hash function to evenly distribute data items across partitions, based on their partition key values. The sort key of an item is also known as its range attribute. The term "range attribute" derives from the way DynamoDB stores items with the same partition key physically close together, in sorted order by the sort key value.
1242 */
1243 KeySchema?: KeySchema;
1244 /**
1245 * Represents attributes that are copied (projected) from the table into the global secondary index. These are in addition to the primary key attributes and index key attributes, which are automatically projected.
1246 */
1247 Projection?: Projection;
1248 /**
1249 * Represents the provisioned throughput settings for the specified global secondary index.
1250 */
1251 ProvisionedThroughput?: ProvisionedThroughput;
1252 }
1253 export type GlobalSecondaryIndexList = GlobalSecondaryIndex[];
1254 export interface GlobalSecondaryIndexUpdate {
1255 /**
1256 * The name of an existing global secondary index, along with new provisioned throughput settings to be applied to that index.
1257 */
1258 Update?: UpdateGlobalSecondaryIndexAction;
1259 /**
1260 * The parameters required for creating a global secondary index on an existing table: IndexName KeySchema AttributeDefinitions Projection ProvisionedThroughput
1261 */
1262 Create?: CreateGlobalSecondaryIndexAction;
1263 /**
1264 * The name of an existing global secondary index to be removed.
1265 */
1266 Delete?: DeleteGlobalSecondaryIndexAction;
1267 }
1268 export type GlobalSecondaryIndexUpdateList = GlobalSecondaryIndexUpdate[];
1269 export type GlobalSecondaryIndexes = GlobalSecondaryIndexInfo[];
1270 export interface GlobalTable {
1271 /**
1272 * The global table name.
1273 */
1274 GlobalTableName?: TableName;
1275 /**
1276 * The regions where the global table has replicas.
1277 */
1278 ReplicationGroup?: ReplicaList;
1279 }
1280 export type GlobalTableArnString = string;
1281 export interface GlobalTableDescription {
1282 /**
1283 * The regions where the global table has replicas.
1284 */
1285 ReplicationGroup?: ReplicaDescriptionList;
1286 /**
1287 * The unique identifier of the global table.
1288 */
1289 GlobalTableArn?: GlobalTableArnString;
1290 /**
1291 * The creation time of the global table.
1292 */
1293 CreationDateTime?: _Date;
1294 /**
1295 * The current state of the global table: CREATING - The global table is being created. UPDATING - The global table is being updated. DELETING - The global table is being deleted. ACTIVE - The global table is ready for use.
1296 */
1297 GlobalTableStatus?: GlobalTableStatus;
1298 /**
1299 * The global table name.
1300 */
1301 GlobalTableName?: TableName;
1302 }
1303 export interface GlobalTableGlobalSecondaryIndexSettingsUpdate {
1304 /**
1305 * The name of the global secondary index. The name must be unique among all other indexes on this table.
1306 */
1307 IndexName: IndexName;
1308 /**
1309 * The maximum number of writes consumed per second before DynamoDB returns a ThrottlingException.
1310 */
1311 ProvisionedWriteCapacityUnits?: PositiveLongObject;
1312 /**
1313 * AutoScaling settings for managing a global secondary index's write capacity units.
1314 */
1315 ProvisionedWriteCapacityAutoScalingSettingsUpdate?: AutoScalingSettingsUpdate;
1316 }
1317 export type GlobalTableGlobalSecondaryIndexSettingsUpdateList = GlobalTableGlobalSecondaryIndexSettingsUpdate[];
1318 export type GlobalTableList = GlobalTable[];
1319 export type GlobalTableStatus = "CREATING"|"ACTIVE"|"DELETING"|"UPDATING"|string;
1320 export type IndexName = string;
1321 export type IndexStatus = "CREATING"|"UPDATING"|"DELETING"|"ACTIVE"|string;
1322 export type Integer = number;
1323 export type IntegerObject = number;
1324 export type ItemCollectionKeyAttributeMap = {[key: string]: AttributeValue};
1325 export interface ItemCollectionMetrics {
1326 /**
1327 * The partition key value of the item collection. This value is the same as the partition key value of the item.
1328 */
1329 ItemCollectionKey?: ItemCollectionKeyAttributeMap;
1330 /**
1331 * An estimate of item collection size, in gigabytes. This value is a two-element array containing a lower bound and an upper bound for the estimate. The estimate includes the size of all the items in the table, plus the size of all attributes projected into all of the local secondary indexes on that table. Use this estimate to measure whether a local secondary index is approaching its size limit. The estimate is subject to change over time; therefore, do not rely on the precision or accuracy of the estimate.
1332 */
1333 SizeEstimateRangeGB?: ItemCollectionSizeEstimateRange;
1334 }
1335 export type ItemCollectionMetricsMultiple = ItemCollectionMetrics[];
1336 export type ItemCollectionMetricsPerTable = {[key: string]: ItemCollectionMetricsMultiple};
1337 export type ItemCollectionSizeEstimateBound = number;
1338 export type ItemCollectionSizeEstimateRange = ItemCollectionSizeEstimateBound[];
1339 export type ItemCount = number;
1340 export type ItemList = AttributeMap[];
1341 export interface ItemResponse {
1342 /**
1343 * Map of attribute data consisting of the data type and attribute value.
1344 */
1345 Item?: AttributeMap;
1346 }
1347 export type ItemResponseList = ItemResponse[];
1348 export type KMSMasterKeyArn = string;
1349 export type KMSMasterKeyId = string;
1350 export type Key = {[key: string]: AttributeValue};
1351 export type KeyConditions = {[key: string]: Condition};
1352 export type KeyExpression = string;
1353 export type KeyList = Key[];
1354 export type KeySchema = KeySchemaElement[];
1355 export type KeySchemaAttributeName = string;
1356 export interface KeySchemaElement {
1357 /**
1358 * The name of a key attribute.
1359 */
1360 AttributeName: KeySchemaAttributeName;
1361 /**
1362 * The role that this key attribute will assume: HASH - partition key RANGE - sort key The partition key of an item is also known as its hash attribute. The term "hash attribute" derives from DynamoDB' usage of an internal hash function to evenly distribute data items across partitions, based on their partition key values. The sort key of an item is also known as its range attribute. The term "range attribute" derives from the way DynamoDB stores items with the same partition key physically close together, in sorted order by the sort key value.
1363 */
1364 KeyType: KeyType;
1365 }
1366 export type KeyType = "HASH"|"RANGE"|string;
1367 export interface KeysAndAttributes {
1368 /**
1369 * The primary key attribute values that define the items and the attributes associated with the items.
1370 */
1371 Keys: KeyList;
1372 /**
1373 * This is a legacy parameter. Use ProjectionExpression instead. For more information, see Legacy Conditional Parameters in the Amazon DynamoDB Developer Guide.
1374 */
1375 AttributesToGet?: AttributeNameList;
1376 /**
1377 * The consistency of a read operation. If set to true, then a strongly consistent read is used; otherwise, an eventually consistent read is used.
1378 */
1379 ConsistentRead?: ConsistentRead;
1380 /**
1381 * A string that identifies one or more attributes to retrieve from the table. These attributes can include scalars, sets, or elements of a JSON document. The attributes in the ProjectionExpression must be separated by commas. If no attribute names are specified, then all attributes will be returned. If any of the requested attributes are not found, they will not appear in the result. For more information, see Accessing Item Attributes in the Amazon DynamoDB Developer Guide.
1382 */
1383 ProjectionExpression?: ProjectionExpression;
1384 /**
1385 * One or more substitution tokens for attribute names in an expression. The following are some use cases for using ExpressionAttributeNames: To access an attribute whose name conflicts with a DynamoDB reserved word. To create a placeholder for repeating occurrences of an attribute name in an expression. To prevent special characters in an attribute name from being misinterpreted in an expression. Use the # character in an expression to dereference an attribute name. For example, consider the following attribute name: Percentile The name of this attribute conflicts with a reserved word, so it cannot be used directly in an expression. (For the complete list of reserved words, see Reserved Words in the Amazon DynamoDB Developer Guide). To work around this, you could specify the following for ExpressionAttributeNames: {"#P":"Percentile"} You could then use this substitution in an expression, as in this example: #P = :val Tokens that begin with the : character are expression attribute values, which are placeholders for the actual value at runtime. For more information on expression attribute names, see Accessing Item Attributes in the Amazon DynamoDB Developer Guide.
1386 */
1387 ExpressionAttributeNames?: ExpressionAttributeNameMap;
1388 }
1389 export type ListAttributeValue = AttributeValue[];
1390 export interface ListBackupsInput {
1391 /**
1392 * The backups from the table specified by TableName are listed.
1393 */
1394 TableName?: TableName;
1395 /**
1396 * Maximum number of backups to return at once.
1397 */
1398 Limit?: BackupsInputLimit;
1399 /**
1400 * Only backups created after this time are listed. TimeRangeLowerBound is inclusive.
1401 */
1402 TimeRangeLowerBound?: TimeRangeLowerBound;
1403 /**
1404 * Only backups created before this time are listed. TimeRangeUpperBound is exclusive.
1405 */
1406 TimeRangeUpperBound?: TimeRangeUpperBound;
1407 /**
1408 * LastEvaluatedBackupArn is the Amazon Resource Name (ARN) of the backup last evaluated when the current page of results was returned, inclusive of the current page of results. This value may be specified as the ExclusiveStartBackupArn of a new ListBackups operation in order to fetch the next page of results.
1409 */
1410 ExclusiveStartBackupArn?: BackupArn;
1411 /**
1412 * The backups from the table specified by BackupType are listed. Where BackupType can be: USER - On-demand backup created by you. SYSTEM - On-demand backup automatically created by DynamoDB. ALL - All types of on-demand backups (USER and SYSTEM).
1413 */
1414 BackupType?: BackupTypeFilter;
1415 }
1416 export interface ListBackupsOutput {
1417 /**
1418 * List of BackupSummary objects.
1419 */
1420 BackupSummaries?: BackupSummaries;
1421 /**
1422 * The ARN of the backup last evaluated when the current page of results was returned, inclusive of the current page of results. This value may be specified as the ExclusiveStartBackupArn of a new ListBackups operation in order to fetch the next page of results. If LastEvaluatedBackupArn is empty, then the last page of results has been processed and there are no more results to be retrieved. If LastEvaluatedBackupArn is not empty, this may or may not indicate that there is more data to be returned. All results are guaranteed to have been returned if and only if no value for LastEvaluatedBackupArn is returned.
1423 */
1424 LastEvaluatedBackupArn?: BackupArn;
1425 }
1426 export interface ListGlobalTablesInput {
1427 /**
1428 * The first global table name that this operation will evaluate.
1429 */
1430 ExclusiveStartGlobalTableName?: TableName;
1431 /**
1432 * The maximum number of table names to return.
1433 */
1434 Limit?: PositiveIntegerObject;
1435 /**
1436 * Lists the global tables in a specific Region.
1437 */
1438 RegionName?: RegionName;
1439 }
1440 export interface ListGlobalTablesOutput {
1441 /**
1442 * List of global table names.
1443 */
1444 GlobalTables?: GlobalTableList;
1445 /**
1446 * Last evaluated global table name.
1447 */
1448 LastEvaluatedGlobalTableName?: TableName;
1449 }
1450 export interface ListTablesInput {
1451 /**
1452 * The first table name that this operation will evaluate. Use the value that was returned for LastEvaluatedTableName in a previous operation, so that you can obtain the next page of results.
1453 */
1454 ExclusiveStartTableName?: TableName;
1455 /**
1456 * A maximum number of table names to return. If this parameter is not specified, the limit is 100.
1457 */
1458 Limit?: ListTablesInputLimit;
1459 }
1460 export type ListTablesInputLimit = number;
1461 export interface ListTablesOutput {
1462 /**
1463 * The names of the tables associated with the current account at the current endpoint. The maximum size of this array is 100. If LastEvaluatedTableName also appears in the output, you can use this value as the ExclusiveStartTableName parameter in a subsequent ListTables request and obtain the next page of results.
1464 */
1465 TableNames?: TableNameList;
1466 /**
1467 * The name of the last table in the current page of results. Use this value as the ExclusiveStartTableName in a new request to obtain the next page of results, until all the table names are returned. If you do not receive a LastEvaluatedTableName value in the response, this means that there are no more table names to be retrieved.
1468 */
1469 LastEvaluatedTableName?: TableName;
1470 }
1471 export interface ListTagsOfResourceInput {
1472 /**
1473 * The Amazon DynamoDB resource with tags to be listed. This value is an Amazon Resource Name (ARN).
1474 */
1475 ResourceArn: ResourceArnString;
1476 /**
1477 * An optional string that, if supplied, must be copied from the output of a previous call to ListTagOfResource. When provided in this manner, this API fetches the next page of results.
1478 */
1479 NextToken?: NextTokenString;
1480 }
1481 export interface ListTagsOfResourceOutput {
1482 /**
1483 * The tags currently associated with the Amazon DynamoDB resource.
1484 */
1485 Tags?: TagList;
1486 /**
1487 * If this value is returned, there are additional results to be displayed. To retrieve them, call ListTagsOfResource again, with NextToken set to this value.
1488 */
1489 NextToken?: NextTokenString;
1490 }
1491 export interface LocalSecondaryIndex {
1492 /**
1493 * The name of the local secondary index. The name must be unique among all other indexes on this table.
1494 */
1495 IndexName: IndexName;
1496 /**
1497 * The complete key schema for the local secondary index, consisting of one or more pairs of attribute names and key types: HASH - partition key RANGE - sort key The partition key of an item is also known as its hash attribute. The term "hash attribute" derives from DynamoDB' usage of an internal hash function to evenly distribute data items across partitions, based on their partition key values. The sort key of an item is also known as its range attribute. The term "range attribute" derives from the way DynamoDB stores items with the same partition key physically close together, in sorted order by the sort key value.
1498 */
1499 KeySchema: KeySchema;
1500 /**
1501 * Represents attributes that are copied (projected) from the table into the local secondary index. These are in addition to the primary key attributes and index key attributes, which are automatically projected.
1502 */
1503 Projection: Projection;
1504 }
1505 export interface LocalSecondaryIndexDescription {
1506 /**
1507 * Represents the name of the local secondary index.
1508 */
1509 IndexName?: IndexName;
1510 /**
1511 * The complete key schema for the local secondary index, consisting of one or more pairs of attribute names and key types: HASH - partition key RANGE - sort key The partition key of an item is also known as its hash attribute. The term "hash attribute" derives from DynamoDB' usage of an internal hash function to evenly distribute data items across partitions, based on their partition key values. The sort key of an item is also known as its range attribute. The term "range attribute" derives from the way DynamoDB stores items with the same partition key physically close together, in sorted order by the sort key value.
1512 */
1513 KeySchema?: KeySchema;
1514 /**
1515 * Represents attributes that are copied (projected) from the table into the global secondary index. These are in addition to the primary key attributes and index key attributes, which are automatically projected.
1516 */
1517 Projection?: Projection;
1518 /**
1519 * The total size of the specified index, in bytes. DynamoDB updates this value approximately every six hours. Recent changes might not be reflected in this value.
1520 */
1521 IndexSizeBytes?: Long;
1522 /**
1523 * The number of items in the specified index. DynamoDB updates this value approximately every six hours. Recent changes might not be reflected in this value.
1524 */
1525 ItemCount?: Long;
1526 /**
1527 * The Amazon Resource Name (ARN) that uniquely identifies the index.
1528 */
1529 IndexArn?: String;
1530 }
1531 export type LocalSecondaryIndexDescriptionList = LocalSecondaryIndexDescription[];
1532 export interface LocalSecondaryIndexInfo {
1533 /**
1534 * Represents the name of the local secondary index.
1535 */
1536 IndexName?: IndexName;
1537 /**
1538 * The complete key schema for a local secondary index, which consists of one or more pairs of attribute names and key types: HASH - partition key RANGE - sort key The partition key of an item is also known as its hash attribute. The term "hash attribute" derives from DynamoDB' usage of an internal hash function to evenly distribute data items across partitions, based on their partition key values. The sort key of an item is also known as its range attribute. The term "range attribute" derives from the way DynamoDB stores items with the same partition key physically close together, in sorted order by the sort key value.
1539 */
1540 KeySchema?: KeySchema;
1541 /**
1542 * Represents attributes that are copied (projected) from the table into the global secondary index. These are in addition to the primary key attributes and index key attributes, which are automatically projected.
1543 */
1544 Projection?: Projection;
1545 }
1546 export type LocalSecondaryIndexList = LocalSecondaryIndex[];
1547 export type LocalSecondaryIndexes = LocalSecondaryIndexInfo[];
1548 export type Long = number;
1549 export type MapAttributeValue = {[key: string]: AttributeValue};
1550 export type NextTokenString = string;
1551 export type NonKeyAttributeName = string;
1552 export type NonKeyAttributeNameList = NonKeyAttributeName[];
1553 export type NonNegativeLongObject = number;
1554 export type NullAttributeValue = boolean;
1555 export type NumberAttributeValue = string;
1556 export type NumberSetAttributeValue = NumberAttributeValue[];
1557 export interface PointInTimeRecoveryDescription {
1558 /**
1559 * The current state of point in time recovery: ENABLING - Point in time recovery is being enabled. ENABLED - Point in time recovery is enabled. DISABLED - Point in time recovery is disabled.
1560 */
1561 PointInTimeRecoveryStatus?: PointInTimeRecoveryStatus;
1562 /**
1563 * Specifies the earliest point in time you can restore your table to. It You can restore your table to any point in time during the last 35 days.
1564 */
1565 EarliestRestorableDateTime?: _Date;
1566 /**
1567 * LatestRestorableDateTime is typically 5 minutes before the current time.
1568 */
1569 LatestRestorableDateTime?: _Date;
1570 }
1571 export interface PointInTimeRecoverySpecification {
1572 /**
1573 * Indicates whether point in time recovery is enabled (true) or disabled (false) on the table.
1574 */
1575 PointInTimeRecoveryEnabled: BooleanObject;
1576 }
1577 export type PointInTimeRecoveryStatus = "ENABLED"|"DISABLED"|string;
1578 export type PositiveIntegerObject = number;
1579 export type PositiveLongObject = number;
1580 export interface Projection {
1581 /**
1582 * The set of attributes that are projected into the index: KEYS_ONLY - Only the index and primary keys are projected into the index. INCLUDE - Only the specified table attributes are projected into the index. The list of projected attributes are in NonKeyAttributes. ALL - All of the table attributes are projected into the index.
1583 */
1584 ProjectionType?: ProjectionType;
1585 /**
1586 * Represents the non-key attribute names which will be projected into the index. For local secondary indexes, the total count of NonKeyAttributes summed across all of the local secondary indexes, must not exceed 20. If you project the same attribute into two different indexes, this counts as two distinct attributes when determining the total.
1587 */
1588 NonKeyAttributes?: NonKeyAttributeNameList;
1589 }
1590 export type ProjectionExpression = string;
1591 export type ProjectionType = "ALL"|"KEYS_ONLY"|"INCLUDE"|string;
1592 export interface ProvisionedThroughput {
1593 /**
1594 * The maximum number of strongly consistent reads consumed per second before DynamoDB returns a ThrottlingException. For more information, see Specifying Read and Write Requirements in the Amazon DynamoDB Developer Guide. If read/write capacity mode is PAY_PER_REQUEST the value is set to 0.
1595 */
1596 ReadCapacityUnits: PositiveLongObject;
1597 /**
1598 * The maximum number of writes consumed per second before DynamoDB returns a ThrottlingException. For more information, see Specifying Read and Write Requirements in the Amazon DynamoDB Developer Guide. If read/write capacity mode is PAY_PER_REQUEST the value is set to 0.
1599 */
1600 WriteCapacityUnits: PositiveLongObject;
1601 }
1602 export interface ProvisionedThroughputDescription {
1603 /**
1604 * The date and time of the last provisioned throughput increase for this table.
1605 */
1606 LastIncreaseDateTime?: _Date;
1607 /**
1608 * The date and time of the last provisioned throughput decrease for this table.
1609 */
1610 LastDecreaseDateTime?: _Date;
1611 /**
1612 * The number of provisioned throughput decreases for this table during this UTC calendar day. For current maximums on provisioned throughput decreases, see Limits in the Amazon DynamoDB Developer Guide.
1613 */
1614 NumberOfDecreasesToday?: PositiveLongObject;
1615 /**
1616 * The maximum number of strongly consistent reads consumed per second before DynamoDB returns a ThrottlingException. Eventually consistent reads require less effort than strongly consistent reads, so a setting of 50 ReadCapacityUnits per second provides 100 eventually consistent ReadCapacityUnits per second.
1617 */
1618 ReadCapacityUnits?: NonNegativeLongObject;
1619 /**
1620 * The maximum number of writes consumed per second before DynamoDB returns a ThrottlingException.
1621 */
1622 WriteCapacityUnits?: NonNegativeLongObject;
1623 }
1624 export interface Put {
1625 /**
1626 * A map of attribute name to attribute values, representing the primary key of the item to be written by PutItem. All of the table's primary key attributes must be specified, and their data types must match those of the table's key schema. If any attributes are present in the item that are part of an index key schema for the table, their types must match the index key schema.
1627 */
1628 Item: PutItemInputAttributeMap;
1629 /**
1630 * Name of the table in which to write the item.
1631 */
1632 TableName: TableName;
1633 /**
1634 * A condition that must be satisfied in order for a conditional update to succeed.
1635 */
1636 ConditionExpression?: ConditionExpression;
1637 /**
1638 * One or more substitution tokens for attribute names in an expression.
1639 */
1640 ExpressionAttributeNames?: ExpressionAttributeNameMap;
1641 /**
1642 * One or more values that can be substituted in an expression.
1643 */
1644 ExpressionAttributeValues?: ExpressionAttributeValueMap;
1645 /**
1646 * Use ReturnValuesOnConditionCheckFailure to get the item attributes if the Put condition fails. For ReturnValuesOnConditionCheckFailure, the valid values are: NONE and ALL_OLD.
1647 */
1648 ReturnValuesOnConditionCheckFailure?: ReturnValuesOnConditionCheckFailure;
1649 }
1650 export interface PutItemInput {
1651 /**
1652 * The name of the table to contain the item.
1653 */
1654 TableName: TableName;
1655 /**
1656 * A map of attribute name/value pairs, one for each attribute. Only the primary key attributes are required; you can optionally provide other attribute name-value pairs for the item. You must provide all of the attributes for the primary key. For example, with a simple primary key, you only need to provide a value for the partition key. For a composite primary key, you must provide both values for both the partition key and the sort key. If you specify any attributes that are part of an index key, then the data types for those attributes must match those of the schema in the table's attribute definition. For more information about primary keys, see Primary Key in the Amazon DynamoDB Developer Guide. Each element in the Item map is an AttributeValue object.
1657 */
1658 Item: PutItemInputAttributeMap;
1659 /**
1660 * This is a legacy parameter. Use ConditionExpression instead. For more information, see Expected in the Amazon DynamoDB Developer Guide.
1661 */
1662 Expected?: ExpectedAttributeMap;
1663 /**
1664 * Use ReturnValues if you want to get the item attributes as they appeared before they were updated with the PutItem request. For PutItem, the valid values are: NONE - If ReturnValues is not specified, or if its value is NONE, then nothing is returned. (This setting is the default for ReturnValues.) ALL_OLD - If PutItem overwrote an attribute name-value pair, then the content of the old item is returned. The ReturnValues parameter is used by several DynamoDB operations; however, PutItem does not recognize any values other than NONE or ALL_OLD.
1665 */
1666 ReturnValues?: ReturnValue;
1667 ReturnConsumedCapacity?: ReturnConsumedCapacity;
1668 /**
1669 * Determines whether item collection metrics are returned. If set to SIZE, the response includes statistics about item collections, if any, that were modified during the operation are returned in the response. If set to NONE (the default), no statistics are returned.
1670 */
1671 ReturnItemCollectionMetrics?: ReturnItemCollectionMetrics;
1672 /**
1673 * This is a legacy parameter. Use ConditionExpression instead. For more information, see ConditionalOperator in the Amazon DynamoDB Developer Guide.
1674 */
1675 ConditionalOperator?: ConditionalOperator;
1676 /**
1677 * A condition that must be satisfied in order for a conditional PutItem operation to succeed. An expression can contain any of the following: Functions: attribute_exists | attribute_not_exists | attribute_type | contains | begins_with | size These function names are case-sensitive. Comparison operators: = | &lt;&gt; | &lt; | &gt; | &lt;= | &gt;= | BETWEEN | IN Logical operators: AND | OR | NOT For more information on condition expressions, see Condition Expressions in the Amazon DynamoDB Developer Guide.
1678 */
1679 ConditionExpression?: ConditionExpression;
1680 /**
1681 * One or more substitution tokens for attribute names in an expression. The following are some use cases for using ExpressionAttributeNames: To access an attribute whose name conflicts with a DynamoDB reserved word. To create a placeholder for repeating occurrences of an attribute name in an expression. To prevent special characters in an attribute name from being misinterpreted in an expression. Use the # character in an expression to dereference an attribute name. For example, consider the following attribute name: Percentile The name of this attribute conflicts with a reserved word, so it cannot be used directly in an expression. (For the complete list of reserved words, see Reserved Words in the Amazon DynamoDB Developer Guide). To work around this, you could specify the following for ExpressionAttributeNames: {"#P":"Percentile"} You could then use this substitution in an expression, as in this example: #P = :val Tokens that begin with the : character are expression attribute values, which are placeholders for the actual value at runtime. For more information on expression attribute names, see Specifying Item Attributes in the Amazon DynamoDB Developer Guide.
1682 */
1683 ExpressionAttributeNames?: ExpressionAttributeNameMap;
1684 /**
1685 * One or more values that can be substituted in an expression. Use the : (colon) character in an expression to dereference an attribute value. For example, suppose that you wanted to check whether the value of the ProductStatus attribute was one of the following: Available | Backordered | Discontinued You would first need to specify ExpressionAttributeValues as follows: { ":avail":{"S":"Available"}, ":back":{"S":"Backordered"}, ":disc":{"S":"Discontinued"} } You could then use these values in an expression, such as this: ProductStatus IN (:avail, :back, :disc) For more information on expression attribute values, see Condition Expressions in the Amazon DynamoDB Developer Guide.
1686 */
1687 ExpressionAttributeValues?: ExpressionAttributeValueMap;
1688 }
1689 export type PutItemInputAttributeMap = {[key: string]: AttributeValue};
1690 export interface PutItemOutput {
1691 /**
1692 * The attribute values as they appeared before the PutItem operation, but only if ReturnValues is specified as ALL_OLD in the request. Each element consists of an attribute name and an attribute value.
1693 */
1694 Attributes?: AttributeMap;
1695 /**
1696 * The capacity units consumed by the PutItem operation. The data returned includes the total provisioned throughput consumed, along with statistics for the table and any indexes involved in the operation. ConsumedCapacity is only returned if the ReturnConsumedCapacity parameter was specified. For more information, see Read/Write Capacity Mode in the Amazon DynamoDB Developer Guide.
1697 */
1698 ConsumedCapacity?: ConsumedCapacity;
1699 /**
1700 * Information about item collections, if any, that were affected by the PutItem operation. ItemCollectionMetrics is only returned if the ReturnItemCollectionMetrics parameter was specified. If the table does not have any local secondary indexes, this information is not returned in the response. Each ItemCollectionMetrics element consists of: ItemCollectionKey - The partition key value of the item collection. This is the same as the partition key value of the item itself. SizeEstimateRangeGB - An estimate of item collection size, in gigabytes. This value is a two-element array containing a lower bound and an upper bound for the estimate. The estimate includes the size of all the items in the table, plus the size of all attributes projected into all of the local secondary indexes on that table. Use this estimate to measure whether a local secondary index is approaching its size limit. The estimate is subject to change over time; therefore, do not rely on the precision or accuracy of the estimate.
1701 */
1702 ItemCollectionMetrics?: ItemCollectionMetrics;
1703 }
1704 export interface PutRequest {
1705 /**
1706 * A map of attribute name to attribute values, representing the primary key of an item to be processed by PutItem. All of the table's primary key attributes must be specified, and their data types must match those of the table's key schema. If any attributes are present in the item which are part of an index key schema for the table, their types must match the index key schema.
1707 */
1708 Item: PutItemInputAttributeMap;
1709 }
1710 export interface QueryInput {
1711 /**
1712 * The name of the table containing the requested items.
1713 */
1714 TableName: TableName;
1715 /**
1716 * The name of an index to query. This index can be any local secondary index or global secondary index on the table. Note that if you use the IndexName parameter, you must also provide TableName.
1717 */
1718 IndexName?: IndexName;
1719 /**
1720 * The attributes to be returned in the result. You can retrieve all item attributes, specific item attributes, the count of matching items, or in the case of an index, some or all of the attributes projected into the index. ALL_ATTRIBUTES - Returns all of the item attributes from the specified table or index. If you query a local secondary index, then for each matching item in the index, DynamoDB fetches the entire item from the parent table. If the index is configured to project all item attributes, then all of the data can be obtained from the local secondary index, and no fetching is required. ALL_PROJECTED_ATTRIBUTES - Allowed only when querying an index. Retrieves all attributes that have been projected into the index. If the index is configured to project all attributes, this return value is equivalent to specifying ALL_ATTRIBUTES. COUNT - Returns the number of matching items, rather than the matching items themselves. SPECIFIC_ATTRIBUTES - Returns only the attributes listed in AttributesToGet. This return value is equivalent to specifying AttributesToGet without specifying any value for Select. If you query or scan a local secondary index and request only attributes that are projected into that index, the operation will read only the index and not the table. If any of the requested attributes are not projected into the local secondary index, DynamoDB fetches each of these attributes from the parent table. This extra fetching incurs additional throughput cost and latency. If you query or scan a global secondary index, you can only request attributes that are projected into the index. Global secondary index queries cannot fetch attributes from the parent table. If neither Select nor AttributesToGet are specified, DynamoDB defaults to ALL_ATTRIBUTES when accessing a table, and ALL_PROJECTED_ATTRIBUTES when accessing an index. You cannot use both Select and AttributesToGet together in a single request, unless the value for Select is SPECIFIC_ATTRIBUTES. (This usage is equivalent to specifying AttributesToGet without any value for Select.) If you use the ProjectionExpression parameter, then the value for Select can only be SPECIFIC_ATTRIBUTES. Any other value for Select will return an error.
1721 */
1722 Select?: Select;
1723 /**
1724 * This is a legacy parameter. Use ProjectionExpression instead. For more information, see AttributesToGet in the Amazon DynamoDB Developer Guide.
1725 */
1726 AttributesToGet?: AttributeNameList;
1727 /**
1728 * The maximum number of items to evaluate (not necessarily the number of matching items). If DynamoDB processes the number of items up to the limit while processing the results, it stops the operation and returns the matching values up to that point, and a key in LastEvaluatedKey to apply in a subsequent operation, so that you can pick up where you left off. Also, if the processed dataset size exceeds 1 MB before DynamoDB reaches this limit, it stops the operation and returns the matching values up to the limit, and a key in LastEvaluatedKey to apply in a subsequent operation to continue the operation. For more information, see Query and Scan in the Amazon DynamoDB Developer Guide.
1729 */
1730 Limit?: PositiveIntegerObject;
1731 /**
1732 * Determines the read consistency model: If set to true, then the operation uses strongly consistent reads; otherwise, the operation uses eventually consistent reads. Strongly consistent reads are not supported on global secondary indexes. If you query a global secondary index with ConsistentRead set to true, you will receive a ValidationException.
1733 */
1734 ConsistentRead?: ConsistentRead;
1735 /**
1736 * This is a legacy parameter. Use KeyConditionExpression instead. For more information, see KeyConditions in the Amazon DynamoDB Developer Guide.
1737 */
1738 KeyConditions?: KeyConditions;
1739 /**
1740 * This is a legacy parameter. Use FilterExpression instead. For more information, see QueryFilter in the Amazon DynamoDB Developer Guide.
1741 */
1742 QueryFilter?: FilterConditionMap;
1743 /**
1744 * This is a legacy parameter. Use FilterExpression instead. For more information, see ConditionalOperator in the Amazon DynamoDB Developer Guide.
1745 */
1746 ConditionalOperator?: ConditionalOperator;
1747 /**
1748 * Specifies the order for index traversal: If true (default), the traversal is performed in ascending order; if false, the traversal is performed in descending order. Items with the same partition key value are stored in sorted order by sort key. If the sort key data type is Number, the results are stored in numeric order. For type String, the results are stored in order of UTF-8 bytes. For type Binary, DynamoDB treats each byte of the binary data as unsigned. If ScanIndexForward is true, DynamoDB returns the results in the order in which they are stored (by sort key value). This is the default behavior. If ScanIndexForward is false, DynamoDB reads the results in reverse order by sort key value, and then returns the results to the client.
1749 */
1750 ScanIndexForward?: BooleanObject;
1751 /**
1752 * The primary key of the first item that this operation will evaluate. Use the value that was returned for LastEvaluatedKey in the previous operation. The data type for ExclusiveStartKey must be String, Number, or Binary. No set data types are allowed.
1753 */
1754 ExclusiveStartKey?: Key;
1755 ReturnConsumedCapacity?: ReturnConsumedCapacity;
1756 /**
1757 * A string that identifies one or more attributes to retrieve from the table. These attributes can include scalars, sets, or elements of a JSON document. The attributes in the expression must be separated by commas. If no attribute names are specified, then all attributes will be returned. If any of the requested attributes are not found, they will not appear in the result. For more information, see Accessing Item Attributes in the Amazon DynamoDB Developer Guide.
1758 */
1759 ProjectionExpression?: ProjectionExpression;
1760 /**
1761 * A string that contains conditions that DynamoDB applies after the Query operation, but before the data is returned to you. Items that do not satisfy the FilterExpression criteria are not returned. A FilterExpression does not allow key attributes. You cannot define a filter expression based on a partition key or a sort key. A FilterExpression is applied after the items have already been read; the process of filtering does not consume any additional read capacity units. For more information, see Filter Expressions in the Amazon DynamoDB Developer Guide.
1762 */
1763 FilterExpression?: ConditionExpression;
1764 /**
1765 * The condition that specifies the key values for items to be retrieved by the Query action. The condition must perform an equality test on a single partition key value. The condition can optionally perform one of several comparison tests on a single sort key value. This allows Query to retrieve one item with a given partition key value and sort key value, or several items that have the same partition key value but different sort key values. The partition key equality test is required, and must be specified in the following format: partitionKeyName = :partitionkeyval If you also want to provide a condition for the sort key, it must be combined using AND with the condition for the sort key. Following is an example, using the = comparison operator for the sort key: partitionKeyName = :partitionkeyval AND sortKeyName = :sortkeyval Valid comparisons for the sort key condition are as follows: sortKeyName = :sortkeyval - true if the sort key value is equal to :sortkeyval. sortKeyName &lt; :sortkeyval - true if the sort key value is less than :sortkeyval. sortKeyName &lt;= :sortkeyval - true if the sort key value is less than or equal to :sortkeyval. sortKeyName &gt; :sortkeyval - true if the sort key value is greater than :sortkeyval. sortKeyName &gt;= :sortkeyval - true if the sort key value is greater than or equal to :sortkeyval. sortKeyName BETWEEN :sortkeyval1 AND :sortkeyval2 - true if the sort key value is greater than or equal to :sortkeyval1, and less than or equal to :sortkeyval2. begins_with ( sortKeyName, :sortkeyval ) - true if the sort key value begins with a particular operand. (You cannot use this function with a sort key that is of type Number.) Note that the function name begins_with is case-sensitive. Use the ExpressionAttributeValues parameter to replace tokens such as :partitionval and :sortval with actual values at runtime. You can optionally use the ExpressionAttributeNames parameter to replace the names of the partition key and sort key with placeholder tokens. This option might be necessary if an attribute name conflicts with a DynamoDB reserved word. For example, the following KeyConditionExpression parameter causes an error because Size is a reserved word: Size = :myval To work around this, define a placeholder (such a #S) to represent the attribute name Size. KeyConditionExpression then is as follows: #S = :myval For a list of reserved words, see Reserved Words in the Amazon DynamoDB Developer Guide. For more information on ExpressionAttributeNames and ExpressionAttributeValues, see Using Placeholders for Attribute Names and Values in the Amazon DynamoDB Developer Guide.
1766 */
1767 KeyConditionExpression?: KeyExpression;
1768 /**
1769 * One or more substitution tokens for attribute names in an expression. The following are some use cases for using ExpressionAttributeNames: To access an attribute whose name conflicts with a DynamoDB reserved word. To create a placeholder for repeating occurrences of an attribute name in an expression. To prevent special characters in an attribute name from being misinterpreted in an expression. Use the # character in an expression to dereference an attribute name. For example, consider the following attribute name: Percentile The name of this attribute conflicts with a reserved word, so it cannot be used directly in an expression. (For the complete list of reserved words, see Reserved Words in the Amazon DynamoDB Developer Guide). To work around this, you could specify the following for ExpressionAttributeNames: {"#P":"Percentile"} You could then use this substitution in an expression, as in this example: #P = :val Tokens that begin with the : character are expression attribute values, which are placeholders for the actual value at runtime. For more information on expression attribute names, see Specifying Item Attributes in the Amazon DynamoDB Developer Guide.
1770 */
1771 ExpressionAttributeNames?: ExpressionAttributeNameMap;
1772 /**
1773 * One or more values that can be substituted in an expression. Use the : (colon) character in an expression to dereference an attribute value. For example, suppose that you wanted to check whether the value of the ProductStatus attribute was one of the following: Available | Backordered | Discontinued You would first need to specify ExpressionAttributeValues as follows: { ":avail":{"S":"Available"}, ":back":{"S":"Backordered"}, ":disc":{"S":"Discontinued"} } You could then use these values in an expression, such as this: ProductStatus IN (:avail, :back, :disc) For more information on expression attribute values, see Specifying Conditions in the Amazon DynamoDB Developer Guide.
1774 */
1775 ExpressionAttributeValues?: ExpressionAttributeValueMap;
1776 }
1777 export interface QueryOutput {
1778 /**
1779 * An array of item attributes that match the query criteria. Each element in this array consists of an attribute name and the value for that attribute.
1780 */
1781 Items?: ItemList;
1782 /**
1783 * The number of items in the response. If you used a QueryFilter in the request, then Count is the number of items returned after the filter was applied, and ScannedCount is the number of matching items before the filter was applied. If you did not use a filter in the request, then Count and ScannedCount are the same.
1784 */
1785 Count?: Integer;
1786 /**
1787 * The number of items evaluated, before any QueryFilter is applied. A high ScannedCount value with few, or no, Count results indicates an inefficient Query operation. For more information, see Count and ScannedCount in the Amazon DynamoDB Developer Guide. If you did not use a filter in the request, then ScannedCount is the same as Count.
1788 */
1789 ScannedCount?: Integer;
1790 /**
1791 * The primary key of the item where the operation stopped, inclusive of the previous result set. Use this value to start a new operation, excluding this value in the new request. If LastEvaluatedKey is empty, then the "last page" of results has been processed and there is no more data to be retrieved. If LastEvaluatedKey is not empty, it does not necessarily mean that there is more data in the result set. The only way to know when you have reached the end of the result set is when LastEvaluatedKey is empty.
1792 */
1793 LastEvaluatedKey?: Key;
1794 /**
1795 * The capacity units consumed by the Query operation. The data returned includes the total provisioned throughput consumed, along with statistics for the table and any indexes involved in the operation. ConsumedCapacity is only returned if the ReturnConsumedCapacity parameter was specified. For more information, see Provisioned Throughput in the Amazon DynamoDB Developer Guide.
1796 */
1797 ConsumedCapacity?: ConsumedCapacity;
1798 }
1799 export type RegionName = string;
1800 export interface Replica {
1801 /**
1802 * The region where the replica needs to be created.
1803 */
1804 RegionName?: RegionName;
1805 }
1806 export interface ReplicaDescription {
1807 /**
1808 * The name of the region.
1809 */
1810 RegionName?: RegionName;
1811 }
1812 export type ReplicaDescriptionList = ReplicaDescription[];
1813 export interface ReplicaGlobalSecondaryIndexSettingsDescription {
1814 /**
1815 * The name of the global secondary index. The name must be unique among all other indexes on this table.
1816 */
1817 IndexName: IndexName;
1818 /**
1819 * The current status of the global secondary index: CREATING - The global secondary index is being created. UPDATING - The global secondary index is being updated. DELETING - The global secondary index is being deleted. ACTIVE - The global secondary index is ready for use.
1820 */
1821 IndexStatus?: IndexStatus;
1822 /**
1823 * The maximum number of strongly consistent reads consumed per second before DynamoDB returns a ThrottlingException.
1824 */
1825 ProvisionedReadCapacityUnits?: PositiveLongObject;
1826 /**
1827 * Autoscaling settings for a global secondary index replica's read capacity units.
1828 */
1829 ProvisionedReadCapacityAutoScalingSettings?: AutoScalingSettingsDescription;
1830 /**
1831 * The maximum number of writes consumed per second before DynamoDB returns a ThrottlingException.
1832 */
1833 ProvisionedWriteCapacityUnits?: PositiveLongObject;
1834 /**
1835 * AutoScaling settings for a global secondary index replica's write capacity units.
1836 */
1837 ProvisionedWriteCapacityAutoScalingSettings?: AutoScalingSettingsDescription;
1838 }
1839 export type ReplicaGlobalSecondaryIndexSettingsDescriptionList = ReplicaGlobalSecondaryIndexSettingsDescription[];
1840 export interface ReplicaGlobalSecondaryIndexSettingsUpdate {
1841 /**
1842 * The name of the global secondary index. The name must be unique among all other indexes on this table.
1843 */
1844 IndexName: IndexName;
1845 /**
1846 * The maximum number of strongly consistent reads consumed per second before DynamoDB returns a ThrottlingException.
1847 */
1848 ProvisionedReadCapacityUnits?: PositiveLongObject;
1849 /**
1850 * Autoscaling settings for managing a global secondary index replica's read capacity units.
1851 */
1852 ProvisionedReadCapacityAutoScalingSettingsUpdate?: AutoScalingSettingsUpdate;
1853 }
1854 export type ReplicaGlobalSecondaryIndexSettingsUpdateList = ReplicaGlobalSecondaryIndexSettingsUpdate[];
1855 export type ReplicaList = Replica[];
1856 export interface ReplicaSettingsDescription {
1857 /**
1858 * The region name of the replica.
1859 */
1860 RegionName: RegionName;
1861 /**
1862 * The current state of the region: CREATING - The region is being created. UPDATING - The region is being updated. DELETING - The region is being deleted. ACTIVE - The region is ready for use.
1863 */
1864 ReplicaStatus?: ReplicaStatus;
1865 /**
1866 * The read/write capacity mode of the replica.
1867 */
1868 ReplicaBillingModeSummary?: BillingModeSummary;
1869 /**
1870 * The maximum number of strongly consistent reads consumed per second before DynamoDB returns a ThrottlingException. For more information, see Specifying Read and Write Requirements in the Amazon DynamoDB Developer Guide.
1871 */
1872 ReplicaProvisionedReadCapacityUnits?: NonNegativeLongObject;
1873 /**
1874 * Autoscaling settings for a global table replica's read capacity units.
1875 */
1876 ReplicaProvisionedReadCapacityAutoScalingSettings?: AutoScalingSettingsDescription;
1877 /**
1878 * The maximum number of writes consumed per second before DynamoDB returns a ThrottlingException. For more information, see Specifying Read and Write Requirements in the Amazon DynamoDB Developer Guide.
1879 */
1880 ReplicaProvisionedWriteCapacityUnits?: NonNegativeLongObject;
1881 /**
1882 * AutoScaling settings for a global table replica's write capacity units.
1883 */
1884 ReplicaProvisionedWriteCapacityAutoScalingSettings?: AutoScalingSettingsDescription;
1885 /**
1886 * Replica global secondary index settings for the global table.
1887 */
1888 ReplicaGlobalSecondaryIndexSettings?: ReplicaGlobalSecondaryIndexSettingsDescriptionList;
1889 }
1890 export type ReplicaSettingsDescriptionList = ReplicaSettingsDescription[];
1891 export interface ReplicaSettingsUpdate {
1892 /**
1893 * The region of the replica to be added.
1894 */
1895 RegionName: RegionName;
1896 /**
1897 * The maximum number of strongly consistent reads consumed per second before DynamoDB returns a ThrottlingException. For more information, see Specifying Read and Write Requirements in the Amazon DynamoDB Developer Guide.
1898 */
1899 ReplicaProvisionedReadCapacityUnits?: PositiveLongObject;
1900 /**
1901 * Autoscaling settings for managing a global table replica's read capacity units.
1902 */
1903 ReplicaProvisionedReadCapacityAutoScalingSettingsUpdate?: AutoScalingSettingsUpdate;
1904 /**
1905 * Represents the settings of a global secondary index for a global table that will be modified.
1906 */
1907 ReplicaGlobalSecondaryIndexSettingsUpdate?: ReplicaGlobalSecondaryIndexSettingsUpdateList;
1908 }
1909 export type ReplicaSettingsUpdateList = ReplicaSettingsUpdate[];
1910 export type ReplicaStatus = "CREATING"|"UPDATING"|"DELETING"|"ACTIVE"|string;
1911 export interface ReplicaUpdate {
1912 /**
1913 * The parameters required for creating a replica on an existing global table.
1914 */
1915 Create?: CreateReplicaAction;
1916 /**
1917 * The name of the existing replica to be removed.
1918 */
1919 Delete?: DeleteReplicaAction;
1920 }
1921 export type ReplicaUpdateList = ReplicaUpdate[];
1922 export type ResourceArnString = string;
1923 export type RestoreInProgress = boolean;
1924 export interface RestoreSummary {
1925 /**
1926 * ARN of the backup from which the table was restored.
1927 */
1928 SourceBackupArn?: BackupArn;
1929 /**
1930 * ARN of the source table of the backup that is being restored.
1931 */
1932 SourceTableArn?: TableArn;
1933 /**
1934 * Point in time or source backup time.
1935 */
1936 RestoreDateTime: _Date;
1937 /**
1938 * Indicates if a restore is in progress or not.
1939 */
1940 RestoreInProgress: RestoreInProgress;
1941 }
1942 export interface RestoreTableFromBackupInput {
1943 /**
1944 * The name of the new table to which the backup must be restored.
1945 */
1946 TargetTableName: TableName;
1947 /**
1948 * The Amazon Resource Name (ARN) associated with the backup.
1949 */
1950 BackupArn: BackupArn;
1951 }
1952 export interface RestoreTableFromBackupOutput {
1953 /**
1954 * The description of the table created from an existing backup.
1955 */
1956 TableDescription?: TableDescription;
1957 }
1958 export interface RestoreTableToPointInTimeInput {
1959 /**
1960 * Name of the source table that is being restored.
1961 */
1962 SourceTableName: TableName;
1963 /**
1964 * The name of the new table to which it must be restored to.
1965 */
1966 TargetTableName: TableName;
1967 /**
1968 * Restore the table to the latest possible time. LatestRestorableDateTime is typically 5 minutes before the current time.
1969 */
1970 UseLatestRestorableTime?: BooleanObject;
1971 /**
1972 * Time in the past to restore the table to.
1973 */
1974 RestoreDateTime?: _Date;
1975 }
1976 export interface RestoreTableToPointInTimeOutput {
1977 /**
1978 * Represents the properties of a table.
1979 */
1980 TableDescription?: TableDescription;
1981 }
1982 export type ReturnConsumedCapacity = "INDEXES"|"TOTAL"|"NONE"|string;
1983 export type ReturnItemCollectionMetrics = "SIZE"|"NONE"|string;
1984 export type ReturnValue = "NONE"|"ALL_OLD"|"UPDATED_OLD"|"ALL_NEW"|"UPDATED_NEW"|string;
1985 export type ReturnValuesOnConditionCheckFailure = "ALL_OLD"|"NONE"|string;
1986 export interface SSEDescription {
1987 /**
1988 * Represents the current state of server-side encryption. The only supported values are: ENABLED - Server-side encryption is enabled. UPDATING - Server-side encryption is being updated.
1989 */
1990 Status?: SSEStatus;
1991 /**
1992 * Server-side encryption type. The only supported value is: KMS - Server-side encryption which uses AWS Key Management Service. Key is stored in your account and is managed by AWS KMS (KMS charges apply).
1993 */
1994 SSEType?: SSEType;
1995 /**
1996 * The KMS customer master key (CMK) ARN used for the KMS encryption.
1997 */
1998 KMSMasterKeyArn?: KMSMasterKeyArn;
1999 }
2000 export type SSEEnabled = boolean;
2001 export interface SSESpecification {
2002 /**
2003 * Indicates whether server-side encryption is done using an AWS managed CMK or an AWS owned CMK. If enabled (true), server-side encryption type is set to KMS and an AWS managed CMK is used (AWS KMS charges apply). If disabled (false) or not specified, server-side encryption is set to AWS owned CMK.
2004 */
2005 Enabled?: SSEEnabled;
2006 /**
2007 * Server-side encryption type. The only supported value is: KMS - Server-side encryption which uses AWS Key Management Service. Key is stored in your account and is managed by AWS KMS (KMS charges apply).
2008 */
2009 SSEType?: SSEType;
2010 /**
2011 * The KMS Customer Master Key (CMK) which should be used for the KMS encryption. To specify a CMK, use its key ID, Amazon Resource Name (ARN), alias name, or alias ARN. Note that you should only provide this parameter if the key is different from the default DynamoDB Customer Master Key alias/aws/dynamodb.
2012 */
2013 KMSMasterKeyId?: KMSMasterKeyId;
2014 }
2015 export type SSEStatus = "ENABLING"|"ENABLED"|"DISABLING"|"DISABLED"|"UPDATING"|string;
2016 export type SSEType = "AES256"|"KMS"|string;
2017 export type ScalarAttributeType = "S"|"N"|"B"|string;
2018 export interface ScanInput {
2019 /**
2020 * The name of the table containing the requested items; or, if you provide IndexName, the name of the table to which that index belongs.
2021 */
2022 TableName: TableName;
2023 /**
2024 * The name of a secondary index to scan. This index can be any local secondary index or global secondary index. Note that if you use the IndexName parameter, you must also provide TableName.
2025 */
2026 IndexName?: IndexName;
2027 /**
2028 * This is a legacy parameter. Use ProjectionExpression instead. For more information, see AttributesToGet in the Amazon DynamoDB Developer Guide.
2029 */
2030 AttributesToGet?: AttributeNameList;
2031 /**
2032 * The maximum number of items to evaluate (not necessarily the number of matching items). If DynamoDB processes the number of items up to the limit while processing the results, it stops the operation and returns the matching values up to that point, and a key in LastEvaluatedKey to apply in a subsequent operation, so that you can pick up where you left off. Also, if the processed dataset size exceeds 1 MB before DynamoDB reaches this limit, it stops the operation and returns the matching values up to the limit, and a key in LastEvaluatedKey to apply in a subsequent operation to continue the operation. For more information, see Working with Queries in the Amazon DynamoDB Developer Guide.
2033 */
2034 Limit?: PositiveIntegerObject;
2035 /**
2036 * The attributes to be returned in the result. You can retrieve all item attributes, specific item attributes, the count of matching items, or in the case of an index, some or all of the attributes projected into the index. ALL_ATTRIBUTES - Returns all of the item attributes from the specified table or index. If you query a local secondary index, then for each matching item in the index, DynamoDB fetches the entire item from the parent table. If the index is configured to project all item attributes, then all of the data can be obtained from the local secondary index, and no fetching is required. ALL_PROJECTED_ATTRIBUTES - Allowed only when querying an index. Retrieves all attributes that have been projected into the index. If the index is configured to project all attributes, this return value is equivalent to specifying ALL_ATTRIBUTES. COUNT - Returns the number of matching items, rather than the matching items themselves. SPECIFIC_ATTRIBUTES - Returns only the attributes listed in AttributesToGet. This return value is equivalent to specifying AttributesToGet without specifying any value for Select. If you query or scan a local secondary index and request only attributes that are projected into that index, the operation reads only the index and not the table. If any of the requested attributes are not projected into the local secondary index, DynamoDB fetches each of these attributes from the parent table. This extra fetching incurs additional throughput cost and latency. If you query or scan a global secondary index, you can only request attributes that are projected into the index. Global secondary index queries cannot fetch attributes from the parent table. If neither Select nor AttributesToGet are specified, DynamoDB defaults to ALL_ATTRIBUTES when accessing a table, and ALL_PROJECTED_ATTRIBUTES when accessing an index. You cannot use both Select and AttributesToGet together in a single request, unless the value for Select is SPECIFIC_ATTRIBUTES. (This usage is equivalent to specifying AttributesToGet without any value for Select.) If you use the ProjectionExpression parameter, then the value for Select can only be SPECIFIC_ATTRIBUTES. Any other value for Select will return an error.
2037 */
2038 Select?: Select;
2039 /**
2040 * This is a legacy parameter. Use FilterExpression instead. For more information, see ScanFilter in the Amazon DynamoDB Developer Guide.
2041 */
2042 ScanFilter?: FilterConditionMap;
2043 /**
2044 * This is a legacy parameter. Use FilterExpression instead. For more information, see ConditionalOperator in the Amazon DynamoDB Developer Guide.
2045 */
2046 ConditionalOperator?: ConditionalOperator;
2047 /**
2048 * The primary key of the first item that this operation will evaluate. Use the value that was returned for LastEvaluatedKey in the previous operation. The data type for ExclusiveStartKey must be String, Number or Binary. No set data types are allowed. In a parallel scan, a Scan request that includes ExclusiveStartKey must specify the same segment whose previous Scan returned the corresponding value of LastEvaluatedKey.
2049 */
2050 ExclusiveStartKey?: Key;
2051 ReturnConsumedCapacity?: ReturnConsumedCapacity;
2052 /**
2053 * For a parallel Scan request, TotalSegments represents the total number of segments into which the Scan operation will be divided. The value of TotalSegments corresponds to the number of application workers that will perform the parallel scan. For example, if you want to use four application threads to scan a table or an index, specify a TotalSegments value of 4. The value for TotalSegments must be greater than or equal to 1, and less than or equal to 1000000. If you specify a TotalSegments value of 1, the Scan operation will be sequential rather than parallel. If you specify TotalSegments, you must also specify Segment.
2054 */
2055 TotalSegments?: ScanTotalSegments;
2056 /**
2057 * For a parallel Scan request, Segment identifies an individual segment to be scanned by an application worker. Segment IDs are zero-based, so the first segment is always 0. For example, if you want to use four application threads to scan a table or an index, then the first thread specifies a Segment value of 0, the second thread specifies 1, and so on. The value of LastEvaluatedKey returned from a parallel Scan request must be used as ExclusiveStartKey with the same segment ID in a subsequent Scan operation. The value for Segment must be greater than or equal to 0, and less than the value provided for TotalSegments. If you provide Segment, you must also provide TotalSegments.
2058 */
2059 Segment?: ScanSegment;
2060 /**
2061 * A string that identifies one or more attributes to retrieve from the specified table or index. These attributes can include scalars, sets, or elements of a JSON document. The attributes in the expression must be separated by commas. If no attribute names are specified, then all attributes will be returned. If any of the requested attributes are not found, they will not appear in the result. For more information, see Specifying Item Attributes in the Amazon DynamoDB Developer Guide.
2062 */
2063 ProjectionExpression?: ProjectionExpression;
2064 /**
2065 * A string that contains conditions that DynamoDB applies after the Scan operation, but before the data is returned to you. Items that do not satisfy the FilterExpression criteria are not returned. A FilterExpression is applied after the items have already been read; the process of filtering does not consume any additional read capacity units. For more information, see Filter Expressions in the Amazon DynamoDB Developer Guide.
2066 */
2067 FilterExpression?: ConditionExpression;
2068 /**
2069 * One or more substitution tokens for attribute names in an expression. The following are some use cases for using ExpressionAttributeNames: To access an attribute whose name conflicts with a DynamoDB reserved word. To create a placeholder for repeating occurrences of an attribute name in an expression. To prevent special characters in an attribute name from being misinterpreted in an expression. Use the # character in an expression to dereference an attribute name. For example, consider the following attribute name: Percentile The name of this attribute conflicts with a reserved word, so it cannot be used directly in an expression. (For the complete list of reserved words, see Reserved Words in the Amazon DynamoDB Developer Guide). To work around this, you could specify the following for ExpressionAttributeNames: {"#P":"Percentile"} You could then use this substitution in an expression, as in this example: #P = :val Tokens that begin with the : character are expression attribute values, which are placeholders for the actual value at runtime. For more information on expression attribute names, see Specifying Item Attributes in the Amazon DynamoDB Developer Guide.
2070 */
2071 ExpressionAttributeNames?: ExpressionAttributeNameMap;
2072 /**
2073 * One or more values that can be substituted in an expression. Use the : (colon) character in an expression to dereference an attribute value. For example, suppose that you wanted to check whether the value of the ProductStatus attribute was one of the following: Available | Backordered | Discontinued You would first need to specify ExpressionAttributeValues as follows: { ":avail":{"S":"Available"}, ":back":{"S":"Backordered"}, ":disc":{"S":"Discontinued"} } You could then use these values in an expression, such as this: ProductStatus IN (:avail, :back, :disc) For more information on expression attribute values, see Condition Expressions in the Amazon DynamoDB Developer Guide.
2074 */
2075 ExpressionAttributeValues?: ExpressionAttributeValueMap;
2076 /**
2077 * A Boolean value that determines the read consistency model during the scan: If ConsistentRead is false, then the data returned from Scan might not contain the results from other recently completed write operations (PutItem, UpdateItem, or DeleteItem). If ConsistentRead is true, then all of the write operations that completed before the Scan began are guaranteed to be contained in the Scan response. The default setting for ConsistentRead is false. The ConsistentRead parameter is not supported on global secondary indexes. If you scan a global secondary index with ConsistentRead set to true, you will receive a ValidationException.
2078 */
2079 ConsistentRead?: ConsistentRead;
2080 }
2081 export interface ScanOutput {
2082 /**
2083 * An array of item attributes that match the scan criteria. Each element in this array consists of an attribute name and the value for that attribute.
2084 */
2085 Items?: ItemList;
2086 /**
2087 * The number of items in the response. If you set ScanFilter in the request, then Count is the number of items returned after the filter was applied, and ScannedCount is the number of matching items before the filter was applied. If you did not use a filter in the request, then Count is the same as ScannedCount.
2088 */
2089 Count?: Integer;
2090 /**
2091 * The number of items evaluated, before any ScanFilter is applied. A high ScannedCount value with few, or no, Count results indicates an inefficient Scan operation. For more information, see Count and ScannedCount in the Amazon DynamoDB Developer Guide. If you did not use a filter in the request, then ScannedCount is the same as Count.
2092 */
2093 ScannedCount?: Integer;
2094 /**
2095 * The primary key of the item where the operation stopped, inclusive of the previous result set. Use this value to start a new operation, excluding this value in the new request. If LastEvaluatedKey is empty, then the "last page" of results has been processed and there is no more data to be retrieved. If LastEvaluatedKey is not empty, it does not necessarily mean that there is more data in the result set. The only way to know when you have reached the end of the result set is when LastEvaluatedKey is empty.
2096 */
2097 LastEvaluatedKey?: Key;
2098 /**
2099 * The capacity units consumed by the Scan operation. The data returned includes the total provisioned throughput consumed, along with statistics for the table and any indexes involved in the operation. ConsumedCapacity is only returned if the ReturnConsumedCapacity parameter was specified. For more information, see Provisioned Throughput in the Amazon DynamoDB Developer Guide.
2100 */
2101 ConsumedCapacity?: ConsumedCapacity;
2102 }
2103 export type ScanSegment = number;
2104 export type ScanTotalSegments = number;
2105 export type SecondaryIndexesCapacityMap = {[key: string]: Capacity};
2106 export type Select = "ALL_ATTRIBUTES"|"ALL_PROJECTED_ATTRIBUTES"|"SPECIFIC_ATTRIBUTES"|"COUNT"|string;
2107 export interface SourceTableDetails {
2108 /**
2109 * The name of the table for which the backup was created.
2110 */
2111 TableName: TableName;
2112 /**
2113 * Unique identifier for the table for which the backup was created.
2114 */
2115 TableId: TableId;
2116 /**
2117 * ARN of the table for which backup was created.
2118 */
2119 TableArn?: TableArn;
2120 /**
2121 * Size of the table in bytes. Please note this is an approximate value.
2122 */
2123 TableSizeBytes?: Long;
2124 /**
2125 * Schema of the table.
2126 */
2127 KeySchema: KeySchema;
2128 /**
2129 * Time when the source table was created.
2130 */
2131 TableCreationDateTime: TableCreationDateTime;
2132 /**
2133 * Read IOPs and Write IOPS on the table when the backup was created.
2134 */
2135 ProvisionedThroughput: ProvisionedThroughput;
2136 /**
2137 * Number of items in the table. Please note this is an approximate value.
2138 */
2139 ItemCount?: ItemCount;
2140 /**
2141 * Controls how you are charged for read and write throughput and how you manage capacity. This setting can be changed later. PROVISIONED - Sets the read/write capacity mode to PROVISIONED. We recommend using PROVISIONED for predictable workloads. PAY_PER_REQUEST - Sets the read/write capacity mode to PAY_PER_REQUEST. We recommend using PAY_PER_REQUEST for unpredictable workloads.
2142 */
2143 BillingMode?: BillingMode;
2144 }
2145 export interface SourceTableFeatureDetails {
2146 /**
2147 * Represents the LSI properties for the table when the backup was created. It includes the IndexName, KeySchema and Projection for the LSIs on the table at the time of backup.
2148 */
2149 LocalSecondaryIndexes?: LocalSecondaryIndexes;
2150 /**
2151 * Represents the GSI properties for the table when the backup was created. It includes the IndexName, KeySchema, Projection and ProvisionedThroughput for the GSIs on the table at the time of backup.
2152 */
2153 GlobalSecondaryIndexes?: GlobalSecondaryIndexes;
2154 /**
2155 * Stream settings on the table when the backup was created.
2156 */
2157 StreamDescription?: StreamSpecification;
2158 /**
2159 * Time to Live settings on the table when the backup was created.
2160 */
2161 TimeToLiveDescription?: TimeToLiveDescription;
2162 /**
2163 * The description of the server-side encryption status on the table when the backup was created.
2164 */
2165 SSEDescription?: SSEDescription;
2166 }
2167 export type StreamArn = string;
2168 export type StreamEnabled = boolean;
2169 export interface StreamSpecification {
2170 /**
2171 * Indicates whether DynamoDB Streams is enabled (true) or disabled (false) on the table.
2172 */
2173 StreamEnabled?: StreamEnabled;
2174 /**
2175 * When an item in the table is modified, StreamViewType determines what information is written to the stream for this table. Valid values for StreamViewType are: KEYS_ONLY - Only the key attributes of the modified item are written to the stream. NEW_IMAGE - The entire item, as it appears after it was modified, is written to the stream. OLD_IMAGE - The entire item, as it appeared before it was modified, is written to the stream. NEW_AND_OLD_IMAGES - Both the new and the old item images of the item are written to the stream.
2176 */
2177 StreamViewType?: StreamViewType;
2178 }
2179 export type StreamViewType = "NEW_IMAGE"|"OLD_IMAGE"|"NEW_AND_OLD_IMAGES"|"KEYS_ONLY"|string;
2180 export type String = string;
2181 export type StringAttributeValue = string;
2182 export type StringSetAttributeValue = StringAttributeValue[];
2183 export type TableArn = string;
2184 export type TableCreationDateTime = Date;
2185 export interface TableDescription {
2186 /**
2187 * An array of AttributeDefinition objects. Each of these objects describes one attribute in the table and index key schema. Each AttributeDefinition object in this array is composed of: AttributeName - The name of the attribute. AttributeType - The data type for the attribute.
2188 */
2189 AttributeDefinitions?: AttributeDefinitions;
2190 /**
2191 * The name of the table.
2192 */
2193 TableName?: TableName;
2194 /**
2195 * The primary key structure for the table. Each KeySchemaElement consists of: AttributeName - The name of the attribute. KeyType - The role of the attribute: HASH - partition key RANGE - sort key The partition key of an item is also known as its hash attribute. The term "hash attribute" derives from DynamoDB's usage of an internal hash function to evenly distribute data items across partitions, based on their partition key values. The sort key of an item is also known as its range attribute. The term "range attribute" derives from the way DynamoDB stores items with the same partition key physically close together, in sorted order by the sort key value. For more information about primary keys, see Primary Key in the Amazon DynamoDB Developer Guide.
2196 */
2197 KeySchema?: KeySchema;
2198 /**
2199 * The current state of the table: CREATING - The table is being created. UPDATING - The table is being updated. DELETING - The table is being deleted. ACTIVE - The table is ready for use.
2200 */
2201 TableStatus?: TableStatus;
2202 /**
2203 * The date and time when the table was created, in UNIX epoch time format.
2204 */
2205 CreationDateTime?: _Date;
2206 /**
2207 * The provisioned throughput settings for the table, consisting of read and write capacity units, along with data about increases and decreases.
2208 */
2209 ProvisionedThroughput?: ProvisionedThroughputDescription;
2210 /**
2211 * The total size of the specified table, in bytes. DynamoDB updates this value approximately every six hours. Recent changes might not be reflected in this value.
2212 */
2213 TableSizeBytes?: Long;
2214 /**
2215 * The number of items in the specified table. DynamoDB updates this value approximately every six hours. Recent changes might not be reflected in this value.
2216 */
2217 ItemCount?: Long;
2218 /**
2219 * The Amazon Resource Name (ARN) that uniquely identifies the table.
2220 */
2221 TableArn?: String;
2222 /**
2223 * Unique identifier for the table for which the backup was created.
2224 */
2225 TableId?: TableId;
2226 /**
2227 * Contains the details for the read/write capacity mode.
2228 */
2229 BillingModeSummary?: BillingModeSummary;
2230 /**
2231 * Represents one or more local secondary indexes on the table. Each index is scoped to a given partition key value. Tables with one or more local secondary indexes are subject to an item collection size limit, where the amount of data within a given item collection cannot exceed 10 GB. Each element is composed of: IndexName - The name of the local secondary index. KeySchema - Specifies the complete index key schema. The attribute names in the key schema must be between 1 and 255 characters (inclusive). The key schema must begin with the same partition key as the table. Projection - Specifies attributes that are copied (projected) from the table into the index. These are in addition to the primary key attributes and index key attributes, which are automatically projected. Each attribute specification is composed of: ProjectionType - One of the following: KEYS_ONLY - Only the index and primary keys are projected into the index. INCLUDE - Only the specified table attributes are projected into the index. The list of projected attributes are in NonKeyAttributes. ALL - All of the table attributes are projected into the index. NonKeyAttributes - A list of one or more non-key attribute names that are projected into the secondary index. The total count of attributes provided in NonKeyAttributes, summed across all of the secondary indexes, must not exceed 20. If you project the same attribute into two different indexes, this counts as two distinct attributes when determining the total. IndexSizeBytes - Represents the total size of the index, in bytes. DynamoDB updates this value approximately every six hours. Recent changes might not be reflected in this value. ItemCount - Represents the number of items in the index. DynamoDB updates this value approximately every six hours. Recent changes might not be reflected in this value. If the table is in the DELETING state, no information about indexes will be returned.
2232 */
2233 LocalSecondaryIndexes?: LocalSecondaryIndexDescriptionList;
2234 /**
2235 * The global secondary indexes, if any, on the table. Each index is scoped to a given partition key value. Each element is composed of: Backfilling - If true, then the index is currently in the backfilling phase. Backfilling occurs only when a new global secondary index is added to the table; it is the process by which DynamoDB populates the new index with data from the table. (This attribute does not appear for indexes that were created during a CreateTable operation.) IndexName - The name of the global secondary index. IndexSizeBytes - The total size of the global secondary index, in bytes. DynamoDB updates this value approximately every six hours. Recent changes might not be reflected in this value. IndexStatus - The current status of the global secondary index: CREATING - The index is being created. UPDATING - The index is being updated. DELETING - The index is being deleted. ACTIVE - The index is ready for use. ItemCount - The number of items in the global secondary index. DynamoDB updates this value approximately every six hours. Recent changes might not be reflected in this value. KeySchema - Specifies the complete index key schema. The attribute names in the key schema must be between 1 and 255 characters (inclusive). The key schema must begin with the same partition key as the table. Projection - Specifies attributes that are copied (projected) from the table into the index. These are in addition to the primary key attributes and index key attributes, which are automatically projected. Each attribute specification is composed of: ProjectionType - One of the following: KEYS_ONLY - Only the index and primary keys are projected into the index. INCLUDE - Only the specified table attributes are projected into the index. The list of projected attributes are in NonKeyAttributes. ALL - All of the table attributes are projected into the index. NonKeyAttributes - A list of one or more non-key attribute names that are projected into the secondary index. The total count of attributes provided in NonKeyAttributes, summed across all of the secondary indexes, must not exceed 20. If you project the same attribute into two different indexes, this counts as two distinct attributes when determining the total. ProvisionedThroughput - The provisioned throughput settings for the global secondary index, consisting of read and write capacity units, along with data about increases and decreases. If the table is in the DELETING state, no information about indexes will be returned.
2236 */
2237 GlobalSecondaryIndexes?: GlobalSecondaryIndexDescriptionList;
2238 /**
2239 * The current DynamoDB Streams configuration for the table.
2240 */
2241 StreamSpecification?: StreamSpecification;
2242 /**
2243 * A timestamp, in ISO 8601 format, for this stream. Note that LatestStreamLabel is not a unique identifier for the stream, because it is possible that a stream from another table might have the same timestamp. However, the combination of the following three elements is guaranteed to be unique: the AWS customer ID. the table name. the StreamLabel.
2244 */
2245 LatestStreamLabel?: String;
2246 /**
2247 * The Amazon Resource Name (ARN) that uniquely identifies the latest stream for this table.
2248 */
2249 LatestStreamArn?: StreamArn;
2250 /**
2251 * Contains details for the restore.
2252 */
2253 RestoreSummary?: RestoreSummary;
2254 /**
2255 * The description of the server-side encryption status on the specified table.
2256 */
2257 SSEDescription?: SSEDescription;
2258 }
2259 export type TableId = string;
2260 export type TableName = string;
2261 export type TableNameList = TableName[];
2262 export type TableStatus = "CREATING"|"UPDATING"|"DELETING"|"ACTIVE"|string;
2263 export interface Tag {
2264 /**
2265 * The key of the tag. Tag keys are case sensitive. Each DynamoDB table can only have up to one tag with the same key. If you try to add an existing tag (same key), the existing tag value will be updated to the new value.
2266 */
2267 Key: TagKeyString;
2268 /**
2269 * The value of the tag. Tag values are case-sensitive and can be null.
2270 */
2271 Value: TagValueString;
2272 }
2273 export type TagKeyList = TagKeyString[];
2274 export type TagKeyString = string;
2275 export type TagList = Tag[];
2276 export interface TagResourceInput {
2277 /**
2278 * Identifies the Amazon DynamoDB resource to which tags should be added. This value is an Amazon Resource Name (ARN).
2279 */
2280 ResourceArn: ResourceArnString;
2281 /**
2282 * The tags to be assigned to the Amazon DynamoDB resource.
2283 */
2284 Tags: TagList;
2285 }
2286 export type TagValueString = string;
2287 export type TimeRangeLowerBound = Date;
2288 export type TimeRangeUpperBound = Date;
2289 export type TimeToLiveAttributeName = string;
2290 export interface TimeToLiveDescription {
2291 /**
2292 * The TTL status for the table.
2293 */
2294 TimeToLiveStatus?: TimeToLiveStatus;
2295 /**
2296 * The name of the TTL attribute for items in the table.
2297 */
2298 AttributeName?: TimeToLiveAttributeName;
2299 }
2300 export type TimeToLiveEnabled = boolean;
2301 export interface TimeToLiveSpecification {
2302 /**
2303 * Indicates whether TTL is to be enabled (true) or disabled (false) on the table.
2304 */
2305 Enabled: TimeToLiveEnabled;
2306 /**
2307 * The name of the TTL attribute used to store the expiration time for items in the table.
2308 */
2309 AttributeName: TimeToLiveAttributeName;
2310 }
2311 export type TimeToLiveStatus = "ENABLING"|"DISABLING"|"ENABLED"|"DISABLED"|string;
2312 export interface TransactGetItem {
2313 /**
2314 * Contains the primary key that identifies the item to get, together with the name of the table that contains the item, and optionally the specific attributes of the item to retrieve.
2315 */
2316 Get: Get;
2317 }
2318 export type TransactGetItemList = TransactGetItem[];
2319 export interface TransactGetItemsInput {
2320 /**
2321 * An ordered array of up to 25 TransactGetItem objects, each of which contains a Get structure.
2322 */
2323 TransactItems: TransactGetItemList;
2324 /**
2325 * A value of TOTAL causes consumed capacity information to be returned, and a value of NONE prevents that information from being returned. No other value is valid.
2326 */
2327 ReturnConsumedCapacity?: ReturnConsumedCapacity;
2328 }
2329 export interface TransactGetItemsOutput {
2330 /**
2331 * If the ReturnConsumedCapacity value was TOTAL, this is an array of ConsumedCapacity objects, one for each table addressed by TransactGetItem objects in the TransactItems parameter. These ConsumedCapacity objects report the read-capacity units consumed by the TransactGetItems call in that table.
2332 */
2333 ConsumedCapacity?: ConsumedCapacityMultiple;
2334 /**
2335 * An ordered array of up to 25 ItemResponse objects, each of which corresponds to the TransactGetItem object in the same position in the TransactItems array. Each ItemResponse object contains a Map of the name-value pairs that are the projected attributes of the requested item. If a requested item could not be retrieved, the corresponding ItemResponse object is Null, or if the requested item has no projected attributes, the corresponding ItemResponse object is an empty Map.
2336 */
2337 Responses?: ItemResponseList;
2338 }
2339 export interface TransactWriteItem {
2340 /**
2341 * A request to perform a check item operation.
2342 */
2343 ConditionCheck?: ConditionCheck;
2344 /**
2345 * A request to perform a PutItem operation.
2346 */
2347 Put?: Put;
2348 /**
2349 * A request to perform a DeleteItem operation.
2350 */
2351 Delete?: Delete;
2352 /**
2353 * A request to perform an UpdateItem operation.
2354 */
2355 Update?: Update;
2356 }
2357 export type TransactWriteItemList = TransactWriteItem[];
2358 export interface TransactWriteItemsInput {
2359 /**
2360 * An ordered array of up to 25 TransactWriteItem objects, each of which contains a ConditionCheck, Put, Update, or Delete object. These can operate on items in different tables, but the tables must reside in the same AWS account and Region, and no two of them can operate on the same item.
2361 */
2362 TransactItems: TransactWriteItemList;
2363 ReturnConsumedCapacity?: ReturnConsumedCapacity;
2364 /**
2365 * Determines whether item collection metrics are returned. If set to SIZE, the response includes statistics about item collections (if any), that were modified during the operation and are returned in the response. If set to NONE (the default), no statistics are returned.
2366 */
2367 ReturnItemCollectionMetrics?: ReturnItemCollectionMetrics;
2368 /**
2369 * Providing a ClientRequestToken makes the call to TransactWriteItems idempotent, meaning that multiple identical calls have the same effect as one single call. Although multiple identical calls using the same client request token produce the same result on the server (no side effects), the responses to the calls might not be the same. If the ReturnConsumedCapacity&gt; parameter is set, then the initial TransactWriteItems call returns the amount of write capacity units consumed in making the changes. Subsequent TransactWriteItems calls with the same client token return the number of read capacity units consumed in reading the item. A client request token is valid for 10 minutes after the first request that uses it is completed. After 10 minutes, any request with the same client token is treated as a new request. Do not resubmit the same request with the same client token for more than 10 minutes, or the result might not be idempotent. If you submit a request with the same client token but a change in other parameters within the 10-minute idempotency window, DynamoDB returns an IdempotentParameterMismatch exception.
2370 */
2371 ClientRequestToken?: ClientRequestToken;
2372 }
2373 export interface TransactWriteItemsOutput {
2374 /**
2375 * The capacity units consumed by the entire TransactWriteItems operation. The values of the list are ordered according to the ordering of the TransactItems request parameter.
2376 */
2377 ConsumedCapacity?: ConsumedCapacityMultiple;
2378 /**
2379 * A list of tables that were processed by TransactWriteItems and, for each table, information about any item collections that were affected by individual UpdateItem, PutItem, or DeleteItem operations.
2380 */
2381 ItemCollectionMetrics?: ItemCollectionMetricsPerTable;
2382 }
2383 export interface UntagResourceInput {
2384 /**
2385 * The DynamoDB resource that the tags will be removed from. This value is an Amazon Resource Name (ARN).
2386 */
2387 ResourceArn: ResourceArnString;
2388 /**
2389 * A list of tag keys. Existing tags of the resource whose keys are members of this list will be removed from the DynamoDB resource.
2390 */
2391 TagKeys: TagKeyList;
2392 }
2393 export interface Update {
2394 /**
2395 * The primary key of the item to be updated. Each element consists of an attribute name and a value for that attribute.
2396 */
2397 Key: Key;
2398 /**
2399 * An expression that defines one or more attributes to be updated, the action to be performed on them, and new value(s) for them.
2400 */
2401 UpdateExpression: UpdateExpression;
2402 /**
2403 * Name of the table for the UpdateItem request.
2404 */
2405 TableName: TableName;
2406 /**
2407 * A condition that must be satisfied in order for a conditional update to succeed.
2408 */
2409 ConditionExpression?: ConditionExpression;
2410 /**
2411 * One or more substitution tokens for attribute names in an expression.
2412 */
2413 ExpressionAttributeNames?: ExpressionAttributeNameMap;
2414 /**
2415 * One or more values that can be substituted in an expression.
2416 */
2417 ExpressionAttributeValues?: ExpressionAttributeValueMap;
2418 /**
2419 * Use ReturnValuesOnConditionCheckFailure to get the item attributes if the Update condition fails. For ReturnValuesOnConditionCheckFailure, the valid values are: NONE, ALL_OLD, UPDATED_OLD, ALL_NEW, UPDATED_NEW.
2420 */
2421 ReturnValuesOnConditionCheckFailure?: ReturnValuesOnConditionCheckFailure;
2422 }
2423 export interface UpdateContinuousBackupsInput {
2424 /**
2425 * The name of the table.
2426 */
2427 TableName: TableName;
2428 /**
2429 * Represents the settings used to enable point in time recovery.
2430 */
2431 PointInTimeRecoverySpecification: PointInTimeRecoverySpecification;
2432 }
2433 export interface UpdateContinuousBackupsOutput {
2434 /**
2435 * Represents the continuous backups and point in time recovery settings on the table.
2436 */
2437 ContinuousBackupsDescription?: ContinuousBackupsDescription;
2438 }
2439 export type UpdateExpression = string;
2440 export interface UpdateGlobalSecondaryIndexAction {
2441 /**
2442 * The name of the global secondary index to be updated.
2443 */
2444 IndexName: IndexName;
2445 /**
2446 * Represents the provisioned throughput settings for the specified global secondary index. For current minimum and maximum provisioned throughput values, see Limits in the Amazon DynamoDB Developer Guide.
2447 */
2448 ProvisionedThroughput: ProvisionedThroughput;
2449 }
2450 export interface UpdateGlobalTableInput {
2451 /**
2452 * The global table name.
2453 */
2454 GlobalTableName: TableName;
2455 /**
2456 * A list of Regions that should be added or removed from the global table.
2457 */
2458 ReplicaUpdates: ReplicaUpdateList;
2459 }
2460 export interface UpdateGlobalTableOutput {
2461 /**
2462 * Contains the details of the global table.
2463 */
2464 GlobalTableDescription?: GlobalTableDescription;
2465 }
2466 export interface UpdateGlobalTableSettingsInput {
2467 /**
2468 * The name of the global table
2469 */
2470 GlobalTableName: TableName;
2471 /**
2472 * The billing mode of the global table. If GlobalTableBillingMode is not specified, the global table defaults to PROVISIONED capacity billing mode.
2473 */
2474 GlobalTableBillingMode?: BillingMode;
2475 /**
2476 * The maximum number of writes consumed per second before DynamoDB returns a ThrottlingException.
2477 */
2478 GlobalTableProvisionedWriteCapacityUnits?: PositiveLongObject;
2479 /**
2480 * Auto scaling settings for managing provisioned write capacity for the global table.
2481 */
2482 GlobalTableProvisionedWriteCapacityAutoScalingSettingsUpdate?: AutoScalingSettingsUpdate;
2483 /**
2484 * Represents the settings of a global secondary index for a global table that will be modified.
2485 */
2486 GlobalTableGlobalSecondaryIndexSettingsUpdate?: GlobalTableGlobalSecondaryIndexSettingsUpdateList;
2487 /**
2488 * Represents the settings for a global table in a Region that will be modified.
2489 */
2490 ReplicaSettingsUpdate?: ReplicaSettingsUpdateList;
2491 }
2492 export interface UpdateGlobalTableSettingsOutput {
2493 /**
2494 * The name of the global table.
2495 */
2496 GlobalTableName?: TableName;
2497 /**
2498 * The Region-specific settings for the global table.
2499 */
2500 ReplicaSettings?: ReplicaSettingsDescriptionList;
2501 }
2502 export interface UpdateItemInput {
2503 /**
2504 * The name of the table containing the item to update.
2505 */
2506 TableName: TableName;
2507 /**
2508 * The primary key of the item to be updated. Each element consists of an attribute name and a value for that attribute. For the primary key, you must provide all of the attributes. For example, with a simple primary key, you only need to provide a value for the partition key. For a composite primary key, you must provide values for both the partition key and the sort key.
2509 */
2510 Key: Key;
2511 /**
2512 * This is a legacy parameter. Use UpdateExpression instead. For more information, see AttributeUpdates in the Amazon DynamoDB Developer Guide.
2513 */
2514 AttributeUpdates?: AttributeUpdates;
2515 /**
2516 * This is a legacy parameter. Use ConditionExpression instead. For more information, see Expected in the Amazon DynamoDB Developer Guide.
2517 */
2518 Expected?: ExpectedAttributeMap;
2519 /**
2520 * This is a legacy parameter. Use ConditionExpression instead. For more information, see ConditionalOperator in the Amazon DynamoDB Developer Guide.
2521 */
2522 ConditionalOperator?: ConditionalOperator;
2523 /**
2524 * Use ReturnValues if you want to get the item attributes as they appear before or after they are updated. For UpdateItem, the valid values are: NONE - If ReturnValues is not specified, or if its value is NONE, then nothing is returned. (This setting is the default for ReturnValues.) ALL_OLD - Returns all of the attributes of the item, as they appeared before the UpdateItem operation. UPDATED_OLD - Returns only the updated attributes, as they appeared before the UpdateItem operation. ALL_NEW - Returns all of the attributes of the item, as they appear after the UpdateItem operation. UPDATED_NEW - Returns only the updated attributes, as they appear after the UpdateItem operation. There is no additional cost associated with requesting a return value aside from the small network and processing overhead of receiving a larger response. No read capacity units are consumed. The values returned are strongly consistent.
2525 */
2526 ReturnValues?: ReturnValue;
2527 ReturnConsumedCapacity?: ReturnConsumedCapacity;
2528 /**
2529 * Determines whether item collection metrics are returned. If set to SIZE, the response includes statistics about item collections, if any, that were modified during the operation are returned in the response. If set to NONE (the default), no statistics are returned.
2530 */
2531 ReturnItemCollectionMetrics?: ReturnItemCollectionMetrics;
2532 /**
2533 * An expression that defines one or more attributes to be updated, the action to be performed on them, and new values for them. The following action values are available for UpdateExpression. SET - Adds one or more attributes and values to an item. If any of these attributes already exist, they are replaced by the new values. You can also use SET to add or subtract from an attribute that is of type Number. For example: SET myNum = myNum + :val SET supports the following functions: if_not_exists (path, operand) - if the item does not contain an attribute at the specified path, then if_not_exists evaluates to operand; otherwise, it evaluates to path. You can use this function to avoid overwriting an attribute that may already be present in the item. list_append (operand, operand) - evaluates to a list with a new element added to it. You can append the new element to the start or the end of the list by reversing the order of the operands. These function names are case-sensitive. REMOVE - Removes one or more attributes from an item. ADD - Adds the specified value to the item, if the attribute does not already exist. If the attribute does exist, then the behavior of ADD depends on the data type of the attribute: If the existing attribute is a number, and if Value is also a number, then Value is mathematically added to the existing attribute. If Value is a negative number, then it is subtracted from the existing attribute. If you use ADD to increment or decrement a number value for an item that doesn't exist before the update, DynamoDB uses 0 as the initial value. Similarly, if you use ADD for an existing item to increment or decrement an attribute value that doesn't exist before the update, DynamoDB uses 0 as the initial value. For example, suppose that the item you want to update doesn't have an attribute named itemcount, but you decide to ADD the number 3 to this attribute anyway. DynamoDB will create the itemcount attribute, set its initial value to 0, and finally add 3 to it. The result will be a new itemcount attribute in the item, with a value of 3. If the existing data type is a set and if Value is also a set, then Value is added to the existing set. For example, if the attribute value is the set [1,2], and the ADD action specified [3], then the final attribute value is [1,2,3]. An error occurs if an ADD action is specified for a set attribute and the attribute type specified does not match the existing set type. Both sets must have the same primitive data type. For example, if the existing data type is a set of strings, the Value must also be a set of strings. The ADD action only supports Number and set data types. In addition, ADD can only be used on top-level attributes, not nested attributes. DELETE - Deletes an element from a set. If a set of values is specified, then those values are subtracted from the old set. For example, if the attribute value was the set [a,b,c] and the DELETE action specifies [a,c], then the final attribute value is [b]. Specifying an empty set is an error. The DELETE action only supports set data types. In addition, DELETE can only be used on top-level attributes, not nested attributes. You can have many actions in a single expression, such as the following: SET a=:value1, b=:value2 DELETE :value3, :value4, :value5 For more information on update expressions, see Modifying Items and Attributes in the Amazon DynamoDB Developer Guide.
2534 */
2535 UpdateExpression?: UpdateExpression;
2536 /**
2537 * A condition that must be satisfied in order for a conditional update to succeed. An expression can contain any of the following: Functions: attribute_exists | attribute_not_exists | attribute_type | contains | begins_with | size These function names are case-sensitive. Comparison operators: = | &lt;&gt; | &lt; | &gt; | &lt;= | &gt;= | BETWEEN | IN Logical operators: AND | OR | NOT For more information about condition expressions, see Specifying Conditions in the Amazon DynamoDB Developer Guide.
2538 */
2539 ConditionExpression?: ConditionExpression;
2540 /**
2541 * One or more substitution tokens for attribute names in an expression. The following are some use cases for using ExpressionAttributeNames: To access an attribute whose name conflicts with a DynamoDB reserved word. To create a placeholder for repeating occurrences of an attribute name in an expression. To prevent special characters in an attribute name from being misinterpreted in an expression. Use the # character in an expression to dereference an attribute name. For example, consider the following attribute name: Percentile The name of this attribute conflicts with a reserved word, so it cannot be used directly in an expression. (For the complete list of reserved words, see Reserved Words in the Amazon DynamoDB Developer Guide.) To work around this, you could specify the following for ExpressionAttributeNames: {"#P":"Percentile"} You could then use this substitution in an expression, as in this example: #P = :val Tokens that begin with the : character are expression attribute values, which are placeholders for the actual value at runtime. For more information about expression attribute names, see Specifying Item Attributes in the Amazon DynamoDB Developer Guide.
2542 */
2543 ExpressionAttributeNames?: ExpressionAttributeNameMap;
2544 /**
2545 * One or more values that can be substituted in an expression. Use the : (colon) character in an expression to dereference an attribute value. For example, suppose that you wanted to check whether the value of the ProductStatus attribute was one of the following: Available | Backordered | Discontinued You would first need to specify ExpressionAttributeValues as follows: { ":avail":{"S":"Available"}, ":back":{"S":"Backordered"}, ":disc":{"S":"Discontinued"} } You could then use these values in an expression, such as this: ProductStatus IN (:avail, :back, :disc) For more information on expression attribute values, see Condition Expressions in the Amazon DynamoDB Developer Guide.
2546 */
2547 ExpressionAttributeValues?: ExpressionAttributeValueMap;
2548 }
2549 export interface UpdateItemOutput {
2550 /**
2551 * A map of attribute values as they appear before or after the UpdateItem operation, as determined by the ReturnValues parameter. The Attributes map is only present if ReturnValues was specified as something other than NONE in the request. Each element represents one attribute.
2552 */
2553 Attributes?: AttributeMap;
2554 /**
2555 * The capacity units consumed by the UpdateItem operation. The data returned includes the total provisioned throughput consumed, along with statistics for the table and any indexes involved in the operation. ConsumedCapacity is only returned if the ReturnConsumedCapacity parameter was specified. For more information, see Provisioned Throughput in the Amazon DynamoDB Developer Guide.
2556 */
2557 ConsumedCapacity?: ConsumedCapacity;
2558 /**
2559 * Information about item collections, if any, that were affected by the UpdateItem operation. ItemCollectionMetrics is only returned if the ReturnItemCollectionMetrics parameter was specified. If the table does not have any local secondary indexes, this information is not returned in the response. Each ItemCollectionMetrics element consists of: ItemCollectionKey - The partition key value of the item collection. This is the same as the partition key value of the item itself. SizeEstimateRangeGB - An estimate of item collection size, in gigabytes. This value is a two-element array containing a lower bound and an upper bound for the estimate. The estimate includes the size of all the items in the table, plus the size of all attributes projected into all of the local secondary indexes on that table. Use this estimate to measure whether a local secondary index is approaching its size limit. The estimate is subject to change over time; therefore, do not rely on the precision or accuracy of the estimate.
2560 */
2561 ItemCollectionMetrics?: ItemCollectionMetrics;
2562 }
2563 export interface UpdateTableInput {
2564 /**
2565 * An array of attributes that describe the key schema for the table and indexes. If you are adding a new global secondary index to the table, AttributeDefinitions must include the key element(s) of the new index.
2566 */
2567 AttributeDefinitions?: AttributeDefinitions;
2568 /**
2569 * The name of the table to be updated.
2570 */
2571 TableName: TableName;
2572 /**
2573 * Controls how you are charged for read and write throughput and how you manage capacity. When switching from pay-per-request to provisioned capacity, initial provisioned capacity values must be set. The initial provisioned capacity values are estimated based on the consumed read and write capacity of your table and global secondary indexes over the past 30 minutes. PROVISIONED - Sets the billing mode to PROVISIONED. We recommend using PROVISIONED for predictable workloads. PAY_PER_REQUEST - Sets the billing mode to PAY_PER_REQUEST. We recommend using PAY_PER_REQUEST for unpredictable workloads.
2574 */
2575 BillingMode?: BillingMode;
2576 /**
2577 * The new provisioned throughput settings for the specified table or index.
2578 */
2579 ProvisionedThroughput?: ProvisionedThroughput;
2580 /**
2581 * An array of one or more global secondary indexes for the table. For each index in the array, you can request one action: Create - add a new global secondary index to the table. Update - modify the provisioned throughput settings of an existing global secondary index. Delete - remove a global secondary index from the table. For more information, see Managing Global Secondary Indexes in the Amazon DynamoDB Developer Guide.
2582 */
2583 GlobalSecondaryIndexUpdates?: GlobalSecondaryIndexUpdateList;
2584 /**
2585 * Represents the DynamoDB Streams configuration for the table. You receive a ResourceInUseException if you try to enable a stream on a table that already has a stream, or if you try to disable a stream on a table that doesn't have a stream.
2586 */
2587 StreamSpecification?: StreamSpecification;
2588 /**
2589 * The new server-side encryption settings for the specified table.
2590 */
2591 SSESpecification?: SSESpecification;
2592 }
2593 export interface UpdateTableOutput {
2594 /**
2595 * Represents the properties of the table.
2596 */
2597 TableDescription?: TableDescription;
2598 }
2599 export interface UpdateTimeToLiveInput {
2600 /**
2601 * The name of the table to be configured.
2602 */
2603 TableName: TableName;
2604 /**
2605 * Represents the settings used to enable or disable Time to Live for the specified table.
2606 */
2607 TimeToLiveSpecification: TimeToLiveSpecification;
2608 }
2609 export interface UpdateTimeToLiveOutput {
2610 /**
2611 * Represents the output of an UpdateTimeToLive operation.
2612 */
2613 TimeToLiveSpecification?: TimeToLiveSpecification;
2614 }
2615 export interface WriteRequest {
2616 /**
2617 * A request to perform a PutItem operation.
2618 */
2619 PutRequest?: PutRequest;
2620 /**
2621 * A request to perform a DeleteItem operation.
2622 */
2623 DeleteRequest?: DeleteRequest;
2624 }
2625 export type WriteRequests = WriteRequest[];
2626 /**
2627 * A string in YYYY-MM-DD format that represents the latest possible API version that can be used in this service. Specify 'latest' to use the latest possible version.
2628 */
2629 export type apiVersion = "2011-12-05"|"2012-08-10"|"latest"|string;
2630 export interface ClientApiVersions {
2631 /**
2632 * A string in YYYY-MM-DD format that represents the latest possible API version that can be used in this service. Specify 'latest' to use the latest possible version.
2633 */
2634 apiVersion?: apiVersion;
2635 }
2636 export type ClientConfiguration = ServiceConfigurationOptions & ClientApiVersions;
2637 /**
2638 * Contains interfaces for use with the DynamoDB client.
2639 */
2640 export import Types = DynamoDB;
2641}
2642export = DynamoDB;