class Aws::DynamoDB::Types::UpdateTableInput

@see docs.aws.amazon.com/goto/WebAPI/dynamodb-2012-08-10/UpdateTableInput AWS API Documentation
@return [Types::WarmThroughput]
units per second) for updating a table.
Represents the warm throughput (in read units per second and write
@!attribute [rw] warm_throughput
@return [Types::OnDemandThroughput]
must specify ‘MaxReadRequestUnits`, `MaxWriteRequestUnits`, or both.
table in on-demand capacity mode. If you use this parameter, you
Updates the maximum number of read and write units for the specified
@!attribute [rw] on_demand_throughput
@return [String]<br>: docs.aws.amazon.com/amazondynamodb/latest/developerguide/PreviewFeatures.html#multi-region-strong-consistency-gt<br>[2]: docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_UpdateTable.html#DDB-UpdateTable-request-ReplicaUpdates<br>[1]: docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_ReplicationGroupUpdate.html#DDB-Type-ReplicationGroupUpdate-Create<br><br><br><br>mode defaults to `EVENTUAL`.
If you don’t specify this parameter, the global table consistency<br><br></note><br><br>consistency].
information, see [Global tables multi-Region strong
tables capability currently available in preview mode. For more
<note markdown=“1”> Multi-Region strong consistency (MRSC) is a new DynamoDB global
consistency (preview).
* ‘STRONG`: Configures a new global table for multi-Region strong
global tables.
eventual consistency. This is the default consistency mode for
* `EVENTUAL`: Configures a new global table for multi-Region
You can specify one of the following consistency modes:
list.
one or more [Create] actions in the [ReplicaUpdates] action
parameter is only valid when you create a global table by specifying
Specifies the consistency mode for a new global table. This
@!attribute [rw] multi_region_consistency
@return [Boolean]
disabled (false) on the table.
Indicates whether deletion protection is to be enabled (true) or
@!attribute [rw] deletion_protection_enabled
@return [String]
`STANDARD` and `STANDARD_INFREQUENT_ACCESS`.
The table class of the table to be updated. Valid values are
@!attribute [rw] table_class
@return [Array<Types::ReplicationGroupUpdate>]
</note>
Version 2019.11.21 (Current version).
<note markdown=“1”> For global tables, this property only applies to global tables using
table.
A list of replica update actions (create, delete, or update) for the
@!attribute [rw] replica_updates
@return [Types::SSESpecification]
The new server-side encryption settings for the specified table.
@!attribute [rw] sse_specification
@return [Types::StreamSpecification]
</note>
on a table that doesn’t have a stream.
a table that already has a stream, or if you try to disable a stream
<note markdown=“1”> You receive a ‘ValidationException` if you try to enable a stream on
Represents the DynamoDB Streams configuration for the table.
@!attribute [rw] stream_specification
@return [Array<Types::GlobalSecondaryIndexUpdate>]<br>: docs.aws.amazon.com/amazondynamodb/latest/developerguide/GSI.OnlineOps.html<br><br><br><br>the *Amazon DynamoDB Developer Guide*.
For more information, see [Managing Global Secondary Indexes] in
`UpdateTable` operation.
You can create or delete only one global secondary index per
* `Delete` - remove a global secondary index from the table.
existing global secondary index.
* `Update` - modify the provisioned throughput settings of an
* `Create` - add a new global secondary index to the table.
each index in the array, you can request one action:
An array of one or more global secondary indexes for the table. For
@!attribute [rw] global_secondary_index_updates
@return [Types::ProvisionedThroughput]
index.
The new provisioned throughput settings for the specified table or
@!attribute [rw] provisioned_throughput
@return [String]<br>: docs.aws.amazon.com/amazondynamodb/latest/developerguide/provisioned-capacity-mode.html<br>[1]: docs.aws.amazon.com/amazondynamodb/latest/developerguide/on-demand-capacity-mode.html<br><br><br><br>[Provisioned capacity mode].
be reliably forecasted. `PROVISIONED` sets the billing mode to
workloads with predictable growth where capacity requirements can
* `PROVISIONED` - We recommend using `PROVISIONED` for steady
[On-demand capacity mode].
DynamoDB workloads. `PAY_PER_REQUEST` sets the billing mode to
* `PAY_PER_REQUEST` - We recommend using `PAY_PER_REQUEST` for most
secondary indexes over the past 30 minutes.
the consumed read and write capacity of your table and global
set. The initial provisioned capacity values are estimated based on
provisioned capacity, initial provisioned capacity values must be
you manage capacity. When switching from pay-per-request to
Controls how you are charged for read and write throughput and how
@!attribute [rw] billing_mode
@return [String]
Resource Name (ARN) of the table in this parameter.
The name of the table to be updated. You can also provide the Amazon
@!attribute [rw] table_name
@return [Array<Types::AttributeDefinition>]
new index.
table, `AttributeDefinitions` must include the key element(s) of the
and indexes. If you are adding a new global secondary index to the
An array of attributes that describe the key schema for the table
@!attribute [rw] attribute_definitions
Represents the input of an `UpdateTable` operation.