• Home
• aws.sdk.kotlin
• dynamodb-jvm
• 1.1.0
• source code
• DynamoDbClient.kt

×

Project download

Many resources are needed to download a project. Please understand that we have to compensate our server costs. Thank you in advance.
Project price only 1 $

You can buy this project and download/modify it how often you want.

commonMain.aws.sdk.kotlin.services.dynamodb.DynamoDbClient.kt Maven / Gradle / Ivy

// Code generated by smithy-kotlin-codegen. DO NOT EDIT!

package aws.sdk.kotlin.services.dynamodb

import aws.sdk.kotlin.runtime.auth.credentials.DefaultChainCredentialsProvider
import aws.sdk.kotlin.runtime.auth.credentials.internal.manage
import aws.sdk.kotlin.runtime.client.AwsSdkClientConfig
import aws.sdk.kotlin.runtime.config.AbstractAwsSdkClientFactory
import aws.sdk.kotlin.runtime.config.endpoints.resolveEndpointUrl
import aws.sdk.kotlin.runtime.config.profile.AwsProfile
import aws.sdk.kotlin.runtime.config.profile.AwsSharedConfig
import aws.sdk.kotlin.runtime.http.retries.AwsRetryPolicy
import aws.sdk.kotlin.services.dynamodb.auth.DefaultDynamoDbAuthSchemeProvider
import aws.sdk.kotlin.services.dynamodb.auth.DynamoDbAuthSchemeProvider
import aws.sdk.kotlin.services.dynamodb.endpoints.DefaultDynamoDbEndpointProvider
import aws.sdk.kotlin.services.dynamodb.endpoints.DynamoDbEndpointDiscoverer
import aws.sdk.kotlin.services.dynamodb.endpoints.DynamoDbEndpointParameters
import aws.sdk.kotlin.services.dynamodb.endpoints.DynamoDbEndpointProvider
import aws.sdk.kotlin.services.dynamodb.model.BatchExecuteStatementRequest
import aws.sdk.kotlin.services.dynamodb.model.BatchExecuteStatementResponse
import aws.sdk.kotlin.services.dynamodb.model.BatchGetItemRequest
import aws.sdk.kotlin.services.dynamodb.model.BatchGetItemResponse
import aws.sdk.kotlin.services.dynamodb.model.BatchWriteItemRequest
import aws.sdk.kotlin.services.dynamodb.model.BatchWriteItemResponse
import aws.sdk.kotlin.services.dynamodb.model.CreateBackupRequest
import aws.sdk.kotlin.services.dynamodb.model.CreateBackupResponse
import aws.sdk.kotlin.services.dynamodb.model.CreateGlobalTableRequest
import aws.sdk.kotlin.services.dynamodb.model.CreateGlobalTableResponse
import aws.sdk.kotlin.services.dynamodb.model.CreateTableRequest
import aws.sdk.kotlin.services.dynamodb.model.CreateTableResponse
import aws.sdk.kotlin.services.dynamodb.model.DeleteBackupRequest
import aws.sdk.kotlin.services.dynamodb.model.DeleteBackupResponse
import aws.sdk.kotlin.services.dynamodb.model.DeleteItemRequest
import aws.sdk.kotlin.services.dynamodb.model.DeleteItemResponse
import aws.sdk.kotlin.services.dynamodb.model.DeleteTableRequest
import aws.sdk.kotlin.services.dynamodb.model.DeleteTableResponse
import aws.sdk.kotlin.services.dynamodb.model.DescribeBackupRequest
import aws.sdk.kotlin.services.dynamodb.model.DescribeBackupResponse
import aws.sdk.kotlin.services.dynamodb.model.DescribeContinuousBackupsRequest
import aws.sdk.kotlin.services.dynamodb.model.DescribeContinuousBackupsResponse
import aws.sdk.kotlin.services.dynamodb.model.DescribeContributorInsightsRequest
import aws.sdk.kotlin.services.dynamodb.model.DescribeContributorInsightsResponse
import aws.sdk.kotlin.services.dynamodb.model.DescribeEndpointsRequest
import aws.sdk.kotlin.services.dynamodb.model.DescribeEndpointsResponse
import aws.sdk.kotlin.services.dynamodb.model.DescribeExportRequest
import aws.sdk.kotlin.services.dynamodb.model.DescribeExportResponse
import aws.sdk.kotlin.services.dynamodb.model.DescribeGlobalTableRequest
import aws.sdk.kotlin.services.dynamodb.model.DescribeGlobalTableResponse
import aws.sdk.kotlin.services.dynamodb.model.DescribeGlobalTableSettingsRequest
import aws.sdk.kotlin.services.dynamodb.model.DescribeGlobalTableSettingsResponse
import aws.sdk.kotlin.services.dynamodb.model.DescribeImportRequest
import aws.sdk.kotlin.services.dynamodb.model.DescribeImportResponse
import aws.sdk.kotlin.services.dynamodb.model.DescribeKinesisStreamingDestinationRequest
import aws.sdk.kotlin.services.dynamodb.model.DescribeKinesisStreamingDestinationResponse
import aws.sdk.kotlin.services.dynamodb.model.DescribeLimitsRequest
import aws.sdk.kotlin.services.dynamodb.model.DescribeLimitsResponse
import aws.sdk.kotlin.services.dynamodb.model.DescribeTableReplicaAutoScalingRequest
import aws.sdk.kotlin.services.dynamodb.model.DescribeTableReplicaAutoScalingResponse
import aws.sdk.kotlin.services.dynamodb.model.DescribeTableRequest
import aws.sdk.kotlin.services.dynamodb.model.DescribeTableResponse
import aws.sdk.kotlin.services.dynamodb.model.DescribeTimeToLiveRequest
import aws.sdk.kotlin.services.dynamodb.model.DescribeTimeToLiveResponse
import aws.sdk.kotlin.services.dynamodb.model.DisableKinesisStreamingDestinationRequest
import aws.sdk.kotlin.services.dynamodb.model.DisableKinesisStreamingDestinationResponse
import aws.sdk.kotlin.services.dynamodb.model.EnableKinesisStreamingDestinationRequest
import aws.sdk.kotlin.services.dynamodb.model.EnableKinesisStreamingDestinationResponse
import aws.sdk.kotlin.services.dynamodb.model.ExecuteStatementRequest
import aws.sdk.kotlin.services.dynamodb.model.ExecuteStatementResponse
import aws.sdk.kotlin.services.dynamodb.model.ExecuteTransactionRequest
import aws.sdk.kotlin.services.dynamodb.model.ExecuteTransactionResponse
import aws.sdk.kotlin.services.dynamodb.model.ExportTableToPointInTimeRequest
import aws.sdk.kotlin.services.dynamodb.model.ExportTableToPointInTimeResponse
import aws.sdk.kotlin.services.dynamodb.model.GetItemRequest
import aws.sdk.kotlin.services.dynamodb.model.GetItemResponse
import aws.sdk.kotlin.services.dynamodb.model.ImportTableRequest
import aws.sdk.kotlin.services.dynamodb.model.ImportTableResponse
import aws.sdk.kotlin.services.dynamodb.model.ListBackupsRequest
import aws.sdk.kotlin.services.dynamodb.model.ListBackupsResponse
import aws.sdk.kotlin.services.dynamodb.model.ListContributorInsightsRequest
import aws.sdk.kotlin.services.dynamodb.model.ListContributorInsightsResponse
import aws.sdk.kotlin.services.dynamodb.model.ListExportsRequest
import aws.sdk.kotlin.services.dynamodb.model.ListExportsResponse
import aws.sdk.kotlin.services.dynamodb.model.ListGlobalTablesRequest
import aws.sdk.kotlin.services.dynamodb.model.ListGlobalTablesResponse
import aws.sdk.kotlin.services.dynamodb.model.ListImportsRequest
import aws.sdk.kotlin.services.dynamodb.model.ListImportsResponse
import aws.sdk.kotlin.services.dynamodb.model.ListTablesRequest
import aws.sdk.kotlin.services.dynamodb.model.ListTablesResponse
import aws.sdk.kotlin.services.dynamodb.model.ListTagsOfResourceRequest
import aws.sdk.kotlin.services.dynamodb.model.ListTagsOfResourceResponse
import aws.sdk.kotlin.services.dynamodb.model.PutItemRequest
import aws.sdk.kotlin.services.dynamodb.model.PutItemResponse
import aws.sdk.kotlin.services.dynamodb.model.QueryRequest
import aws.sdk.kotlin.services.dynamodb.model.QueryResponse
import aws.sdk.kotlin.services.dynamodb.model.RestoreTableFromBackupRequest
import aws.sdk.kotlin.services.dynamodb.model.RestoreTableFromBackupResponse
import aws.sdk.kotlin.services.dynamodb.model.RestoreTableToPointInTimeRequest
import aws.sdk.kotlin.services.dynamodb.model.RestoreTableToPointInTimeResponse
import aws.sdk.kotlin.services.dynamodb.model.ScanRequest
import aws.sdk.kotlin.services.dynamodb.model.ScanResponse
import aws.sdk.kotlin.services.dynamodb.model.TagResourceRequest
import aws.sdk.kotlin.services.dynamodb.model.TagResourceResponse
import aws.sdk.kotlin.services.dynamodb.model.TransactGetItemsRequest
import aws.sdk.kotlin.services.dynamodb.model.TransactGetItemsResponse
import aws.sdk.kotlin.services.dynamodb.model.TransactWriteItemsRequest
import aws.sdk.kotlin.services.dynamodb.model.TransactWriteItemsResponse
import aws.sdk.kotlin.services.dynamodb.model.UntagResourceRequest
import aws.sdk.kotlin.services.dynamodb.model.UntagResourceResponse
import aws.sdk.kotlin.services.dynamodb.model.UpdateContinuousBackupsRequest
import aws.sdk.kotlin.services.dynamodb.model.UpdateContinuousBackupsResponse
import aws.sdk.kotlin.services.dynamodb.model.UpdateContributorInsightsRequest
import aws.sdk.kotlin.services.dynamodb.model.UpdateContributorInsightsResponse
import aws.sdk.kotlin.services.dynamodb.model.UpdateGlobalTableRequest
import aws.sdk.kotlin.services.dynamodb.model.UpdateGlobalTableResponse
import aws.sdk.kotlin.services.dynamodb.model.UpdateGlobalTableSettingsRequest
import aws.sdk.kotlin.services.dynamodb.model.UpdateGlobalTableSettingsResponse
import aws.sdk.kotlin.services.dynamodb.model.UpdateItemRequest
import aws.sdk.kotlin.services.dynamodb.model.UpdateItemResponse
import aws.sdk.kotlin.services.dynamodb.model.UpdateKinesisStreamingDestinationRequest
import aws.sdk.kotlin.services.dynamodb.model.UpdateKinesisStreamingDestinationResponse
import aws.sdk.kotlin.services.dynamodb.model.UpdateTableReplicaAutoScalingRequest
import aws.sdk.kotlin.services.dynamodb.model.UpdateTableReplicaAutoScalingResponse
import aws.sdk.kotlin.services.dynamodb.model.UpdateTableRequest
import aws.sdk.kotlin.services.dynamodb.model.UpdateTableResponse
import aws.sdk.kotlin.services.dynamodb.model.UpdateTimeToLiveRequest
import aws.sdk.kotlin.services.dynamodb.model.UpdateTimeToLiveResponse
import aws.smithy.kotlin.runtime.auth.awscredentials.CredentialsProvider
import aws.smithy.kotlin.runtime.auth.awscredentials.CredentialsProviderConfig
import aws.smithy.kotlin.runtime.awsprotocol.ClockSkewInterceptor
import aws.smithy.kotlin.runtime.client.AbstractSdkClientBuilder
import aws.smithy.kotlin.runtime.client.IdempotencyTokenConfig
import aws.smithy.kotlin.runtime.client.IdempotencyTokenProvider
import aws.smithy.kotlin.runtime.client.LogMode
import aws.smithy.kotlin.runtime.client.RetryClientConfig
import aws.smithy.kotlin.runtime.client.RetryStrategyClientConfig
import aws.smithy.kotlin.runtime.client.RetryStrategyClientConfigImpl
import aws.smithy.kotlin.runtime.client.SdkClient
import aws.smithy.kotlin.runtime.client.SdkClientConfig
import aws.smithy.kotlin.runtime.client.SdkClientFactory
import aws.smithy.kotlin.runtime.http.auth.AuthScheme
import aws.smithy.kotlin.runtime.http.auth.HttpAuthConfig
import aws.smithy.kotlin.runtime.http.config.HttpClientConfig
import aws.smithy.kotlin.runtime.http.config.HttpEngineConfig
import aws.smithy.kotlin.runtime.http.engine.HttpClientEngine
import aws.smithy.kotlin.runtime.http.engine.HttpEngineConfigImpl
import aws.smithy.kotlin.runtime.http.interceptors.HttpInterceptor
import aws.smithy.kotlin.runtime.net.url.Url
import aws.smithy.kotlin.runtime.retries.RetryStrategy
import aws.smithy.kotlin.runtime.retries.policy.RetryPolicy
import aws.smithy.kotlin.runtime.telemetry.Global
import aws.smithy.kotlin.runtime.telemetry.TelemetryConfig
import aws.smithy.kotlin.runtime.telemetry.TelemetryProvider
import aws.smithy.kotlin.runtime.util.LazyAsyncValue
import kotlin.collections.List
import kotlin.jvm.JvmStatic


