ModifyCurrentDBClusterCapacityMessage

import type { ModifyCurrentDBClusterCapacityMessage } from "https://aws-api.deno.dev/v0.4/services/rds.ts?docs=full";

interface ModifyCurrentDBClusterCapacityMessage {

Capacity?: number | null;

DBClusterIdentifier: string;

SecondsBeforeTimeout?: number | null;

TimeoutAction?: string | null;

}

§Properties

Capacity?: number | null

[src]

The DB cluster capacity.

When you change the capacity of a paused Aurora Serverless v1 DB cluster, it automatically resumes.

Constraints:

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.

DBClusterIdentifier: string

[src]

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.

SecondsBeforeTimeout?: number | null

[src]

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 10 and 600 seconds.

TimeoutAction?: string | null

[src]

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.