Glossary
Concepts
Initial Setup
Peformance & Benchmark
Troubleshooting
FAQs
Database Proxy (DB Proxy) is an intermediary layer between applications and database servers. It manages and routes client connections, performs load balancing, and directs connections to the appropriate database nodes without requiring changes to application code or database configuration, thereby improving system high availability.
Currently, FPT Database Engine supports DB Proxy for the following database engines: MySQL, PostgreSQL, and MariaDB. DB Proxy is available only for databases deployed in High Availability (HA) mode.
On the FPT Cloud Portal, the DB Proxy Management feature allows users to:
| Permission | Action Type | Description |
|---|---|---|
| manageDatabase:ListProxy | View | Allow viewing the database's DB Proxy list. |
| manageDatabase:CreateProxy | Create | Allow creating a new DB proxy for a database in the system. |
| manageDatabase:DeleteProxy | Delete | Allow deleting a DB Proxy for databases in the system. |
Log in to the FPT Cloud Portal. After a successful login, from the main menu, select “Database Platform” > “All Databases”. Click the ID of the database cluster you want to manage, then switch to the DB Proxy tab to access the DB Proxy Management page:

Note: The DB Proxy tab is displayed only when the database is created with High Availability (HA) enabled and the database engine is supported.
On the DB Proxy Management page, click Create DB Proxy. The Create DB Proxy dialog is displayed:

Provide the following information:
After completing the configuration, click Create DB Proxy to confirm. The system validates resource availability, displays a creation notification, and starts provisioning the DB Proxy based on the selected settings. The newly created proxy appears at the top of the DB Proxy Management list with the status Processing.
The provisioning process typically takes 5–7 minutes. Once completed, the proxy status changes to Running and the proxy is ready for use. Note: If the provisioning process fails, delete the failed proxy and create a new one..
To view connection details for a DB Proxy, go to the DB Proxy Management page and select the proxy ID. The DB Proxy Detail dialog is displayed, showing endpoint and configuration information:

A Running status indicates that the DB Proxy is active and ready to accept connections. Use the information provided in the Endpoint field to configure application connections to the proxy.
You can perform operational actions on a DB Proxy based on its lifecycle status, including Start, Stop, Restart, Resize, and Delete.
Available Actions:
Action availability by database status:
| Status | Meaning | Actions Available |
|---|---|---|
| Processing | The proxy is provisioning. | Delete |
| Running | The proxy is operating normally. | Stop, Restart, Resize, Delete |
| Stopped | The proxy is stopped. | Start, Delete |
| Resizing | The proxy is currently having its resources adjusted. | Delete |
| Failed | The proxy encountered an unknown error. If the proxy is no longer needed, delete it to clean up resources, or contact FPT Support for assistance. | Delete |
Performing Operational Actions:
To perform an operation, open the DB Proxy Management page and select the More actions (⋯) icon in the Actions column for the target proxy. A list of available actions is displayed:

When you select an action, a confirmation dialog appears. Manual confirmation is required to prevent accidental or unintended operations, especially for irreversible actions such as Delete.
After confirmation, the system executes the selected action, which typically takes 5–7 minutes. During this time, other operations on the proxy are temporarily disabled until the process completes.
Best Practices Perform Restart or Resize operations during off-peak hours to minimize impact on applications.