public const val ServiceId: String = "DynamoDB"
public const val SdkVersion: String = "1.1.0"
public const val ServiceApiVersion: String = "2012-08-10"

/**
 * # Amazon DynamoDB
 * Amazon DynamoDB is a fully managed NoSQL database service that provides fast and predictable performance with seamless scalability. DynamoDB lets you offload the administrative burdens of operating and scaling a distributed database, so that you don't have to worry about hardware provisioning, setup and configuration, replication, software patching, or cluster scaling.
 *
 * With DynamoDB, you can create database tables that can store and retrieve any amount of data, and serve any level of request traffic. You can scale up or scale down your tables' throughput capacity without downtime or performance degradation, and use the Amazon Web Services Management Console to monitor resource utilization and performance metrics.
 *
 * DynamoDB automatically spreads the data and traffic for your tables over a sufficient number of servers to handle your throughput and storage requirements, while maintaining consistent and fast performance. All of your data is stored on solid state disks (SSDs) and automatically replicated across multiple Availability Zones in an Amazon Web Services Region, providing built-in high availability and data durability.
 */
public interface DynamoDbClient : SdkClient {
    /**
     * DynamoDbClient's configuration
     */
    public override val config: Config

    public companion object : AbstractAwsSdkClientFactory() {
        @JvmStatic
        override fun builder(): Builder = Builder()

        override suspend fun finalizeConfig(builder: Builder, sharedConfig: LazyAsyncValue, activeProfile: LazyAsyncValue) {
            builder.config.endpointUrl = builder.config.endpointUrl ?: resolveEndpointUrl(
                sharedConfig,
                "DynamoDb",
                "DYNAMODB",
                "dynamodb",
            )
            builder.config.interceptors.add(0, ClockSkewInterceptor())
        }
    }

    public class Builder internal constructor(): AbstractSdkClientBuilder() {
        override val config: Config.Builder = Config.Builder()
        override fun newClient(config: Config): DynamoDbClient = DefaultDynamoDbClient(config)
    }

    public class Config private constructor(builder: Builder) : AwsSdkClientConfig, CredentialsProviderConfig, HttpAuthConfig, HttpClientConfig, HttpEngineConfig by builder.buildHttpEngineConfig(), IdempotencyTokenConfig, RetryClientConfig, RetryStrategyClientConfig by builder.buildRetryStrategyClientConfig(), SdkClientConfig, TelemetryConfig {
        override val clientName: String = builder.clientName
        override val region: String? = builder.region
        override val authSchemes: kotlin.collections.List = builder.authSchemes
        override val credentialsProvider: CredentialsProvider = builder.credentialsProvider ?: DefaultChainCredentialsProvider(httpClient = httpClient, region = region).manage()
        public val endpointDiscoverer: DynamoDbEndpointDiscoverer? = builder.endpointDiscoverer
        public val endpointProvider: DynamoDbEndpointProvider = builder.endpointProvider ?: DefaultDynamoDbEndpointProvider()
        public val endpointUrl: Url? = builder.endpointUrl
        override val idempotencyTokenProvider: IdempotencyTokenProvider = builder.idempotencyTokenProvider ?: IdempotencyTokenProvider.Default
        override val interceptors: kotlin.collections.List = builder.interceptors
        override val logMode: LogMode = builder.logMode ?: LogMode.Default
        override val retryPolicy: RetryPolicy = builder.retryPolicy ?: AwsRetryPolicy.Default
        override val telemetryProvider: TelemetryProvider = builder.telemetryProvider ?: TelemetryProvider.Global
        override val useDualStack: Boolean = builder.useDualStack ?: false
        override val useFips: Boolean = builder.useFips ?: false
        override val applicationId: String? = builder.applicationId
        public val authSchemeProvider: DynamoDbAuthSchemeProvider = builder.authSchemeProvider ?: DefaultDynamoDbAuthSchemeProvider()
        public companion object {
            public inline operator fun invoke(block: Builder.() -> kotlin.Unit): Config = Builder().apply(block).build()
        }

        public fun toBuilder(): Builder = Builder().apply {
            clientName = [email protected]
            region = [email protected]
            authSchemes = [email protected]
            credentialsProvider = [email protected]
            endpointDiscoverer = [email protected]
            endpointProvider = [email protected]
            endpointUrl = [email protected]
            httpClient = [email protected]
            idempotencyTokenProvider = [email protected]
            interceptors = [email protected]()
            logMode = [email protected]
            retryPolicy = [email protected]
            retryStrategy = [email protected]
            telemetryProvider = [email protected]
            useDualStack = [email protected]
            useFips = [email protected]
            applicationId = [email protected]
            authSchemeProvider = [email protected]
        }

        public class Builder : AwsSdkClientConfig.Builder, CredentialsProviderConfig.Builder, HttpAuthConfig.Builder, HttpClientConfig.Builder, HttpEngineConfig.Builder by HttpEngineConfigImpl.BuilderImpl(), IdempotencyTokenConfig.Builder, RetryClientConfig.Builder, RetryStrategyClientConfig.Builder by RetryStrategyClientConfigImpl.BuilderImpl(), SdkClientConfig.Builder, TelemetryConfig.Builder {
            /**
             * A reader-friendly name for the client.
             */
            override var clientName: String = "DynamoDB"

            /**
             * The AWS region (e.g. `us-west-2`) to make requests to. See about AWS
             * [global infrastructure](https://aws.amazon.com/about-aws/global-infrastructure/regions_az/) for more
             * information
             */
            override var region: String? = null

            /**
             * Register new or override default [AuthScheme]s configured for this client. By default, the set
             * of auth schemes configured comes from the service model. An auth scheme configured explicitly takes
             * precedence over the defaults and can be used to customize identity resolution and signing for specific
             * authentication schemes.
             */
            override var authSchemes: kotlin.collections.List = emptyList()

            /**
             * The AWS credentials provider to use for authenticating requests. If not provided a
             * [aws.sdk.kotlin.runtime.auth.credentials.DefaultChainCredentialsProvider] instance will be used.
             * NOTE: The caller is responsible for managing the lifetime of the provider when set. The SDK
             * client will not close it when the client is closed.
             */
            override var credentialsProvider: CredentialsProvider? = null

