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

Match the plan to the workload

The module’s curated Oracle plans are Small and Medium on the burstable T3 family, plus Large and X-Large on the M5 family. Their stored instance classes are db.t3.small, db.t3.medium, db.m5.large and db.m5.xlarge. These are Oracle-specific choices; do not substitute another engine’s Graviton plan IDs.

AWS documents the supported RDS for Oracle instance classes. 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 Oracle 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 Oracle Blesta guide for related tasks, or explore PD AWS Oracle.