TimeoutAction

class aws_cdk.aws_rds.TimeoutAction(value, names=None, *, module=None, qualname=None, type=None, start=1, boundary=None)

Bases: Enum

TimeoutAction defines the action to take when a timeout occurs if a scaling point is not found.

See:: https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-serverless-v1.how-it-works.html#aurora-serverless.how-it-works.timeout-action
ExampleMetadata:: infused

Example:

# vpc: ec2.Vpc


cluster = rds.ServerlessCluster(self, "AnotherCluster",
    engine=rds.DatabaseClusterEngine.AURORA_POSTGRESQL,
    copy_tags_to_snapshot=True,  # whether to save the cluster tags when creating the snapshot. Default is 'true'
    parameter_group=rds.ParameterGroup.from_parameter_group_name(self, "ParameterGroup", "default.aurora-postgresql11"),
    vpc=vpc,
    scaling=rds.ServerlessScalingOptions(
        auto_pause=Duration.minutes(10),  # default is to pause after 5 minutes of idle time
        min_capacity=rds.AuroraCapacityUnit.ACU_8,  # default is 2 Aurora capacity units (ACUs)
        max_capacity=rds.AuroraCapacityUnit.ACU_32,  # default is 16 Aurora capacity units (ACUs)
        timeout=Duration.seconds(100),  # default is 5 minutes
        timeout_action=rds.TimeoutAction.FORCE_APPLY_CAPACITY_CHANGE
    )
)

Attributes

FORCE_APPLY_CAPACITY_CHANGE

FORCE_APPLY_CAPACITY_CHANGE sets the capacity to the specified value as soon as possible.

Transactions may be interrupted, and connections to temporary tables and locks may be dropped. Only select this option if your application can recover from dropped connections or incomplete transactions.

ROLLBACK_CAPACITY_CHANGE

ROLLBACK_CAPACITY_CHANGE ignores the capacity change if a scaling point is not found.

This is the default behavior.