            /**
             * The endpoint discoverer for this client, if applicable. By default, no endpoint
             * discovery is provided. To use endpoint discovery, set this to a valid
             * [DynamoDbEndpointDiscoverer] instance.
             */
            public var endpointDiscoverer: DynamoDbEndpointDiscoverer? = null

            /**
             * The endpoint provider used to determine where to make service requests. **This is an advanced config
             * option.**
             *
             * Endpoint resolution occurs as part of the workflow for every request made via the service client.
             *
             * The inputs to endpoint resolution are defined on a per-service basis (see [EndpointParameters]).
             */
            public var endpointProvider: DynamoDbEndpointProvider? = null

            /**
             * A custom endpoint to route requests to. The endpoint set here is passed to the configured
             * [endpointProvider], which may inspect and modify it as needed.
             *
             * Setting a custom endpointUrl should generally be preferred to overriding the [endpointProvider] and is
             * the recommended way to route requests to development or preview instances of a service.
             *
             * **This is an advanced config option.**
             */
            public var endpointUrl: Url? = null

            /**
             * Override the default idempotency token generator. SDK clients will generate tokens for members
             * that represent idempotent tokens when not explicitly set by the caller using this generator.
             */
            override var idempotencyTokenProvider: IdempotencyTokenProvider? = null

            /**
             * Add an [aws.smithy.kotlin.runtime.client.Interceptor] that will have access to read and modify
             * the request and response objects as they are processed by the SDK.
             * Interceptors added using this method are executed in the order they are configured and are always
             * later than any added automatically by the SDK.
             */
            override var interceptors: kotlin.collections.MutableList = kotlin.collections.mutableListOf()

            /**
             * Configure events that will be logged. By default clients will not output
             * raw requests or responses. Use this setting to opt-in to additional debug logging.
             *
             * This can be used to configure logging of requests, responses, retries, etc of SDK clients.
             *
             * **NOTE**: Logging of raw requests or responses may leak sensitive information! It may also have
             * performance considerations when dumping the request/response body. This is primarily a tool for
             * debug purposes.
             */
            override var logMode: LogMode? = null

            /**
             * The policy to use for evaluating operation results and determining whether/how to retry.
             */
            override var retryPolicy: RetryPolicy? = null

            /**
             * The telemetry provider used to instrument the SDK operations with. By default, the global telemetry
             * provider will be used.
             */
            override var telemetryProvider: TelemetryProvider? = null

            /**
             *            Flag to toggle whether to use dual-stack endpoints when making requests.
             *            See [https://docs.aws.amazon.com/sdkref/latest/guide/feature-endpoints.html] for more information.
             * `          Disabled by default.
             */
            override var useDualStack: Boolean? = null

            /**
             *            Flag to toggle whether to use [FIPS](https://aws.amazon.com/compliance/fips/) endpoints when making requests.
             * `          Disabled by default.
             */
            override var useFips: Boolean? = null

            /**
             * An optional application specific identifier.
             * When set it will be appended to the User-Agent header of every request in the form of: `app/{applicationId}`.
             * When not explicitly set, the value will be loaded from the following locations:
             *
             * - JVM System Property: `aws.userAgentAppId`
             * - Environment variable: `AWS_SDK_UA_APP_ID`
             * - Shared configuration profile attribute: `sdk_ua_app_id`
             *
             * See [shared configuration settings](https://docs.aws.amazon.com/sdkref/latest/guide/settings-reference.html)
             * reference for more information on environment variables and shared config settings.
             */
            override var applicationId: String? = null

            /**
             * Configure the provider used to resolve the authentication scheme to use for a particular operation.
             */
            public var authSchemeProvider: DynamoDbAuthSchemeProvider? = null

            override fun build(): Config = Config(this)
        }
    }

    /**
     * This operation allows you to perform batch reads or writes on data stored in DynamoDB, using PartiQL. Each read statement in a `BatchExecuteStatement` must specify an equality condition on all key attributes. This enforces that each `SELECT` statement in a batch returns at most a single item.
     *
     * The entire batch must consist of either read statements or write statements, you cannot mix both in one batch.
     *
     * A HTTP 200 response does not mean that all statements in the BatchExecuteStatement succeeded. Error details for individual statements can be found under the [Error](https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_BatchStatementResponse.html#DDB-Type-BatchStatementResponse-Error) field of the `BatchStatementResponse` for each statement.
     */
    public suspend fun batchExecuteStatement(input: BatchExecuteStatementRequest): BatchExecuteStatementResponse

    /**
     * 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, more than 1MB per partition is requested, 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](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/ErrorHandling.html#BatchOperations) 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` may retrieve 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](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/WorkingWithTables.html#CapacityUnitCalculations) in the *Amazon DynamoDB Developer Guide*.
     *
     * @sample aws.sdk.kotlin.services.dynamodb.samples.BatchGetItem.sample
     */
    public suspend fun batchGetItem(input: BatchGetItemRequest): BatchGetItemResponse

    /**
     * The `BatchWriteItem` operation puts or deletes multiple items in one or more tables. A single call to `BatchWriteItem` can transmit up to 16MB of data over the network, consisting of up to 25 item put or delete operations. While individual items can be up to 400 KB once stored, it's important to note that an item's representation might be greater than 400KB while being sent in DynamoDB's JSON format for the API call. For more details on this distinction, see [Naming Rules and Data Types](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/HowItWorks.NamingRulesDataTypes.html).
     *
     * `BatchWriteItem` cannot update items. If you perform a `BatchWriteItem` operation on an existing item, that item's values will be overwritten by the operation and it will appear like it was updated. To update items, we recommend you 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](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/ErrorHandling.html#Programming.Errors.BatchOperations) 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.
     *
     * @sample aws.sdk.kotlin.services.dynamodb.samples.BatchWriteItem.sample
     */
    public suspend fun batchWriteItem(input: BatchWriteItemRequest): BatchWriteItemResponse

    /**
     * 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
     */
    public suspend fun createBackup(input: CreateBackupRequest): CreateBackupResponse

    /**
     * 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.
     *
     * This operation only applies to [Version 2017.11.29 (Legacy)](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/globaltables.V1.html) of global tables. We recommend using [Version 2019.11.21 (Current)](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/globaltables.V2.html) when creating new global tables, as it provides greater flexibility, higher efficiency and consumes less write capacity than 2017.11.29 (Legacy). To determine which version you are using, see [Determining the version](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/globaltables.DetermineVersion.html). To update existing global tables from version 2017.11.29 (Legacy) to version 2019.11.21 (Current), see [ Updating global tables](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/V2globaltables_upgrade.html).
     *
     * 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).
     *
     *  If local secondary indexes are specified, then the following conditions must also be met:
     * +  The local secondary indexes must have the same name.
     * +  The local 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.
     */
    public suspend fun createGlobalTable(input: CreateGlobalTableRequest): CreateGlobalTableResponse

    /**
     * The `CreateTable` operation adds a new table to your account. In an Amazon Web Services 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.
     */
    public suspend fun createTable(input: CreateTableRequest): CreateTableResponse

    /**
     * Deletes an existing backup of a table.
     *
     * You can call `DeleteBackup` at a maximum rate of 10 times per second.
     */
    public suspend fun deleteBackup(input: DeleteBackupRequest): DeleteBackupResponse

    /**
     * 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.
     *
     * @sample aws.sdk.kotlin.services.dynamodb.samples.DeleteItem.sample
     */
    public suspend fun deleteItem(input: DeleteItemRequest): DeleteItemResponse

    /**
     * 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.
     *
     * This operation only applies to [Version 2019.11.21 (Current)](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/globaltables.V2.html) of global tables.
     *
     * 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.
     *
     * @sample aws.sdk.kotlin.services.dynamodb.samples.DeleteTable.sample
     */
    public suspend fun deleteTable(input: DeleteTableRequest): DeleteTableResponse

    /**
     * Describes an existing backup of a table.
     *
     * You can call `DescribeBackup` at a maximum rate of 10 times per second.
     */
    public suspend fun describeBackup(input: DescribeBackupRequest): DescribeBackupResponse

    /**
     * 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.
     */
    public suspend fun describeContinuousBackups(input: DescribeContinuousBackupsRequest): DescribeContinuousBackupsResponse

    /**
     * Returns information about contributor insights for a given table or global secondary index.
     */
    public suspend fun describeContributorInsights(input: DescribeContributorInsightsRequest): DescribeContributorInsightsResponse

    /**
     * Returns the regional endpoint information. For more information on policy permissions, please see [Internetwork traffic privacy](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/inter-network-traffic-privacy.html#inter-network-traffic-DescribeEndpoints).
     */
    public suspend fun describeEndpoints(input: DescribeEndpointsRequest = DescribeEndpointsRequest { }): DescribeEndpointsResponse

    /**
     * Describes an existing table export.
     */
    public suspend fun describeExport(input: DescribeExportRequest): DescribeExportResponse

    /**
     * Returns information about the specified global table.
     *
     * This operation only applies to [Version 2017.11.29 (Legacy)](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/globaltables.V1.html) of global tables. We recommend using [Version 2019.11.21 (Current)](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/globaltables.V2.html) when creating new global tables, as it provides greater flexibility, higher efficiency and consumes less write capacity than 2017.11.29 (Legacy). To determine which version you are using, see [Determining the version](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/globaltables.DetermineVersion.html). To update existing global tables from version 2017.11.29 (Legacy) to version 2019.11.21 (Current), see [ Updating global tables](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/V2globaltables_upgrade.html).
     */
    public suspend fun describeGlobalTable(input: DescribeGlobalTableRequest): DescribeGlobalTableResponse

