stop_db_cluster
¶
stop_db_cluster(
*,
config_overrides: Optional[RDSClientConfig] = None,
db_cluster_identifier: Optional[String] = None,
) -> StopDBClusterResult
Stops an Amazon Aurora DB cluster. When you stop a DB cluster, Aurora retains the DB cluster's metadata, including its endpoints and DB parameter groups. Aurora also retains the transaction logs so you can do a point-in-time restore if necessary.
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 stopped. 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.
-
UnknownServiceError–The service returned an error code this client does not model.
Examples:
To stop a DB cluster The following example stops a DB cluster and its DB instances.
Source code in docs_src/capo_rds/_services/rds.py
15569 15570 15571 15572 15573 15574 15575 15576 15577 15578 15579 15580 15581 15582 15583 15584 15585 15586 15587 15588 15589 15590 15591 15592 15593 15594 15595 15596 15597 15598 15599 15600 15601 15602 15603 15604 15605 15606 15607 15608 15609 15610 15611 15612 15613 15614 15615 15616 15617 15618 15619 15620 15621 15622 15623 15624 15625 15626 15627 15628 15629 | |