Choose a database instance class that suits the application you intend to host through PD AWS MariaDB. The plan controls compute and memory; storage and the MariaDB engine version need their own review.

Match the plan to the workload

The module’s curated RDS plans include Micro, Small, Medium, Large and X-Large. Micro, Small and Medium use the burstable T4g family; Large and X-Large use the M6g family. Medium is not a fixed-performance plan simply because it is larger than Small.

AWS explains the baseline and CPU-credit behaviour of RDS instance types. Review sustained CPU demand, working memory and connection load, rather than choosing only by the tier name. A burstable plan can suit intermittent workloads while sustained usage needs closer capacity and provider-cost review.

Save a matching configuration

1. Open the package’s Module tab.
2. Confirm Amazon RDS, the intended region and Plan.
3. Review MariaDB version and storage for that combination.
4. Save and review the actual order or service selections before provisioning.

Availability can change by AWS region, engine version and account. Live lookups may fall back to curated choices when AWS is unavailable, so a displayed plan is not proof that AWS will accept that precise combination.

Keep existing database changes deliberate

Changing a default for new orders is separate from changing an existing database. Do not resize a live application simply to inspect a plan. Review provider readiness, recovery needs and application interruption with the administrator before a supported service change. If provisioning refused the selected class, keep the original service and inspect the recorded result before trying again.

See the PD AWS MariaDB Blesta guide for related tasks, or explore PD AWS MariaDB.