    /**
     * Describes Region-specific settings for a global table.
     *
     * This operation only applies to [Version 2017.11.29 (Legacy)](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/globaltables.V1.html) of global tables. We recommend using [Version 2019.11.21 (Current)](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/globaltables.V2.html) when creating new global tables, as it provides greater flexibility, higher efficiency and consumes less write capacity than 2017.11.29 (Legacy). To determine which version you are using, see [Determining the version](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/globaltables.DetermineVersion.html). To update existing global tables from version 2017.11.29 (Legacy) to version 2019.11.21 (Current), see [ Updating global tables](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/V2globaltables_upgrade.html).
     */
    public suspend fun describeGlobalTableSettings(input: DescribeGlobalTableSettingsRequest): DescribeGlobalTableSettingsResponse

    /**
     * Represents the properties of the import.
     */
    public suspend fun describeImport(input: DescribeImportRequest): DescribeImportResponse

    /**
     * Returns information about the status of Kinesis streaming.
     */
    public suspend fun describeKinesisStreamingDestination(input: DescribeKinesisStreamingDestinationRequest): DescribeKinesisStreamingDestinationResponse

    /**
     * Returns the current provisioned-capacity quotas for your Amazon Web Services 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 Amazon Web Services account, the account has initial quotas on the maximum read capacity units and write capacity units that you can provision across all of your DynamoDB tables in a given Region. Also, there are per-table quotas that apply when you create a table there. For more information, see [Service, Account, and Table Quotas](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Limits.html) page in the *Amazon DynamoDB Developer Guide*.
     *
     * Although you can increase these quotas by filing a case at [Amazon Web Services Support Center](https://console.aws.amazon.com/support/home#/), obtaining the increase is not instantaneous. The `DescribeLimits` action lets you write code to compare the capacity you are currently using to those quotas imposed by your account so that you have enough time to apply for an increase before you hit a quota.
     *
     * For example, you could use one of the Amazon Web Services SDKs to do the following:
     * + Call `DescribeLimits` for a particular Region to obtain your current account quotas on provisioned capacity there.
     * + Create a variable to hold the aggregate read capacity units provisioned for all your tables in that Region, and one to hold the aggregate write capacity units. Zero them both.
     * + Call `ListTables` to obtain a list of all your DynamoDB tables.
     * + For each table name listed by `ListTables`, do the following:
     *    + Call `DescribeTable` with the table name.
     *    + Use the data returned by `DescribeTable` to add the read capacity units and write capacity units provisioned for the table itself to your variables.
     *    + If the table has one or more global secondary indexes (GSIs), loop over these GSIs and add their provisioned capacity values to your variables as well.
     * + Report the account quotas for that Region returned by `DescribeLimits`, along with the total current provisioned capacity levels you have calculated.
     *
     * This will let you see whether you are getting close to your account-level quotas.
     *
     * The per-table quotas apply only when you are creating a new table. They restrict the sum of the provisioned capacity of the new table itself and all its global secondary indexes.
     *
     * For existing tables and their GSIs, DynamoDB doesn't let you increase provisioned capacity extremely rapidly, but the only quota that applies is that the aggregate provisioned capacity over all your tables and GSIs cannot exceed either of the per-account quotas.
     *
     * `DescribeLimits` should only be called periodically. You can expect throttling errors if you call it more than once in a minute.
     *
     * The `DescribeLimits` Request element has no content.
     *
     * @sample aws.sdk.kotlin.services.dynamodb.samples.DescribeLimits.sample
     */
    public suspend fun describeLimits(input: DescribeLimitsRequest = DescribeLimitsRequest { }): DescribeLimitsResponse

    /**
     * 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.
     *
     * This operation only applies to [Version 2019.11.21 (Current)](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/globaltables.V2.html) of global tables.
     *
     * 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.
     */
    public suspend fun describeTable(input: DescribeTableRequest): DescribeTableResponse

    /**
     * Describes auto scaling settings across replicas of the global table at once.
     *
     * This operation only applies to [Version 2019.11.21 (Current)](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/globaltables.V2.html) of global tables.
     */
    public suspend fun describeTableReplicaAutoScaling(input: DescribeTableReplicaAutoScalingRequest): DescribeTableReplicaAutoScalingResponse

    /**
     * Gives a description of the Time to Live (TTL) status on the specified table.
     */
    public suspend fun describeTimeToLive(input: DescribeTimeToLiveRequest): DescribeTimeToLiveResponse

    /**
     * Stops replication from the DynamoDB table to the Kinesis data stream. This is done without deleting either of the resources.
     */
    public suspend fun disableKinesisStreamingDestination(input: DisableKinesisStreamingDestinationRequest): DisableKinesisStreamingDestinationResponse

    /**
     * Starts table data replication to the specified Kinesis data stream at a timestamp chosen during the enable workflow. If this operation doesn't return results immediately, use DescribeKinesisStreamingDestination to check if streaming to the Kinesis data stream is ACTIVE.
     */
    public suspend fun enableKinesisStreamingDestination(input: EnableKinesisStreamingDestinationRequest): EnableKinesisStreamingDestinationResponse

    /**
     * This operation allows you to perform reads and singleton writes on data stored in DynamoDB, using PartiQL.
     *
     * For PartiQL reads (`SELECT` statement), if the total number of processed items exceeds the maximum dataset size limit of 1 MB, the read stops and results are returned to the user as a `LastEvaluatedKey` value to continue the read in a subsequent operation. If the filter criteria in `WHERE` clause does not match any data, the read will return an empty result set.
     *
     * A single `SELECT` statement response can return up to the maximum number of items (if using the Limit parameter) or a maximum of 1 MB of data (and then apply any filtering to the results using `WHERE` clause). If `LastEvaluatedKey` is present in the response, you need to paginate the result set. If `NextToken` is present, you need to paginate the result set and include `NextToken`.
     */
    public suspend fun executeStatement(input: ExecuteStatementRequest): ExecuteStatementResponse

    /**
     * This operation allows you to perform transactional reads or writes on data stored in DynamoDB, using PartiQL.
     *
     * The entire transaction must consist of either read statements or write statements, you cannot mix both in one transaction. The EXISTS function is an exception and can be used to check the condition of specific attributes of the item in a similar manner to `ConditionCheck` in the [TransactWriteItems](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/transaction-apis.html#transaction-apis-txwriteitems) API.
     */
    public suspend fun executeTransaction(input: ExecuteTransactionRequest): ExecuteTransactionResponse

    /**
     * Exports table data to an S3 bucket. The table must have point in time recovery enabled, and you can export data from any time within the point in time recovery window.
     */
    public suspend fun exportTableToPointInTime(input: ExportTableToPointInTimeRequest): ExportTableToPointInTimeResponse

    /**
     * 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.
     *
     * @sample aws.sdk.kotlin.services.dynamodb.samples.GetItem.sample
     */
    public suspend fun getItem(input: GetItemRequest): GetItemResponse

    /**
     * Imports table data from an S3 bucket.
     */
    public suspend fun importTable(input: ImportTableRequest): ImportTableResponse

    /**
     * List DynamoDB backups that are associated with an Amazon Web Services account and weren't made with Amazon Web Services Backup. To list these 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 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 boundaries are for the time at which the original backup was requested.
     *
     * You can call `ListBackups` a maximum of five times per second.
     *
     * If you want to retrieve the complete list of backups made with Amazon Web Services Backup, use the [Amazon Web Services Backup list API.](https://docs.aws.amazon.com/aws-backup/latest/devguide/API_ListBackupJobs.html)
     */
    public suspend fun listBackups(input: ListBackupsRequest = ListBackupsRequest { }): ListBackupsResponse

    /**
     * Returns a list of ContributorInsightsSummary for a table and all its global secondary indexes.
     */
    public suspend fun listContributorInsights(input: ListContributorInsightsRequest = ListContributorInsightsRequest { }): ListContributorInsightsResponse

    /**
     * Lists completed exports within the past 90 days.
     */
    public suspend fun listExports(input: ListExportsRequest = ListExportsRequest { }): ListExportsResponse

    /**
     * Lists all global tables that have a replica in the specified Region.
     *
     * This operation only applies to [Version 2017.11.29 (Legacy)](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/globaltables.V1.html) of global tables. We recommend using [Version 2019.11.21 (Current)](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/globaltables.V2.html) when creating new global tables, as it provides greater flexibility, higher efficiency and consumes less write capacity than 2017.11.29 (Legacy). To determine which version you are using, see [Determining the version](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/globaltables.DetermineVersion.html). To update existing global tables from version 2017.11.29 (Legacy) to version 2019.11.21 (Current), see [ Updating global tables](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/V2globaltables_upgrade.html).
     */
    public suspend fun listGlobalTables(input: ListGlobalTablesRequest = ListGlobalTablesRequest { }): ListGlobalTablesResponse

    /**
     * Lists completed imports within the past 90 days.
     */
    public suspend fun listImports(input: ListImportsRequest = ListImportsRequest { }): ListImportsResponse

    /**
     * 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.
     *
     * @sample aws.sdk.kotlin.services.dynamodb.samples.ListTables.sample
     */
    public suspend fun listTables(input: ListTablesRequest = ListTablesRequest { }): ListTablesResponse

    /**
     * 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](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Tagging.html) in the *Amazon DynamoDB Developer Guide*.
     */
    public suspend fun listTagsOfResource(input: ListTagsOfResourceRequest): ListTagsOfResourceResponse

    /**
     * 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.
     *
     * When you add an item, the primary key attributes are the only required attributes.
     *
     * Empty String and Binary attribute values are allowed. Attribute values of type String and Binary must have a length greater than zero if the attribute is used as a key attribute for a table or index. Set type attributes cannot be empty.
     *
     * Invalid 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](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/WorkingWithItems.html) in the *Amazon DynamoDB Developer Guide*.
     *
     * @sample aws.sdk.kotlin.services.dynamodb.samples.PutItem.sample
     */
    public suspend fun putItem(input: PutItemRequest): PutItemResponse

