aws neptune restore-db-cluster-from-snapshot
Creates a new DB cluster from a DB snapshot or DB cluster snapshot. If a DB snapshot is specified, the target DB cluster is created from the source DB snapshot with a default configuration and default security group. If a DB cluster snapshot is specified, the target DB cluster is created from the source DB cluster restore point with the same configuration as the original source DB cluster, except that the new DB cluster is created with the default security group
Options
Name | Description |
---|---|
--availability-zones <list> | Provides the list of EC2 Availability Zones that instances in the restored DB cluster can be created in |
--db-cluster-identifier <string> | The name of the DB cluster to create from the DB snapshot or DB cluster snapshot. This parameter isn't case-sensitive. Constraints: Must contain from 1 to 63 letters, numbers, or hyphens First character must be a letter Cannot end with a hyphen or contain two consecutive hyphens Example: my-snapshot-id |
--snapshot-identifier <string> | The identifier for the DB snapshot or DB cluster snapshot to restore from. You can use either the name or the Amazon Resource Name (ARN) to specify a DB cluster snapshot. However, you can use only the ARN to specify a DB snapshot. Constraints: Must match the identifier of an existing Snapshot |
--engine <string> | The database engine to use for the new DB cluster. Default: The same as source Constraint: Must be compatible with the engine of the source |
--engine-version <string> | The version of the database engine to use for the new DB cluster |
--port <integer> | The port number on which the new DB cluster accepts connections. Constraints: Value must be 1150-65535 Default: The same port as the original DB cluster |
--db-subnet-group-name <string> | The name of the DB subnet group to use for the new DB cluster. Constraints: If supplied, must match the name of an existing DBSubnetGroup. Example: mySubnetgroup |
--database-name <string> | Not supported |
--option-group-name <string> | (Not supported by Neptune) |
--vpc-security-group-ids <list> | A list of VPC security groups that the new DB cluster will belong to |
--tags <list> | The tags to be assigned to the restored DB cluster |
--kms-key-id <string> | The AWS KMS key identifier to use when restoring an encrypted DB cluster from a DB snapshot or DB cluster snapshot. The KMS key identifier is the Amazon Resource Name (ARN) for the KMS encryption key. If you are restoring a DB cluster with the same AWS account that owns the KMS encryption key used to encrypt the new DB cluster, then you can use the KMS key alias instead of the ARN for the KMS encryption key. If you do not specify a value for the KmsKeyId parameter, then the following will occur: If the DB snapshot or DB cluster snapshot in SnapshotIdentifier is encrypted, then the restored DB cluster is encrypted using the KMS key that was used to encrypt the DB snapshot or DB cluster snapshot. If the DB snapshot or DB cluster snapshot in SnapshotIdentifier is not encrypted, then the restored DB cluster is not encrypted |
--enable-iam-database-authentication | True to enable mapping of AWS Identity and Access Management (IAM) accounts to database accounts, and otherwise false. Default: false |
--no-enable-iam-database-authentication | True to enable mapping of AWS Identity and Access Management (IAM) accounts to database accounts, and otherwise false. Default: false |
--enable-cloudwatch-logs-exports <list> | The list of logs that the restored DB cluster is to export to Amazon CloudWatch Logs |
--db-cluster-parameter-group-name <string> | The name of the DB cluster parameter group to associate with the new DB cluster. Constraints: If supplied, must match the name of an existing DBClusterParameterGroup |
--deletion-protection | A value that indicates whether the DB cluster has deletion protection enabled. The database can't be deleted when deletion protection is enabled. By default, deletion protection is disabled |
--no-deletion-protection | A value that indicates whether the DB cluster has deletion protection enabled. The database can't be deleted when deletion protection is enabled. By default, deletion protection is disabled |
--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 |