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

Match the plan to the workload

The module’s curated SQL Server plans are Standard and Standard XL on M5 instance classes, plus Memory and Memory XL on R5. Their stored classes are db.m5.large, db.m5.xlarge, db.r5.large and db.r5.xlarge. These differ from the small or Graviton plans offered for some other database engines.

AWS documents the supported RDS for SQL Server instance classes. Review sustained CPU demand, working memory and connection load, rather than choosing only by the tier name. Review general-purpose versus memory capacity against the application’s workload; a tier name alone is not a sizing decision.

Save a matching configuration

1. Open the package’s Module tab.
2. Confirm Amazon RDS, the intended region and Plan.
3. Review SQL Server 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 SQL Server Blesta guide for related tasks, or explore PD AWS SQL Server.