    /**
     * You must provide the name of the partition key attribute and a single value for that attribute. `Query` returns all items with that partition key value. Optionally, you can provide a sort key attribute and use a comparison operator to refine the search results.
     *
     * 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](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Query.html#Query.Pagination) 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.
     *
     * @sample aws.sdk.kotlin.services.dynamodb.samples.Query.sample
     */
    public suspend fun query(input: QueryRequest): QueryResponse

    /**
     * Creates a new table from an existing backup. Any number of users can execute up to 50 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
     */
    public suspend fun restoreTableFromBackup(input: RestoreTableFromBackupRequest): RestoreTableFromBackupResponse

    /**
     * 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 50 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
     */
    public suspend fun restoreTableToPointInTime(input: RestoreTableToPointInTimeRequest): RestoreTableToPointInTimeResponse

    /**
     * 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 size of scanned items exceeds the maximum dataset size limit of 1 MB, the scan completes and results are returned to the user. The `LastEvaluatedKey` value is also returned and the requestor can use the `LastEvaluatedKey` to continue the scan in a subsequent operation. Each scan response also includes number of items that were scanned (ScannedCount) as part of the request. If using a `FilterExpression`, a scan result can result in no items meeting the criteria and the `Count` will result in zero. If you did not use a `FilterExpression` in the scan request, then `Count` is the same as `ScannedCount`.
     *
     * `Count` and `ScannedCount` only return the count of items specific to a single scan request and, unless the table is less than 1MB, do not represent the total number of items in the table.
     *
     * A single `Scan` operation first reads up to the maximum number of items set (if using the `Limit` parameter) or a maximum of 1 MB of data and then applies any filtering to the results if a `FilterExpression` is provided. If `LastEvaluatedKey` is present in the response, pagination is required to complete the full table scan. For more information, see [Paginating the Results](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Scan.html#Scan.Pagination) 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](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Scan.html#Scan.ParallelScan) in the *Amazon DynamoDB Developer Guide*.
     *
     * By default, a `Scan` uses eventually consistent reads when accessing the items in a table. Therefore, the results from an eventually consistent `Scan` may not include the latest item changes at the time the scan iterates through each item in the table. If you require a strongly consistent read of each item as the scan iterates through the items in the table, you can set the `ConsistentRead` parameter to true. Strong consistency only relates to the consistency of the read at the item level.
     *
     *  DynamoDB does not provide snapshot isolation for a scan operation when the `ConsistentRead` parameter is set to true. Thus, a DynamoDB scan operation does not guarantee that all reads in a scan see a consistent snapshot of the table when the scan operation was requested.
     *
     * @sample aws.sdk.kotlin.services.dynamodb.samples.Scan.sample
     */
    public suspend fun scan(input: ScanRequest): ScanResponse

    /**
     * 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](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Tagging.html) in the *Amazon DynamoDB Developer Guide*.
     */
    public suspend fun tagResource(input: TagResourceRequest): TagResourceResponse

    /**
     * `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 100 `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 Amazon Web Services account or Region. The aggregate size of the items in the transaction cannot exceed 4 MB.
     *
     * 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 exceeded 4 MB.
     */
    public suspend fun transactGetItems(input: TransactGetItemsRequest): TransactGetItemsResponse

    /**
     * `TransactWriteItems` is a synchronous write operation that groups up to 100 action requests. These actions can target items in different tables, but not in different Amazon Web Services 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.
     *
     * 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` — 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` — 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` — 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` — 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.
     */
    public suspend fun transactWriteItems(input: TransactWriteItemsRequest): TransactWriteItemsResponse

    /**
     * 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](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Tagging.html) in the *Amazon DynamoDB Developer Guide*.
     */
    public suspend fun untagResource(input: UntagResourceRequest): UntagResourceResponse

    /**
     * `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.
     */
    public suspend fun updateContinuousBackups(input: UpdateContinuousBackupsRequest): UpdateContinuousBackupsResponse

    /**
     * Updates the status for contributor insights for a specific table or index. CloudWatch Contributor Insights for DynamoDB graphs display the partition key and (if applicable) sort key of frequently accessed items and frequently throttled items in plaintext. If you require the use of Amazon Web Services Key Management Service (KMS) to encrypt this table’s partition key and sort key data with an Amazon Web Services managed key or customer managed key, you should not enable CloudWatch Contributor Insights for DynamoDB for this table.
     */
    public suspend fun updateContributorInsights(input: UpdateContributorInsightsRequest): UpdateContributorInsightsResponse

    /**
     * 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.
     *
     * This operation only applies to [Version 2017.11.29 (Legacy)](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/globaltables.V1.html) of global tables. We recommend using [Version 2019.11.21 (Current)](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/globaltables.V2.html) when creating new global tables, as it provides greater flexibility, higher efficiency and consumes less write capacity than 2017.11.29 (Legacy). To determine which version you are using, see [Determining the version](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/globaltables.DetermineVersion.html). To update existing global tables from version 2017.11.29 (Legacy) to version 2019.11.21 (Current), see [ Updating global tables](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/V2globaltables_upgrade.html).
     *
     *  This operation only applies to [Version 2017.11.29](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/globaltables.V1.html) of global tables. If you are using global tables [Version 2019.11.21](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/globaltables.V2.html) you can use [UpdateTable](https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_UpdateTable.html) instead.
     *
     *  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.
     */
    public suspend fun updateGlobalTable(input: UpdateGlobalTableRequest): UpdateGlobalTableResponse

    /**
     * Updates settings for a global table.
     *
     * This operation only applies to [Version 2017.11.29 (Legacy)](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/globaltables.V1.html) of global tables. We recommend using [Version 2019.11.21 (Current)](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/globaltables.V2.html) when creating new global tables, as it provides greater flexibility, higher efficiency and consumes less write capacity than 2017.11.29 (Legacy). To determine which version you are using, see [Determining the version](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/globaltables.DetermineVersion.html). To update existing global tables from version 2017.11.29 (Legacy) to version 2019.11.21 (Current), see [ Updating global tables](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/V2globaltables_upgrade.html).
     */
    public suspend fun updateGlobalTableSettings(input: UpdateGlobalTableSettingsRequest): UpdateGlobalTableSettingsResponse

    /**
     * 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.
     *
     * @sample aws.sdk.kotlin.services.dynamodb.samples.UpdateItem.sample
     */
    public suspend fun updateItem(input: UpdateItemRequest): UpdateItemResponse

    /**
     * The command to update the Kinesis stream destination.
     */
    public suspend fun updateKinesisStreamingDestination(input: UpdateKinesisStreamingDestinationRequest): UpdateKinesisStreamingDestinationResponse

    /**
     * Modifies the provisioned throughput settings, global secondary indexes, or DynamoDB Streams settings for a given table.
     *
     * This operation only applies to [Version 2019.11.21 (Current)](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/globaltables.V2.html) of global tables.
     *
     * You can only perform one of the following operations at once:
     * + Modify the provisioned throughput settings of 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's executing, the table status changes from `ACTIVE` to `UPDATING`. While it's `UPDATING`, you can't issue another `UpdateTable` request on the base table nor any replicas. When the table returns to the `ACTIVE` state, the `UpdateTable` operation is complete.
     */
    public suspend fun updateTable(input: UpdateTableRequest): UpdateTableResponse

    /**
     * Updates auto scaling settings on your global tables at once.
     *
     * This operation only applies to [Version 2019.11.21 (Current)](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/globaltables.V2.html) of global tables.
     */
    public suspend fun updateTableReplicaAutoScaling(input: UpdateTableReplicaAutoScalingRequest): UpdateTableReplicaAutoScalingResponse

    /**
     * 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](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/TTL.html) in the Amazon DynamoDB Developer Guide.
     */
    public suspend fun updateTimeToLive(input: UpdateTimeToLiveRequest): UpdateTimeToLiveResponse
}

/**
 * Create a copy of the client with one or more configuration values overridden.
 * This method allows the caller to perform scoped config overrides for one or more client operations.
 *
 * Any resources created on your behalf will be shared between clients, and will only be closed when ALL clients using them are closed.
 * If you provide a resource (e.g. [HttpClientEngine]) to the SDK, you are responsible for managing the lifetime of that resource.
 */
public fun DynamoDbClient.withConfig(block: DynamoDbClient.Config.Builder.() -> Unit): DynamoDbClient {
    val newConfig = config.toBuilder().apply(block).build()
    return DefaultDynamoDbClient(newConfig)
}

/**
 * This operation allows you to perform batch reads or writes on data stored in DynamoDB, using PartiQL. Each read statement in a `BatchExecuteStatement` must specify an equality condition on all key attributes. This enforces that each `SELECT` statement in a batch returns at most a single item.
 *
 * The entire batch must consist of either read statements or write statements, you cannot mix both in one batch.
 *
 * A HTTP 200 response does not mean that all statements in the BatchExecuteStatement succeeded. Error details for individual statements can be found under the [Error](https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_BatchStatementResponse.html#DDB-Type-BatchStatementResponse-Error) field of the `BatchStatementResponse` for each statement.
 */
public suspend inline fun DynamoDbClient.batchExecuteStatement(crossinline block: BatchExecuteStatementRequest.Builder.() -> Unit): BatchExecuteStatementResponse = batchExecuteStatement(BatchExecuteStatementRequest.Builder().apply(block).build())

/**
 * 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, more than 1MB per partition is requested, 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](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/ErrorHandling.html#BatchOperations) 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` may retrieve 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](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/WorkingWithTables.html#CapacityUnitCalculations) in the *Amazon DynamoDB Developer Guide*.
 *
 * @sample aws.sdk.kotlin.services.dynamodb.samples.BatchGetItem.sample
 */
public suspend inline fun DynamoDbClient.batchGetItem(crossinline block: BatchGetItemRequest.Builder.() -> Unit): BatchGetItemResponse = batchGetItem(BatchGetItemRequest.Builder().apply(block).build())

