AWS cli documentation change
Summary
Reorganized CLI parameters, added network-type documentation, and restructured scaling configuration details. Added new parameters like source-db-cluster-resource-id and expanded DB cluster response fields.
Security assessment
Added documentation for --network-type parameter explaining VPC security implications and IP protocol restrictions. Enhanced CertificateDetails section describing SSL/TLS encryption requirements and certificate management. These changes improve documentation of security-related configurations but don't address specific vulnerabilities.
Diff
diff --git a/cli/latest/reference/rds/restore-db-cluster-to-point-in-time.md b/cli/latest/reference/rds/restore-db-cluster-to-point-in-time.md index a82ab2c29..09b0493b0 100644 --- a//cli/latest/reference/rds/restore-db-cluster-to-point-in-time.md +++ b//cli/latest/reference/rds/restore-db-cluster-to-point-in-time.md @@ -15 +15 @@ - * [AWS CLI 2.31.3 Command Reference](../../index.html) » + * [AWS CLI 2.31.5 Command Reference](../../index.html) » @@ -95,2 +94,0 @@ See also: [AWS API Documentation](https://docs.aws.amazon.com/goto/WebAPI/rds-20 - [--scaling-configuration <value>] - [--engine-mode <value>] @@ -101 +98,0 @@ See also: [AWS API Documentation](https://docs.aws.amazon.com/goto/WebAPI/rds-20 - [--serverless-v2-scaling-configuration <value>] @@ -103,0 +101,3 @@ See also: [AWS API Documentation](https://docs.aws.amazon.com/goto/WebAPI/rds-20 + [--serverless-v2-scaling-configuration <value>] + [--scaling-configuration <value>] + [--engine-mode <value>] @@ -397,85 +396,0 @@ Syntax: -`--scaling-configuration` (structure) - -> For DB clusters in `serverless` DB engine mode, the scaling properties of the DB cluster. -> -> Valid for: Aurora DB clusters only -> -> MinCapacity -> (integer) -> ->> The minimum capacity for an Aurora DB cluster in `serverless` DB engine mode. ->> ->> For Aurora MySQL, valid capacity values are `1` , `2` , `4` , `8` , `16` , `32` , `64` , `128` , and `256` . ->> ->> For Aurora PostgreSQL, valid capacity values are `2` , `4` , `8` , `16` , `32` , `64` , `192` , and `384` . ->> ->> The minimum capacity must be less than or equal to the maximum capacity. -> -> MaxCapacity -> (integer) -> ->> The maximum capacity for an Aurora DB cluster in `serverless` DB engine mode. ->> ->> For Aurora MySQL, valid capacity values are `1` , `2` , `4` , `8` , `16` , `32` , `64` , `128` , and `256` . ->> ->> For Aurora PostgreSQL, valid capacity values are `2` , `4` , `8` , `16` , `32` , `64` , `192` , and `384` . ->> ->> The maximum capacity must be greater than or equal to the minimum capacity. -> -> AutoPause -> (boolean) -> ->> Indicates whether to allow or disallow automatic pause for an Aurora DB cluster in `serverless` DB engine mode. A DB cluster can be paused only when it’s idle (it has no connections). ->> ->> ### Note ->> ->> If a DB cluster is paused for more than seven days, the DB cluster might be backed up with a snapshot. In this case, the DB cluster is restored when there is a request to connect to it. -> -> SecondsUntilAutoPause -> (integer) -> ->> The time, in seconds, before an Aurora DB cluster in `serverless` mode is paused. ->> ->> Specify a value between 300 and 86,400 seconds. -> -> TimeoutAction -> (string) -> ->> The action to take when the timeout is reached, either `ForceApplyCapacityChange` or `RollbackCapacityChange` . ->> ->>> `ForceApplyCapacityChange` sets the capacity to the specified value as soon as possible. ->>> ->>> `RollbackCapacityChange` , the default, ignores the capacity change if a scaling point isn’t found in the timeout period. ->> ->> ### Warning ->> ->> If you specify `ForceApplyCapacityChange` , connections that prevent Aurora Serverless v1 from finding a scaling point might be dropped. ->> ->> For more information, see [Autoscaling for Aurora Serverless v1](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-serverless.how-it-works.html#aurora-serverless.how-it-works.auto-scaling) in the _Amazon Aurora User Guide_ . -> -> SecondsBeforeTimeout -> (integer) -> ->> The amount of time, in seconds, that Aurora Serverless v1 tries to find a scaling point to perform seamless scaling before enforcing the timeout action. The default is 300. ->> ->> Specify a value between 60 and 600 seconds. - -Shorthand Syntax: - - - MinCapacity=integer,MaxCapacity=integer,AutoPause=boolean,SecondsUntilAutoPause=integer,TimeoutAction=string,SecondsBeforeTimeout=integer - - -JSON Syntax: - - - { - "MinCapacity": integer, - "MaxCapacity": integer, - "AutoPause": true|false, - "SecondsUntilAutoPause": integer, - "TimeoutAction": "string", - "SecondsBeforeTimeout": integer - } - - -`--engine-mode` (string) - -> The engine mode of the new cluster. Specify `provisioned` or `serverless` , depending on the type of the cluster you are creating. You can create an Aurora Serverless v1 clone from a provisioned cluster, or a provisioned clone from an Aurora Serverless v1 cluster. To create a clone that is an Aurora Serverless v1 cluster, the original cluster must be an Aurora Serverless v1 cluster or an encrypted provisioned cluster. To create a full copy that is an Aurora Serverless v1 cluster, specify the engine mode `serverless` . -> -> Valid for: Aurora DB clusters only - @@ -537,0 +453,21 @@ JSON Syntax: +`--network-type` (string) + +> The network type of the DB cluster. +> +> Valid Values: +> +> * `IPV4` +> * `DUAL` +> + +> +> The network type is determined by the `DBSubnetGroup` specified for the DB cluster. A `DBSubnetGroup` can support only the IPv4 protocol or the IPv4 and the IPv6 protocols (`DUAL` ). +> +> For more information, see [Working with a DB instance in a VPC](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_VPC.WorkingWithRDSInstanceinaVPC.html) in the _Amazon Aurora User Guide._ +> +> Valid for: Aurora DB clusters only + +`--source-db-cluster-resource-id` (string) + +> The resource ID of the source DB cluster from which to restore. + @@ -574 +510 @@ JSON Syntax: -`--network-type` (string) +`--scaling-configuration` (structure) @@ -576 +512 @@ JSON Syntax: -> The network type of the DB cluster. +> For DB clusters in `serverless` DB engine mode, the scaling properties of the DB cluster. @@ -578 +514 @@ JSON Syntax: -> Valid Values: +> Valid for: Aurora DB clusters only @@ -580,2 +516 @@ JSON Syntax: -> * `IPV4` -> * `DUAL` +> MinCapacity -> (integer) @@ -583 +518,7 @@ JSON Syntax: - +>> The minimum capacity for an Aurora DB cluster in `serverless` DB engine mode. +>> +>> For Aurora MySQL, valid capacity values are `1` , `2` , `4` , `8` , `16` , `32` , `64` , `128` , and `256` . +>> +>> For Aurora PostgreSQL, valid capacity values are `2` , `4` , `8` , `16` , `32` , `64` , `192` , and `384` . +>> +>> The minimum capacity must be less than or equal to the maximum capacity. @@ -585 +526 @@ JSON Syntax: -> The network type is determined by the `DBSubnetGroup` specified for the DB cluster. A `DBSubnetGroup` can support only the IPv4 protocol or the IPv4 and the IPv6 protocols (`DUAL` ). +> MaxCapacity -> (integer) @@ -587 +528,7 @@ JSON Syntax: -> For more information, see [Working with a DB instance in a VPC](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_VPC.WorkingWithRDSInstanceinaVPC.html) in the _Amazon Aurora User Guide._ +>> The maximum capacity for an Aurora DB cluster in `serverless` DB engine mode. +>> +>> For Aurora MySQL, valid capacity values are `1` , `2` , `4` , `8` , `16` , `32` , `64` , `128` , and `256` . +>> +>> For Aurora PostgreSQL, valid capacity values are `2` , `4` , `8` , `16` , `32` , `64` , `192` , and `384` . +>> +>> The maximum capacity must be greater than or equal to the minimum capacity. @@ -589 +536,33 @@ JSON Syntax: -> Valid for: Aurora DB clusters only +> AutoPause -> (boolean) +> +>> Indicates whether to allow or disallow automatic pause for an Aurora DB cluster in `serverless` DB engine mode. A DB cluster can be paused only when it’s idle (it has no connections). +>> +>> ### Note +>> +>> If a DB cluster is paused for more than seven days, the DB cluster might be backed up with a snapshot. In this case, the DB cluster is restored when there is a request to connect to it. +> +> SecondsUntilAutoPause -> (integer) +> +>> The time, in seconds, before an Aurora DB cluster in `serverless` mode is paused. +>> +>> Specify a value between 300 and 86,400 seconds. +> +> TimeoutAction -> (string) +> +>> The action to take when the timeout is reached, either `ForceApplyCapacityChange` or `RollbackCapacityChange` . +>> +>>> `ForceApplyCapacityChange` sets the capacity to the specified value as soon as possible. +>>> +>>> `RollbackCapacityChange` , the default, ignores the capacity change if a scaling point isn’t found in the timeout period. +>> +>> ### Warning +>> +>> If you specify `ForceApplyCapacityChange` , connections that prevent Aurora Serverless v1 from finding a scaling point might be dropped. +>> +>> For more information, see [Autoscaling for Aurora Serverless v1](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-serverless.how-it-works.html#aurora-serverless.how-it-works.auto-scaling) in the _Amazon Aurora User Guide_ . +> +> SecondsBeforeTimeout -> (integer) +> +>> The amount of time, in seconds, that Aurora Serverless v1 tries to find a scaling point to perform seamless scaling before enforcing the timeout action. The default is 300. +>> +>> Specify a value between 60 and 600 seconds. @@ -591 +570,17 @@ JSON Syntax: -`--source-db-cluster-resource-id` (string) +Shorthand Syntax: + + + MinCapacity=integer,MaxCapacity=integer,AutoPause=boolean,SecondsUntilAutoPause=integer,TimeoutAction=string,SecondsBeforeTimeout=integer +