aws rds create-global-cluster
Creates an Aurora global database spread across multiple AWS Regions. The global database contains a single primary cluster with read-write capability, and a read-only secondary cluster that receives data from the primary cluster through high-speed replication performed by the Aurora storage subsystem. You can create a global database that is initially empty, and then add a primary cluster and a secondary cluster to it. Or you can specify an existing Aurora cluster during the create operation, and this cluster becomes the primary cluster of the global database. This action only applies to Aurora DB clusters
Options
| Name | Description |
|---|---|
--global-cluster-identifier <string> | The cluster identifier of the new global database cluster |
--source-db-cluster-identifier <string> | The Amazon Resource Name (ARN) to use as the primary cluster of the global database. This parameter is optional |
--engine <string> | The name of the database engine to be used for this DB cluster |
--engine-version <string> | The engine version of the Aurora global database |
--deletion-protection | The deletion protection setting for the new global database. The global database can't be deleted when deletion protection is enabled |
--no-deletion-protection | The deletion protection setting for the new global database. The global database can't be deleted when deletion protection is enabled |
--database-name <string> | The name for your database of up to 64 alpha-numeric characters. If you do not provide a name, Amazon Aurora will not create a database in the global database cluster you are creating |
--storage-encrypted | The storage encryption setting for the new global database cluster |
--no-storage-encrypted | The storage encryption setting for the new global database cluster |
--cli-input-json <string> | Performs service operation based on the JSON string provided. The JSON string follows the format provided by ``--generate-cli-skeleton``. If other arguments are provided on the command line, the CLI values will override the JSON-provided values. It is not possible to pass arbitrary binary values using a JSON-provided value as the string will be taken literally |
--generate-cli-skeleton <string> | Prints a JSON skeleton to standard output without sending an API request. If provided with no value or the value ``input``, prints a sample input JSON that can be used as an argument for ``--cli-input-json``. If provided with the value ``output``, it validates the command inputs and returns a sample output JSON for that command |