/**
 * The `BatchWriteItem` operation puts or deletes multiple items in one or more tables. A single call to `BatchWriteItem` can transmit up to 16MB of data over the network, consisting of up to 25 item put or delete operations. While individual items can be up to 400 KB once stored, it's important to note that an item's representation might be greater than 400KB while being sent in DynamoDB's JSON format for the API call. For more details on this distinction, see [Naming Rules and Data Types](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/HowItWorks.NamingRulesDataTypes.html).
 *
 * `BatchWriteItem` cannot update items. If you perform a `BatchWriteItem` operation on an existing item, that item's values will be overwritten by the operation and it will appear like it was updated. To update items, we recommend you 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](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/ErrorHandling.html#Programming.Errors.BatchOperations) 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.
 *
 * @sample aws.sdk.kotlin.services.dynamodb.samples.BatchWriteItem.sample
 */
public suspend inline fun DynamoDbClient.batchWriteItem(crossinline block: BatchWriteItemRequest.Builder.() -> Unit): BatchWriteItemResponse = batchWriteItem(BatchWriteItemRequest.Builder().apply(block).build())

/**
 * 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
 */
public suspend inline fun DynamoDbClient.createBackup(crossinline block: CreateBackupRequest.Builder.() -> Unit): CreateBackupResponse = createBackup(CreateBackupRequest.Builder().apply(block).build())

/**
 * 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.
 *
 * This operation only applies to [Version 2017.11.29 (Legacy)](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/globaltables.V1.html) of global tables. We recommend using [Version 2019.11.21 (Current)](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/globaltables.V2.html) when creating new global tables, as it provides greater flexibility, higher efficiency and consumes less write capacity than 2017.11.29 (Legacy). To determine which version you are using, see [Determining the version](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/globaltables.DetermineVersion.html). To update existing global tables from version 2017.11.29 (Legacy) to version 2019.11.21 (Current), see [ Updating global tables](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/V2globaltables_upgrade.html).
 *
 * 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).
 *
 *  If local secondary indexes are specified, then the following conditions must also be met:
 * +  The local secondary indexes must have the same name.
 * +  The local 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.
 */
public suspend inline fun DynamoDbClient.createGlobalTable(crossinline block: CreateGlobalTableRequest.Builder.() -> Unit): CreateGlobalTableResponse = createGlobalTable(CreateGlobalTableRequest.Builder().apply(block).build())

/**
 * The `CreateTable` operation adds a new table to your account. In an Amazon Web Services 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.
 */
public suspend inline fun DynamoDbClient.createTable(crossinline block: CreateTableRequest.Builder.() -> Unit): CreateTableResponse = createTable(CreateTableRequest.Builder().apply(block).build())

/**
 * Deletes an existing backup of a table.
 *
 * You can call `DeleteBackup` at a maximum rate of 10 times per second.
 */
public suspend inline fun DynamoDbClient.deleteBackup(crossinline block: DeleteBackupRequest.Builder.() -> Unit): DeleteBackupResponse = deleteBackup(DeleteBackupRequest.Builder().apply(block).build())

/**
 * 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.
 *
 * @sample aws.sdk.kotlin.services.dynamodb.samples.DeleteItem.sample
 */
public suspend inline fun DynamoDbClient.deleteItem(crossinline block: DeleteItemRequest.Builder.() -> Unit): DeleteItemResponse = deleteItem(DeleteItemRequest.Builder().apply(block).build())

/**
 * 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.
 *
 * This operation only applies to [Version 2019.11.21 (Current)](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/globaltables.V2.html) of global tables.
 *
 * 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.
 *
 * @sample aws.sdk.kotlin.services.dynamodb.samples.DeleteTable.sample
 */
public suspend inline fun DynamoDbClient.deleteTable(crossinline block: DeleteTableRequest.Builder.() -> Unit): DeleteTableResponse = deleteTable(DeleteTableRequest.Builder().apply(block).build())

/**
 * Describes an existing backup of a table.
 *
 * You can call `DescribeBackup` at a maximum rate of 10 times per second.
 */
public suspend inline fun DynamoDbClient.describeBackup(crossinline block: DescribeBackupRequest.Builder.() -> Unit): DescribeBackupResponse = describeBackup(DescribeBackupRequest.Builder().apply(block).build())

/**
 * 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.
 */
public suspend inline fun DynamoDbClient.describeContinuousBackups(crossinline block: DescribeContinuousBackupsRequest.Builder.() -> Unit): DescribeContinuousBackupsResponse = describeContinuousBackups(DescribeContinuousBackupsRequest.Builder().apply(block).build())

/**
 * Returns information about contributor insights for a given table or global secondary index.
 */
public suspend inline fun DynamoDbClient.describeContributorInsights(crossinline block: DescribeContributorInsightsRequest.Builder.() -> Unit): DescribeContributorInsightsResponse = describeContributorInsights(DescribeContributorInsightsRequest.Builder().apply(block).build())

/**
 * Returns the regional endpoint information. For more information on policy permissions, please see [Internetwork traffic privacy](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/inter-network-traffic-privacy.html#inter-network-traffic-DescribeEndpoints).
 */
public suspend inline fun DynamoDbClient.describeEndpoints(crossinline block: DescribeEndpointsRequest.Builder.() -> Unit): DescribeEndpointsResponse = describeEndpoints(DescribeEndpointsRequest.Builder().apply(block).build())

/**
 * Describes an existing table export.
 */
public suspend inline fun DynamoDbClient.describeExport(crossinline block: DescribeExportRequest.Builder.() -> Unit): DescribeExportResponse = describeExport(DescribeExportRequest.Builder().apply(block).build())

/**
 * Returns information about the specified global table.
 *
 * This operation only applies to [Version 2017.11.29 (Legacy)](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/globaltables.V1.html) of global tables. We recommend using [Version 2019.11.21 (Current)](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/globaltables.V2.html) when creating new global tables, as it provides greater flexibility, higher efficiency and consumes less write capacity than 2017.11.29 (Legacy). To determine which version you are using, see [Determining the version](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/globaltables.DetermineVersion.html). To update existing global tables from version 2017.11.29 (Legacy) to version 2019.11.21 (Current), see [ Updating global tables](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/V2globaltables_upgrade.html).
 */
public suspend inline fun DynamoDbClient.describeGlobalTable(crossinline block: DescribeGlobalTableRequest.Builder.() -> Unit): DescribeGlobalTableResponse = describeGlobalTable(DescribeGlobalTableRequest.Builder().apply(block).build())

/**
 * Describes Region-specific settings for a global table.
 *
 * This operation only applies to [Version 2017.11.29 (Legacy)](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/globaltables.V1.html) of global tables. We recommend using [Version 2019.11.21 (Current)](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/globaltables.V2.html) when creating new global tables, as it provides greater flexibility, higher efficiency and consumes less write capacity than 2017.11.29 (Legacy). To determine which version you are using, see [Determining the version](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/globaltables.DetermineVersion.html). To update existing global tables from version 2017.11.29 (Legacy) to version 2019.11.21 (Current), see [ Updating global tables](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/V2globaltables_upgrade.html).
 */
public suspend inline fun DynamoDbClient.describeGlobalTableSettings(crossinline block: DescribeGlobalTableSettingsRequest.Builder.() -> Unit): DescribeGlobalTableSettingsResponse = describeGlobalTableSettings(DescribeGlobalTableSettingsRequest.Builder().apply(block).build())

/**
 * Represents the properties of the import.
 */
public suspend inline fun DynamoDbClient.describeImport(crossinline block: DescribeImportRequest.Builder.() -> Unit): DescribeImportResponse = describeImport(DescribeImportRequest.Builder().apply(block).build())

/**
 * Returns information about the status of Kinesis streaming.
 */
public suspend inline fun DynamoDbClient.describeKinesisStreamingDestination(crossinline block: DescribeKinesisStreamingDestinationRequest.Builder.() -> Unit): DescribeKinesisStreamingDestinationResponse = describeKinesisStreamingDestination(DescribeKinesisStreamingDestinationRequest.Builder().apply(block).build())

/**
 * Returns the current provisioned-capacity quotas for your Amazon Web Services 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 Amazon Web Services account, the account has initial quotas on the maximum read capacity units and write capacity units that you can provision across all of your DynamoDB tables in a given Region. Also, there are per-table quotas that apply when you create a table there. For more information, see [Service, Account, and Table Quotas](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Limits.html) page in the *Amazon DynamoDB Developer Guide*.
 *
 * Although you can increase these quotas by filing a case at [Amazon Web Services Support Center](https://console.aws.amazon.com/support/home#/), obtaining the increase is not instantaneous. The `DescribeLimits` action lets you write code to compare the capacity you are currently using to those quotas imposed by your account so that you have enough time to apply for an increase before you hit a quota.
 *
 * For example, you could use one of the Amazon Web Services SDKs to do the following:
 * + Call `DescribeLimits` for a particular Region to obtain your current account quotas on provisioned capacity there.
 * + Create a variable to hold the aggregate read capacity units provisioned for all your tables in that Region, and one to hold the aggregate write capacity units. Zero them both.
 * + Call `ListTables` to obtain a list of all your DynamoDB tables.
 * + For each table name listed by `ListTables`, do the following:
 *    + Call `DescribeTable` with the table name.
 *    + Use the data returned by `DescribeTable` to add the read capacity units and write capacity units provisioned for the table itself to your variables.
 *    + If the table has one or more global secondary indexes (GSIs), loop over these GSIs and add their provisioned capacity values to your variables as well.
 * + Report the account quotas for that Region returned by `DescribeLimits`, along with the total current provisioned capacity levels you have calculated.
 *
 * This will let you see whether you are getting close to your account-level quotas.
 *
 * The per-table quotas apply only when you are creating a new table. They restrict the sum of the provisioned capacity of the new table itself and all its global secondary indexes.
 *
 * For existing tables and their GSIs, DynamoDB doesn't let you increase provisioned capacity extremely rapidly, but the only quota that applies is that the aggregate provisioned capacity over all your tables and GSIs cannot exceed either of the per-account quotas.
 *
 * `DescribeLimits` should only be called periodically. You can expect throttling errors if you call it more than once in a minute.
 *
 * The `DescribeLimits` Request element has no content.
 *
 * @sample aws.sdk.kotlin.services.dynamodb.samples.DescribeLimits.sample
 */
