You are viewing documentation for version 2 of the AWS SDK for Ruby. Version 3 documentation can be found here.
Class: Aws::RDS::Types::ModifyCurrentDBClusterCapacityMessage
- Inherits:
-
Struct
- Object
- Struct
- Aws::RDS::Types::ModifyCurrentDBClusterCapacityMessage
- Defined in:
- (unknown)
Overview
When passing ModifyCurrentDBClusterCapacityMessage as input to an Aws::Client method, you can use a vanilla Hash:
{
db_cluster_identifier: "String", # required
capacity: 1,
seconds_before_timeout: 1,
timeout_action: "String",
}
Instance Attribute Summary collapse
-
#capacity ⇒ Integer
The DB cluster capacity.
-
#db_cluster_identifier ⇒ String
The DB cluster identifier for the cluster being modified.
-
#seconds_before_timeout ⇒ Integer
The amount of time, in seconds, that Aurora Serverless tries to find a scaling point to perform seamless scaling before enforcing the timeout action.
-
#timeout_action ⇒ String
The action to take when the timeout is reached, either
ForceApplyCapacityChangeorRollbackCapacityChange.
Instance Attribute Details
#capacity ⇒ Integer
The DB cluster capacity.
When you change the capacity of a paused Aurora Serverless DB cluster, it automatically resumes.
Constraints:
For Aurora MySQL, valid capacity values are
1,2,4,8,16,32,64,128, and256.For Aurora PostgreSQL, valid capacity values are
2,4,8,16,32,64,192, and384.
#db_cluster_identifier ⇒ String
The DB cluster identifier for the cluster being modified. This parameter isn\'t case-sensitive.
Constraints:
- Must match the identifier of an existing DB cluster.
^
#seconds_before_timeout ⇒ Integer
The amount of time, in seconds, that Aurora Serverless tries to find a scaling point to perform seamless scaling before enforcing the timeout action. The default is 300.
- Value must be from 10 through 600.
^
#timeout_action ⇒ String
The action to take when the timeout is reached, either
ForceApplyCapacityChange or RollbackCapacityChange.
ForceApplyCapacityChange, the default, sets the capacity to the
specified value as soon as possible.
RollbackCapacityChange ignores the capacity change if a scaling point
isn\'t found in the timeout period.