start_db_cluster
async
¶
start_db_cluster(
*,
config_overrides: Optional[AsyncRDSClientConfig] = None,
db_cluster_identifier: Optional[String] = None,
) -> StartDBClusterResult
Starts an Amazon Aurora DB cluster that was stopped using the Amazon Web Services console, the stop-db-cluster CLI command, or the StopDBCluster operation.
For more information, see Stopping and Starting an Aurora Cluster in the Amazon Aurora User Guide.
This operation only applies to Aurora DB clusters.
Parameters:
-
db_cluster_identifier(Optional[String], default:None) –The DB cluster identifier of the Amazon Aurora DB cluster to be started. This parameter is stored as a lowercase string.
Raises:
-
DBClusterNotFoundFault–DBClusterIdentifierdoesn't refer to an existing DB cluster. -
InvalidDBClusterStateFault–The requested operation can't be performed while the cluster is in this state.
-
InvalidDBInstanceStateFault–The DB instance isn't in a valid state.
-
InvalidDBShardGroupStateFault–The DB shard group must be in the available state.
-
KMSKeyNotAccessibleFault–An error occurred accessing an Amazon Web Services KMS key.
-
VpcEncryptionControlViolationException–The operation violates VPC encryption control settings. Make sure that your DB instance type supports the Nitro encryption-in-transit capability, or modify your VPC's encryption controls to not enforce encryption-in-transit.
-
UnknownServiceError–The service returned an error code this client does not model.
Examples:
To start a DB cluster The following example starts a DB cluster and its DB instances.
Source code in docs_src/capo_rds/_services/async_rds.py
15367 15368 15369 15370 15371 15372 15373 15374 15375 15376 15377 15378 15379 15380 15381 15382 15383 15384 15385 15386 15387 15388 15389 15390 15391 15392 15393 15394 15395 15396 15397 15398 15399 15400 15401 15402 15403 15404 15405 15406 15407 15408 15409 15410 15411 15412 15413 15414 15415 15416 15417 15418 15419 15420 15421 15422 15423 15424 15425 15426 15427 15428 15429 15430 | |