public suspend inline fun DynamoDbClient.describeLimits(crossinline block: DescribeLimitsRequest.Builder.() -> Unit): DescribeLimitsResponse = describeLimits(DescribeLimitsRequest.Builder().apply(block).build())

/**
 * 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.
 *
 * This operation only applies to [Version 2019.11.21 (Current)](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/globaltables.V2.html) of global tables.
 *
 * 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.
 */
public suspend inline fun DynamoDbClient.describeTable(crossinline block: DescribeTableRequest.Builder.() -> Unit): DescribeTableResponse = describeTable(DescribeTableRequest.Builder().apply(block).build())

/**
 * Describes auto scaling settings across replicas of the global table at once.
 *
 * This operation only applies to [Version 2019.11.21 (Current)](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/globaltables.V2.html) of global tables.
 */
public suspend inline fun DynamoDbClient.describeTableReplicaAutoScaling(crossinline block: DescribeTableReplicaAutoScalingRequest.Builder.() -> Unit): DescribeTableReplicaAutoScalingResponse = describeTableReplicaAutoScaling(DescribeTableReplicaAutoScalingRequest.Builder().apply(block).build())

/**
 * Gives a description of the Time to Live (TTL) status on the specified table.
 */
public suspend inline fun DynamoDbClient.describeTimeToLive(crossinline block: DescribeTimeToLiveRequest.Builder.() -> Unit): DescribeTimeToLiveResponse = describeTimeToLive(DescribeTimeToLiveRequest.Builder().apply(block).build())

/**
 * Stops replication from the DynamoDB table to the Kinesis data stream. This is done without deleting either of the resources.
 */
public suspend inline fun DynamoDbClient.disableKinesisStreamingDestination(crossinline block: DisableKinesisStreamingDestinationRequest.Builder.() -> Unit): DisableKinesisStreamingDestinationResponse = disableKinesisStreamingDestination(DisableKinesisStreamingDestinationRequest.Builder().apply(block).build())

/**
 * Starts table data replication to the specified Kinesis data stream at a timestamp chosen during the enable workflow. If this operation doesn't return results immediately, use DescribeKinesisStreamingDestination to check if streaming to the Kinesis data stream is ACTIVE.
 */
public suspend inline fun DynamoDbClient.enableKinesisStreamingDestination(crossinline block: EnableKinesisStreamingDestinationRequest.Builder.() -> Unit): EnableKinesisStreamingDestinationResponse = enableKinesisStreamingDestination(EnableKinesisStreamingDestinationRequest.Builder().apply(block).build())

/**
 * This operation allows you to perform reads and singleton writes on data stored in DynamoDB, using PartiQL.
 *
 * For PartiQL reads (`SELECT` statement), if the total number of processed items exceeds the maximum dataset size limit of 1 MB, the read stops and results are returned to the user as a `LastEvaluatedKey` value to continue the read in a subsequent operation. If the filter criteria in `WHERE` clause does not match any data, the read will return an empty result set.
 *
 * A single `SELECT` statement response can return up to the maximum number of items (if using the Limit parameter) or a maximum of 1 MB of data (and then apply any filtering to the results using `WHERE` clause). If `LastEvaluatedKey` is present in the response, you need to paginate the result set. If `NextToken` is present, you need to paginate the result set and include `NextToken`.
 */
public suspend inline fun DynamoDbClient.executeStatement(crossinline block: ExecuteStatementRequest.Builder.() -> Unit): ExecuteStatementResponse = executeStatement(ExecuteStatementRequest.Builder().apply(block).build())

/**
 * This operation allows you to perform transactional reads or writes on data stored in DynamoDB, using PartiQL.
 *
 * The entire transaction must consist of either read statements or write statements, you cannot mix both in one transaction. The EXISTS function is an exception and can be used to check the condition of specific attributes of the item in a similar manner to `ConditionCheck` in the [TransactWriteItems](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/transaction-apis.html#transaction-apis-txwriteitems) API.
 */
public suspend inline fun DynamoDbClient.executeTransaction(crossinline block: ExecuteTransactionRequest.Builder.() -> Unit): ExecuteTransactionResponse = executeTransaction(ExecuteTransactionRequest.Builder().apply(block).build())

/**
 * Exports table data to an S3 bucket. The table must have point in time recovery enabled, and you can export data from any time within the point in time recovery window.
 */
public suspend inline fun DynamoDbClient.exportTableToPointInTime(crossinline block: ExportTableToPointInTimeRequest.Builder.() -> Unit): ExportTableToPointInTimeResponse = exportTableToPointInTime(ExportTableToPointInTimeRequest.Builder().apply(block).build())

/**
 * 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.
 *
 * @sample aws.sdk.kotlin.services.dynamodb.samples.GetItem.sample
 */
public suspend inline fun DynamoDbClient.getItem(crossinline block: GetItemRequest.Builder.() -> Unit): GetItemResponse = getItem(GetItemRequest.Builder().apply(block).build())

/**
 * Imports table data from an S3 bucket.
 */
public suspend inline fun DynamoDbClient.importTable(crossinline block: ImportTableRequest.Builder.() -> Unit): ImportTableResponse = importTable(ImportTableRequest.Builder().apply(block).build())

/**
 * List DynamoDB backups that are associated with an Amazon Web Services account and weren't made with Amazon Web Services Backup. To list these 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 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 boundaries are for the time at which the original backup was requested.
 *
 * You can call `ListBackups` a maximum of five times per second.
 *
 * If you want to retrieve the complete list of backups made with Amazon Web Services Backup, use the [Amazon Web Services Backup list API.](https://docs.aws.amazon.com/aws-backup/latest/devguide/API_ListBackupJobs.html)
 */
public suspend inline fun DynamoDbClient.listBackups(crossinline block: ListBackupsRequest.Builder.() -> Unit): ListBackupsResponse = listBackups(ListBackupsRequest.Builder().apply(block).build())

/**
 * Returns a list of ContributorInsightsSummary for a table and all its global secondary indexes.
 */
public suspend inline fun DynamoDbClient.listContributorInsights(crossinline block: ListContributorInsightsRequest.Builder.() -> Unit): ListContributorInsightsResponse = listContributorInsights(ListContributorInsightsRequest.Builder().apply(block).build())

/**
 * Lists completed exports within the past 90 days.
 */
public suspend inline fun DynamoDbClient.listExports(crossinline block: ListExportsRequest.Builder.() -> Unit): ListExportsResponse = listExports(ListExportsRequest.Builder().apply(block).build())

/**
 * Lists all global tables that have a replica in the specified Region.
 *
 * This operation only applies to [Version 2017.11.29 (Legacy)](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/globaltables.V1.html) of global tables. We recommend using [Version 2019.11.21 (Current)](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/globaltables.V2.html) when creating new global tables, as it provides greater flexibility, higher efficiency and consumes less write capacity than 2017.11.29 (Legacy). To determine which version you are using, see [Determining the version](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/globaltables.DetermineVersion.html). To update existing global tables from version 2017.11.29 (Legacy) to version 2019.11.21 (Current), see [ Updating global tables](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/V2globaltables_upgrade.html).
 */
public suspend inline fun DynamoDbClient.listGlobalTables(crossinline block: ListGlobalTablesRequest.Builder.() -> Unit): ListGlobalTablesResponse = listGlobalTables(ListGlobalTablesRequest.Builder().apply(block).build())

/**
 * Lists completed imports within the past 90 days.
 */
public suspend inline fun DynamoDbClient.listImports(crossinline block: ListImportsRequest.Builder.() -> Unit): ListImportsResponse = listImports(ListImportsRequest.Builder().apply(block).build())

/**
 * 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.
 *
 * @sample aws.sdk.kotlin.services.dynamodb.samples.ListTables.sample
 */
public suspend inline fun DynamoDbClient.listTables(crossinline block: ListTablesRequest.Builder.() -> Unit): ListTablesResponse = listTables(ListTablesRequest.Builder().apply(block).build())

/**
 * 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](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Tagging.html) in the *Amazon DynamoDB Developer Guide*.
 */
public suspend inline fun DynamoDbClient.listTagsOfResource(crossinline block: ListTagsOfResourceRequest.Builder.() -> Unit): ListTagsOfResourceResponse = listTagsOfResource(ListTagsOfResourceRequest.Builder().apply(block).build())

/**
 * 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.
 *
 * When you add an item, the primary key attributes are the only required attributes.
 *
 * Empty String and Binary attribute values are allowed. Attribute values of type String and Binary must have a length greater than zero if the attribute is used as a key attribute for a table or index. Set type attributes cannot be empty.
 *
 * Invalid 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](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/WorkingWithItems.html) in the *Amazon DynamoDB Developer Guide*.
 *
 * @sample aws.sdk.kotlin.services.dynamodb.samples.PutItem.sample
 */
public suspend inline fun DynamoDbClient.putItem(crossinline block: PutItemRequest.Builder.() -> Unit): PutItemResponse = putItem(PutItemRequest.Builder().apply(block).build())

/**
 * You must provide the name of the partition key attribute and a single value for that attribute. `Query` returns all items with that partition key value. Optionally, you can provide a sort key attribute and use a comparison operator to refine the search results.
 *
 * 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](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Query.html#Query.Pagination) 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.
 *
 * @sample aws.sdk.kotlin.services.dynamodb.samples.Query.sample
 */
