import { DynamoDBClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../DynamoDBClient"; import { CreateGlobalTableInput, CreateGlobalTableOutput } from "../models/models_0"; import { deserializeAws_json1_0CreateGlobalTableCommand, serializeAws_json1_0CreateGlobalTableCommand, } from "../protocols/Aws_json1_0"; import { getSerdePlugin } from "@aws-sdk/middleware-serde"; import { HttpRequest as __HttpRequest, HttpResponse as __HttpResponse } from "@aws-sdk/protocol-http"; import { Command as $Command } from "@aws-sdk/smithy-client"; import { FinalizeHandlerArguments, Handler, HandlerExecutionContext, MiddlewareStack, HttpHandlerOptions as __HttpHandlerOptions, MetadataBearer as __MetadataBearer, SerdeContext as __SerdeContext, } from "@aws-sdk/types"; export interface CreateGlobalTableCommandInput extends CreateGlobalTableInput {} export interface CreateGlobalTableCommandOutput extends CreateGlobalTableOutput, __MetadataBearer {} /** *
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 of global tables.
*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. *
*