Scaling & Backup

Scaling

You can only scale RDS up (compute and storage).

You cannot decrease the allocated storage for an RDS instance.

You can scale storage and change the storage type for all DB engines except MS SQL.

For MS SQL the workaround is to create a new instance from a snapshot with the new configuration.

Scaling storage can happen while the RDS instance is running without outage however there may be performance degradation.

Scaling compute will cause downtime.

You can choose to have changes take effect immediately, however the default is within the maintenance window.

Scaling requests are applied during the specified maintenance window unless “apply immediately” is used.

All RDS DB types support a maximum DB size of 64 TiB except for Microsoft SQL Server (16 TiB)

⁠

Automated Backup Process:

Enabled by Default: Automated backups are enabled by default and perform daily snapshots.

Backup Retention Period: User-specified, up to 35 days.

Data Storage: Backups are stored in S3 and the storage size is equal to the DB instance size.

Multi-AZ Backups: For multi-AZ configurations, backups are taken from the standby instance to avoid I/O suspension on the primary instance.

State Requirement: The DB instance must be in an active state for automated backups to occur.

Point-in-Time Recovery:

Granularity: 5 minutes.

Restore Process: Requires creation of a new DB instance with a new endpoint.

Backup Configuration:

Backup Window: Can be chosen to minimize impact.

Costs: No additional charge for backups, but storage costs on S3 apply.

User-Defined Manual Backups:

Manual Snapshots: Initiated by the user and can be copied.

Storage and Retention: Manual snapshots are retained until explicitly deleted.

Restoration Constraints:

Parameter and Security Groups: Restored DB instances use default DB parameters and security groups, requiring reapplication of custom configurations.

No Existing DB Restore: You cannot restore a DB snapshot into an existing DB instance.

Engine-Specific Notes:

InnoDB Requirement: Automated backups are only supported for MySQL's InnoDB storage engine (not myISAM).

Want to print your doc?
This is not the way.

Try clicking the ⋯ next to your doc name or using a keyboard shortcut (

CtrlP

) instead.