public suspend inline fun DynamoDbClient.query(crossinline block: QueryRequest.Builder.() -> Unit): QueryResponse = query(QueryRequest.Builder().apply(block).build())

/**
 * Creates a new table from an existing backup. Any number of users can execute up to 50 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
 */
public suspend inline fun DynamoDbClient.restoreTableFromBackup(crossinline block: RestoreTableFromBackupRequest.Builder.() -> Unit): RestoreTableFromBackupResponse = restoreTableFromBackup(RestoreTableFromBackupRequest.Builder().apply(block).build())

/**
 * 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 50 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
 */
public suspend inline fun DynamoDbClient.restoreTableToPointInTime(crossinline block: RestoreTableToPointInTimeRequest.Builder.() -> Unit): RestoreTableToPointInTimeResponse = restoreTableToPointInTime(RestoreTableToPointInTimeRequest.Builder().apply(block).build())

/**
 * 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 size of scanned items exceeds the maximum dataset size limit of 1 MB, the scan completes and results are returned to the user. The `LastEvaluatedKey` value is also returned and the requestor can use the `LastEvaluatedKey` to continue the scan in a subsequent operation. Each scan response also includes number of items that were scanned (ScannedCount) as part of the request. If using a `FilterExpression`, a scan result can result in no items meeting the criteria and the `Count` will result in zero. If you did not use a `FilterExpression` in the scan request, then `Count` is the same as `ScannedCount`.
 *
 * `Count` and `ScannedCount` only return the count of items specific to a single scan request and, unless the table is less than 1MB, do not represent the total number of items in the table.
 *
 * A single `Scan` operation first reads up to the maximum number of items set (if using the `Limit` parameter) or a maximum of 1 MB of data and then applies any filtering to the results if a `FilterExpression` is provided. If `LastEvaluatedKey` is present in the response, pagination is required to complete the full table scan. For more information, see [Paginating the Results](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Scan.html#Scan.Pagination) 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](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Scan.html#Scan.ParallelScan) in the *Amazon DynamoDB Developer Guide*.
 *
 * By default, a `Scan` uses eventually consistent reads when accessing the items in a table. Therefore, the results from an eventually consistent `Scan` may not include the latest item changes at the time the scan iterates through each item in the table. If you require a strongly consistent read of each item as the scan iterates through the items in the table, you can set the `ConsistentRead` parameter to true. Strong consistency only relates to the consistency of the read at the item level.
 *
 *  DynamoDB does not provide snapshot isolation for a scan operation when the `ConsistentRead` parameter is set to true. Thus, a DynamoDB scan operation does not guarantee that all reads in a scan see a consistent snapshot of the table when the scan operation was requested.
 *
 * @sample aws.sdk.kotlin.services.dynamodb.samples.Scan.sample
 */
public suspend inline fun DynamoDbClient.scan(crossinline block: ScanRequest.Builder.() -> Unit): ScanResponse = scan(ScanRequest.Builder().apply(block).build())

/**
 * 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](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Tagging.html) in the *Amazon DynamoDB Developer Guide*.
 */
public suspend inline fun DynamoDbClient.tagResource(crossinline block: TagResourceRequest.Builder.() -> Unit): TagResourceResponse = tagResource(TagResourceRequest.Builder().apply(block).build())

/**
 * `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 100 `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 Amazon Web Services account or Region. The aggregate size of the items in the transaction cannot exceed 4 MB.
 *
 * 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 exceeded 4 MB.
 */
public suspend inline fun DynamoDbClient.transactGetItems(crossinline block: TransactGetItemsRequest.Builder.() -> Unit): TransactGetItemsResponse = transactGetItems(TransactGetItemsRequest.Builder().apply(block).build())

/**
 * `TransactWriteItems` is a synchronous write operation that groups up to 100 action requests. These actions can target items in different tables, but not in different Amazon Web Services 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.
 *
 * 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` — 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` — 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` — 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` — 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.
 */
public suspend inline fun DynamoDbClient.transactWriteItems(crossinline block: TransactWriteItemsRequest.Builder.() -> Unit): TransactWriteItemsResponse = transactWriteItems(TransactWriteItemsRequest.Builder().apply(block).build())

/**
 * 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](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Tagging.html) in the *Amazon DynamoDB Developer Guide*.
 */
public suspend inline fun DynamoDbClient.untagResource(crossinline block: UntagResourceRequest.Builder.() -> Unit): UntagResourceResponse = untagResource(UntagResourceRequest.Builder().apply(block).build())

/**
 * `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.
 */
public suspend inline fun DynamoDbClient.updateContinuousBackups(crossinline block: UpdateContinuousBackupsRequest.Builder.() -> Unit): UpdateContinuousBackupsResponse = updateContinuousBackups(UpdateContinuousBackupsRequest.Builder().apply(block).build())

/**
 * Updates the status for contributor insights for a specific table or index. CloudWatch Contributor Insights for DynamoDB graphs display the partition key and (if applicable) sort key of frequently accessed items and frequently throttled items in plaintext. If you require the use of Amazon Web Services Key Management Service (KMS) to encrypt this table’s partition key and sort key data with an Amazon Web Services managed key or customer managed key, you should not enable CloudWatch Contributor Insights for DynamoDB for this table.
 */
public suspend inline fun DynamoDbClient.updateContributorInsights(crossinline block: UpdateContributorInsightsRequest.Builder.() -> Unit): UpdateContributorInsightsResponse = updateContributorInsights(UpdateContributorInsightsRequest.Builder().apply(block).build())

/**
 * 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.
 *
 * This operation only applies to [Version 2017.11.29 (Legacy)](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/globaltables.V1.html) of global tables. We recommend using [Version 2019.11.21 (Current)](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/globaltables.V2.html) when creating new global tables, as it provides greater flexibility, higher efficiency and consumes less write capacity than 2017.11.29 (Legacy). To determine which version you are using, see [Determining the version](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/globaltables.DetermineVersion.html). To update existing global tables from version 2017.11.29 (Legacy) to version 2019.11.21 (Current), see [ Updating global tables](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/V2globaltables_upgrade.html).
 *
 *  This operation only applies to [Version 2017.11.29](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/globaltables.V1.html) of global tables. If you are using global tables [Version 2019.11.21](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/globaltables.V2.html) you can use [UpdateTable](https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_UpdateTable.html) instead.
 *
 *  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.
 */
public suspend inline fun DynamoDbClient.updateGlobalTable(crossinline block: UpdateGlobalTableRequest.Builder.() -> Unit): UpdateGlobalTableResponse = updateGlobalTable(UpdateGlobalTableRequest.Builder().apply(block).build())

/**
 * Updates settings for a global table.
 *
 * This operation only applies to [Version 2017.11.29 (Legacy)](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/globaltables.V1.html) of global tables. We recommend using [Version 2019.11.21 (Current)](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/globaltables.V2.html) when creating new global tables, as it provides greater flexibility, higher efficiency and consumes less write capacity than 2017.11.29 (Legacy). To determine which version you are using, see [Determining the version](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/globaltables.DetermineVersion.html). To update existing global tables from version 2017.11.29 (Legacy) to version 2019.11.21 (Current), see [ Updating global tables](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/V2globaltables_upgrade.html).
 */
public suspend inline fun DynamoDbClient.updateGlobalTableSettings(crossinline block: UpdateGlobalTableSettingsRequest.Builder.() -> Unit): UpdateGlobalTableSettingsResponse = updateGlobalTableSettings(UpdateGlobalTableSettingsRequest.Builder().apply(block).build())

/**
 * 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.
 *
 * @sample aws.sdk.kotlin.services.dynamodb.samples.UpdateItem.sample
 */
public suspend inline fun DynamoDbClient.updateItem(crossinline block: UpdateItemRequest.Builder.() -> Unit): UpdateItemResponse = updateItem(UpdateItemRequest.Builder().apply(block).build())

/**
 * The command to update the Kinesis stream destination.
 */
public suspend inline fun DynamoDbClient.updateKinesisStreamingDestination(crossinline block: UpdateKinesisStreamingDestinationRequest.Builder.() -> Unit): UpdateKinesisStreamingDestinationResponse = updateKinesisStreamingDestination(UpdateKinesisStreamingDestinationRequest.Builder().apply(block).build())

/**
 * Modifies the provisioned throughput settings, global secondary indexes, or DynamoDB Streams settings for a given table.
 *
 * This operation only applies to [Version 2019.11.21 (Current)](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/globaltables.V2.html) of global tables.
 *
 * You can only perform one of the following operations at once:
 * + Modify the provisioned throughput settings of 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's executing, the table status changes from `ACTIVE` to `UPDATING`. While it's `UPDATING`, you can't issue another `UpdateTable` request on the base table nor any replicas. When the table returns to the `ACTIVE` state, the `UpdateTable` operation is complete.
 */
public suspend inline fun DynamoDbClient.updateTable(crossinline block: UpdateTableRequest.Builder.() -> Unit): UpdateTableResponse = updateTable(UpdateTableRequest.Builder().apply(block).build())

/**
 * Updates auto scaling settings on your global tables at once.
 *
 * This operation only applies to [Version 2019.11.21 (Current)](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/globaltables.V2.html) of global tables.
 */
public suspend inline fun DynamoDbClient.updateTableReplicaAutoScaling(crossinline block: UpdateTableReplicaAutoScalingRequest.Builder.() -> Unit): UpdateTableReplicaAutoScalingResponse = updateTableReplicaAutoScaling(UpdateTableReplicaAutoScalingRequest.Builder().apply(block).build())

/**
 * 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](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/TTL.html) in the Amazon DynamoDB Developer Guide.
 */
public suspend inline fun DynamoDbClient.updateTimeToLive(crossinline block: UpdateTimeToLiveRequest.Builder.() -> Unit): UpdateTimeToLiveResponse = updateTimeToLive(UpdateTimeToLiveRequest.Builder().apply(block).build())