Storage for Transactions services on AWS
This page is part of MariaDB's Documentation.
The parent of this page is: Storage Configuration
Topics on this page:
Overview
Transactions services on AWS feature SSD-backed storage, provisioned IOPS, and data-at-rest encryption.
Compatibility
Enterprise Server Single Node
Enterprise Server With Replica(s)
Xpand Distributed SQL
Initial Capacity
Initial storage capacity is defined at time of service launch.
For information about how to choose a storage capacity with the SkySQL DBaaS API, see "Transactional Storage Size Selections with the SkySQL DBaaS API".
Auto-Scaling
With auto-scaling of storage, storage expansion can be triggered automatically when a usage threshold is reached.
This feature can be enabled or disabled during service launch or after launch.
Manual Scaling
Storage capacity can be manually changed after launch using Self-Service Operations.
Data-at-Rest Encryption
MariaDB SkySQL features transparent data-at-rest encryption. This feature is not customer-configurable.
SkySQL on Amazon AWS benefits from Amazon EBS encryption.
Storage Type
On AWS, storage options include I/O intensive (io1) and general purpose (gp2).
Both options are SSD-backed.
With io1 storage, IOPS are configurable.
Provisioned IOPS
IOPS are I/O operations per second, a measure of storage performance.
When using the io1 storage type on AWS, the number of IOPS per GB of storage can be specified at time of service launch.
The maximum IOPS for a specific service will depend on the provisioned IOPS per GB of storage, the number of GB of storage per node, and the number of nodes; maximum IOPS = provisioned IOPS/GB * GB of storage/node * node count