As the hosting operator, guide your customer or database administrator through creating an application database after PD AWS SQL Server has provisioned the RDS instance. The module does not create a named application database during instance setup, so an absent Database field in the customer Overview is expected.

Start with the correct connection

Open the active service in the Blesta client area and confirm the intended instance and region. Use the SSMS connection guide to establish a working, encrypted connection. The SQL Server login used for these steps needs permission to create databases. If the credential or permission is missing, your hosting team should verify the intended database login and permissions before your customer proceeds.

The module’s resource is an RDS database instance, not a Windows desktop or server login. Database work happens through a compatible SQL client; it does not require a new billing order for each database you create inside that instance.

Customer steps: create the database in SSMS

1. Select the intended connected instance in Object Explorer.
2. Open the Databases context menu and choose New Database.
3. Give the application database a meaningful name.
4. Keep the managed storage defaults unless the administrator has planned different settings.
5. Confirm with OK, then refresh the database list and check that the new name appears.

Microsoft documents database creation in SSMS. These are SQL client controls, not buttons added to the billing panel by this module.

Verify the application separately

Use the new database name in the application’s connection configuration and verify its intended operation. Database creation alone does not establish that the application login has the required access. Review application permissions with the administrator, and include the new database in the planned recovery checks. Keep passwords out of tickets, screenshots and shared connection strings.

Check database-creation permissions

As the hosting operator, check a refused New Database operation with the responsible SQL Server administrator. Record the selected instance, login’s intended permissions and the exact redacted SSMS error. An absent application database is expected before your customer or administrator creates one; it is not by itself a failed module provisioning result.

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