From f69b00edab12702846a50e656a509fa0b0713202 Mon Sep 17 00:00:00 2001
From: awstools The requested operation can't be performed while the cluster is in this state. The maximum capacity of the DB shard group must be 48-7168 Aurora capacity units (ACUs). The DB subnet group doesn't cover all Availability Zones after it's
* created because of users' change. The requested operation can't be performed while the cluster is in this state. The maximum capacity of the DB shard group must be 48-7168 Aurora capacity units (ACUs). Base exception class for all service exceptions from RDS service.
To restore from a DB snapshot with an unsupported engine version, you must first upgrade the * engine version of the snapshot. For more information about upgrading a RDS for MySQL DB snapshot engine version, see Upgrading a MySQL DB snapshot engine version. - * For more information about upgrading a RDS for PostgreSQL DB snapshot engine version, Upgrading a PostgreSQL DB snapshot engine version.
+ * For more information about upgrading a RDS for PostgreSQL DB snapshot engine version, Upgrading a PostgreSQL DB snapshot engine version. *This command doesn't apply to Aurora MySQL and Aurora PostgreSQL. For Aurora, use RestoreDBClusterFromSnapshot
.
The name of the DB parameter group to associate with this DB instance.
- *If you don't specify a value for DBParameterGroupName
, then Amazon RDS
- * uses the DBParameterGroup
of the source DB instance for a same Region read
+ *
The name of the DB parameter group to associate with this read replica DB + * instance.
+ *For Single-AZ or Multi-AZ DB instance read replica instances, if you don't specify a
+ * value for DBParameterGroupName
, then Amazon RDS uses the
+ * DBParameterGroup
of the source DB instance for a same Region read
* replica, or the default DBParameterGroup
for the specified DB engine for a
* cross-Region read replica.
Specifying a parameter group for this operation is only supported for MySQL DB instances for cross-Region read replicas and for Oracle DB instances. It isn't supported for MySQL DB instances for same Region read replicas or for RDS Custom.
+ *For Multi-AZ DB cluster same Region read replica instances, if you don't specify a
+ * value for DBParameterGroupName
, then Amazon RDS uses the default
+ * DBParameterGroup
.
Specifying a parameter group for this operation is only supported for MySQL DB + * instances for cross-Region read replicas, for Multi-AZ DB cluster read replica + * instances, and for Oracle DB instances. It isn't supported for MySQL DB instances for + * same Region read replicas or for RDS Custom.
*Constraints:
*Specifies whether to create standby instances for the DB shard group. Valid values are the following:
+ *Specifies whether to create standby DB shard groups for the DB shard group. Valid values are the following:
*0 - Creates a single, primary DB instance for each physical shard. This is the default value, and the only one supported for the preview.
+ *0 - Creates a DB shard group without a standby DB shard group. This is the default value.
*1 - Creates a primary DB instance and a standby instance in a different Availability Zone (AZ) for each physical shard.
+ *1 - Creates a DB shard group with a standby DB shard group in a different Availability Zone (AZ).
*2 - Creates a primary DB instance and two standby instances in different AZs for each physical shard.
+ *2 - Creates a DB shard group with two standby DB shard groups in two different AZs.
*Specifies whether to create standby instances for the DB shard group. Valid values are the following:
+ *Specifies whether to create standby DB shard groups for the DB shard group. Valid values are the following:
*0 - Creates a single, primary DB instance for each physical shard. This is the default value, and the only one supported for the preview.
+ *0 - Creates a DB shard group without a standby DB shard group. This is the default value.
*1 - Creates a primary DB instance and a standby instance in a different Availability Zone (AZ) for each physical shard.
+ *1 - Creates a DB shard group with a standby DB shard group in a different Availability Zone (AZ).
*2 - Creates a primary DB instance and two standby instances in different AZs for each physical shard.
+ *2 - Creates a DB shard group with two standby DB shard groups in two different AZs.
*The Amazon Resource Name (ARN) for the DB shard group.
+ * @public + */ + DBShardGroupArn?: string; } /** @@ -11591,26 +11605,6 @@ export class DBShardGroupAlreadyExistsFault extends __BaseException { } } -/** - *The maximum capacity of the DB shard group must be 48-7168 Aurora capacity units (ACUs).
- * @public - */ -export class InvalidMaxAcuFault extends __BaseException { - readonly name: "InvalidMaxAcuFault" = "InvalidMaxAcuFault"; - readonly $fault: "client" = "client"; - /** - * @internal - */ - constructor(opts: __ExceptionOptionTypeThe maximum number of DB shard groups for your Amazon Web Services account in the specified Amazon Web Services Region has been reached.
* @public @@ -14519,6 +14513,18 @@ export interface DeleteTenantDatabaseMessage { FinalDBSnapshotIdentifier?: string; } +/** + * @public + */ +export interface DeleteTenantDatabaseResult { + /** + *A tenant database in the DB instance. This data type is an element in the response to
+ * the DescribeTenantDatabases
action.
A tenant database in the DB instance. This data type is an element in the response to
- * the DescribeTenantDatabases
action.
The specified RDS DB instance or Aurora DB cluster isn't available for a proxy owned by your Amazon Web Services account in the specified Amazon Web Services Region.
* @public @@ -9717,6 +9705,23 @@ export interface ModifyDBShardGroupMessage { * @public */ MinACU?: number; + + /** + *Specifies whether to create standby DB shard groups for the DB shard group. Valid values are the following:
+ *0 - Creates a DB shard group without a standby DB shard group. This is the default value.
+ *1 - Creates a DB shard group with a standby DB shard group in a different Availability Zone (AZ).
+ *2 - Creates a DB shard group with two standby DB shard groups in two different AZs.
+ *The name of the DB parameter group to associate with this DB instance.
\nIf you don't specify a value for DBParameterGroupName
, then Amazon RDS\n uses the DBParameterGroup
of the source DB instance for a same Region read\n replica, or the default DBParameterGroup
for the specified DB engine for a\n cross-Region read replica.
Specifying a parameter group for this operation is only supported for MySQL DB instances for cross-Region read replicas and for Oracle DB instances. It isn't supported for MySQL DB instances for same Region read replicas or for RDS Custom.
\nConstraints:
\nMust be 1 to 255 letters, numbers, or hyphens.
\nFirst character must be a letter.
\nCan't end with a hyphen or contain two consecutive hyphens.
\nThe name of the DB parameter group to associate with this read replica DB\n instance.
\nFor Single-AZ or Multi-AZ DB instance read replica instances, if you don't specify a\n value for DBParameterGroupName
, then Amazon RDS uses the\n DBParameterGroup
of the source DB instance for a same Region read\n replica, or the default DBParameterGroup
for the specified DB engine for a\n cross-Region read replica.
For Multi-AZ DB cluster same Region read replica instances, if you don't specify a\n value for DBParameterGroupName
, then Amazon RDS uses the default\n DBParameterGroup
.
Specifying a parameter group for this operation is only supported for MySQL DB\n instances for cross-Region read replicas, for Multi-AZ DB cluster read replica\n instances, and for Oracle DB instances. It isn't supported for MySQL DB instances for\n same Region read replicas or for RDS Custom.
\nConstraints:
\nMust be 1 to 255 letters, numbers, or hyphens.
\nFirst character must be a letter.
\nCan't end with a hyphen or contain two consecutive hyphens.
\nSpecifies whether to create standby instances for the DB shard group. Valid values are the following:
\n0 - Creates a single, primary DB instance for each physical shard. This is the default value, and the only one supported for the preview.
\n1 - Creates a primary DB instance and a standby instance in a different Availability Zone (AZ) for each physical shard.
\n2 - Creates a primary DB instance and two standby instances in different AZs for each physical shard.
\nSpecifies whether to create standby DB shard groups for the DB shard group. Valid values are the following:
\n0 - Creates a DB shard group without a standby DB shard group. This is the default value.
\n1 - Creates a DB shard group with a standby DB shard group in a different Availability Zone (AZ).
\n2 - Creates a DB shard group with two standby DB shard groups in two different AZs.
\nSpecifies whether to create standby instances for the DB shard group. Valid values are the following:
\n0 - Creates a single, primary DB instance for each physical shard. This is the default value, and the only one supported for the preview.
\n1 - Creates a primary DB instance and a standby instance in a different Availability Zone (AZ) for each physical shard.
\n2 - Creates a primary DB instance and two standby instances in different AZs for each physical shard.
\nSpecifies whether to create standby DB shard groups for the DB shard group. Valid values are the following:
\n0 - Creates a DB shard group without a standby DB shard group. This is the default value.
\n1 - Creates a DB shard group with a standby DB shard group in a different Availability Zone (AZ).
\n2 - Creates a DB shard group with two standby DB shard groups in two different AZs.
\nThe connection endpoint for the DB shard group.
" } + }, + "DBShardGroupArn": { + "target": "com.amazonaws.rds#String", + "traits": { + "smithy.api#documentation": "The Amazon Resource Name (ARN) for the DB shard group.
" + } } } }, @@ -20402,23 +20405,6 @@ "smithy.api#httpError": 400 } }, - "com.amazonaws.rds#InvalidMaxAcuFault": { - "type": "structure", - "members": { - "message": { - "target": "com.amazonaws.rds#ExceptionMessage" - } - }, - "traits": { - "aws.protocols#awsQueryError": { - "code": "InvalidMaxAcu", - "httpResponseCode": 400 - }, - "smithy.api#documentation": "The maximum capacity of the DB shard group must be 48-7168 Aurora capacity units (ACUs).
", - "smithy.api#error": "client", - "smithy.api#httpError": 400 - } - }, "com.amazonaws.rds#InvalidOptionGroupStateFault": { "type": "structure", "members": { @@ -22753,9 +22739,6 @@ }, { "target": "com.amazonaws.rds#InvalidDBClusterStateFault" - }, - { - "target": "com.amazonaws.rds#InvalidMaxAcuFault" } ], "traits": { @@ -22784,6 +22767,12 @@ "traits": { "smithy.api#documentation": "The minimum capacity of the DB shard group in Aurora capacity units (ACUs).
" } + }, + "ComputeRedundancy": { + "target": "com.amazonaws.rds#IntegerOptional", + "traits": { + "smithy.api#documentation": "Specifies whether to create standby DB shard groups for the DB shard group. Valid values are the following:
\n0 - Creates a DB shard group without a standby DB shard group. This is the default value.
\n1 - Creates a DB shard group with a standby DB shard group in a different Availability Zone (AZ).
\n2 - Creates a DB shard group with two standby DB shard groups in two different AZs.
\nCreates a new DB instance from a DB snapshot. The target database is created from the source database restore point with most\n of the source's original configuration, including the default security group and DB parameter group. By default, the new DB\n instance is created as a Single-AZ deployment, except when the instance is a SQL Server instance that has an option group\n associated with mirroring. In this case, the instance becomes a Multi-AZ deployment, not a Single-AZ deployment.
\nIf you want to replace your original DB instance with the new, restored DB instance, then rename your original DB instance\n before you call the RestoreDBInstanceFromDBSnapshot
operation. RDS doesn't allow two DB instances with the same name. After you\n have renamed your original DB instance with a different identifier, then you can pass the original name of the DB instance as\n the DBInstanceIdentifier
in the call to the RestoreDBInstanceFromDBSnapshot
operation. The result is that you replace the original\n DB instance with the DB instance created from the snapshot.
If you are restoring from a shared manual DB snapshot, the DBSnapshotIdentifier
\n must be the ARN of the shared DB snapshot.
To restore from a DB snapshot with an unsupported engine version, you must first upgrade the \n engine version of the snapshot. For more information about upgrading a RDS for MySQL DB snapshot engine version, see Upgrading a MySQL DB snapshot engine version. \n For more information about upgrading a RDS for PostgreSQL DB snapshot engine version, Upgrading a PostgreSQL DB snapshot engine version.
\nThis command doesn't apply to Aurora MySQL and Aurora PostgreSQL. For Aurora, use RestoreDBClusterFromSnapshot
.
Creates a new DB instance from a DB snapshot. The target database is created from the source database restore point with most\n of the source's original configuration, including the default security group and DB parameter group. By default, the new DB\n instance is created as a Single-AZ deployment, except when the instance is a SQL Server instance that has an option group\n associated with mirroring. In this case, the instance becomes a Multi-AZ deployment, not a Single-AZ deployment.
\nIf you want to replace your original DB instance with the new, restored DB instance, then rename your original DB instance\n before you call the RestoreDBInstanceFromDBSnapshot
operation. RDS doesn't allow two DB instances with the same name. After you\n have renamed your original DB instance with a different identifier, then you can pass the original name of the DB instance as\n the DBInstanceIdentifier
in the call to the RestoreDBInstanceFromDBSnapshot
operation. The result is that you replace the original\n DB instance with the DB instance created from the snapshot.
If you are restoring from a shared manual DB snapshot, the DBSnapshotIdentifier
\n must be the ARN of the shared DB snapshot.
To restore from a DB snapshot with an unsupported engine version, you must first upgrade the \n engine version of the snapshot. For more information about upgrading a RDS for MySQL DB snapshot engine version, see Upgrading a MySQL DB snapshot engine version. \n For more information about upgrading a RDS for PostgreSQL DB snapshot engine version, Upgrading a PostgreSQL DB snapshot engine version.
\nThis command doesn't apply to Aurora MySQL and Aurora PostgreSQL. For Aurora, use RestoreDBClusterFromSnapshot
.