Control which database features customers can use from their service page. PD AWS MySQL combines host-enabled features with the backing’s capabilities; enabling a feature cannot add an operation the backing does not support.

Review the offering’s controls

1. Open the product’s Module Settings tab.
2. Review Client: Snapshots, Client: Firewall, Client: Connection details and Client: Usage graphs.
3. Enable only the intended customer features and save.
4. Review the intended service’s client pages and actual allowed actions.
5. Check any accepted feature-related choice when diagnosing a different result.

Connection details controls the connection card and password-reset access. Snapshot and firewall controls are separate. Switching off connection details does not change the AWS host credential or by itself revoke an application’s existing database login.

Keep backend differences visible

RDS supports the module’s IP firewall; Lightsail does not expose that feature here. A Firewall toggle cannot create an equivalent Lightsail IP allow-list. The available plan-management and storage operations also differ between backings.

A billing-suspended service cannot use customer mutations simply because a feature switch is enabled. Review the service’s billing and provider state separately; do not use a direct action to bypass an intended suspension.

Verify the intended experience

Check that required connection help and recovery information remain available to the intended reader. Hiding a page is separate from changing provider access; test the expected supported behaviour rather than relying on a menu alone.

If a feature remains absent or refused, compare the affected service with its saved feature setting, backing and billing state. Use operational checks before changing unrelated controls.

See the PD AWS MySQL WHMCS guide for related tasks, or explore PD AWS MySQL.