stop_db_cluster
async
¶
stop_db_cluster(
*,
config_overrides: Optional[AsyncRDSClientConfig] = 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/async_rds.py
15737 15738 15739 15740 15741 15742 15743 15744 15745 15746 15747 15748 15749 15750 15751 15752 15753 15754 15755 15756 15757 15758 15759 15760 15761 15762 15763 15764 15765 15766 15767 15768 15769 15770 15771 15772 15773 15774 15775 15776 15777 15778 15779 15780 15781 15782 15783 15784 15785 15786 15787 15788 15789 15790 15791 15792 15793 15794 15795 15796 15797 15798 | |