As the hosting operator, enable the intended firewall control and guide your customer through allowing their application’s address on an RDS-backed database. This workflow applies to the module’s dedicated RDS firewall group; it is not available for a Lightsail-backed database.

Establish the application’s actual source address

Identify the address AWS will see from the application, which can differ from a staff browser’s address. Review the database’s public/private access and route separately. An allowed address is not a substitute for routing, authentication or TLS.

The module accepts an IPv4 address or IPv4 CIDR range and applies it to the MySQL service port. Use the narrow intended range; do not assume this form supports IPv6 or arbitrary ports.

Customer steps: add and verify the rule

1. Open the intended service’s Firewall page.
2. Review the existing allowed addresses and their descriptions.
3. Enter the intended IPv4 address or CIDR and a useful description.
4. Choose Allow this IP and follow the request under Activity.
5. Reload the allowed list and confirm existing required addresses remain.
6. Test a connection from the actual application using the current credentials and TLS.

The save represents the intended customer-port rule list. Keep the other required addresses when reviewing it; do not intentionally replace the list with a single new address.

Diagnose a refusal

Check Client: Firewall in the offering’s module settings, the affected service’s ability to make changes and the database’s dedicated group. The module refuses a shared-group change rather than applying a customer rule to unrelated databases.

For a failed or unclear save, compare the original Activity result and current allowed list with the rules visible for that database in your AWS account. Distinguish a refused rule change from a successfully saved rule followed by a failed application connection. If AWS names a permission or group problem, review that requirement with your AWS administrator. Use rule removal for a deliberate later cleanup.

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