A100 support-related questions
This topic answers common questions about the A100 series DataBase Audit service. This information helps you better understand and use the product.
What permissions can I grant to RAM users for DataBase Audit?
To uninstall the agent in CentOS, do I just delete the /usr/local/rmagent folder?
Do I need to select local loopback when installing the agent?
Do I need to consider the database type when I select a DataBase Audit edition?
How do I configure the DataBase Audit service after I purchase it?
How do I verify that the DataBase Audit service is configured correctly?
Does DataBase Audit support viewing administrator operation logs?
How do I uninstall, enable, and stop the agent program on a server?
What permissions can I grant to RAM users for DataBase Audit?
DataBase Audit supports granting the following permissions to Resource Access Management (RAM) users:
AliyunYundunDbAuditFullAccess: Grants a RAM user permission to manage Alibaba Cloud Security DataBase Audit (DBAudit). This policy includes read and write permissions. For more information, see Manage RAM user permissions.
AliyunYundunDbAuditReadOnlyAccess: Grants a RAM user read-only permissions for Alibaba Cloud Security DataBase Audit (DBAudit). For more information, see Manage RAM user permissions.
A RAM user authorization applies to the entire DataBase Audit service. You cannot grant permissions to a RAM user for a specific database that is configured in DataBase Audit. This applies to both ApsaraDB RDS databases and self-managed databases on ECS instances. A RAM user with DataBase Audit permissions can use the service for all configured databases, regardless of whether they have separate permissions for those individual databases.
Does DataBase Audit A100 support ApsaraDB PolarDB?
Yes. A100 supports ApsaraDB PolarDB. When you configure it, select the database type that corresponds to your database engine.
Does deleting the agent in CentOS mean deleting the /usr/local/rmagent folder?
Yes. To uninstall the agent in CentOS, follow these steps:
In the /usr/local/rmagent folder, run
./stop_rmagent.shto stop the agent process.Run the
pscommand. After you confirm that the rmagent process is stopped, delete /usr/local/rmagent.
The /tmp/rmagent folder stores the operational logs of the agent. You can also delete this folder after you uninstall the agent.
How do I delete the agent in Windows?
Open Control Panel, select Add or Remove Programs, find the agent program, and uninstall it.
Do I need to select local loopback when installing the agent?
Not always. You need to enable local loopback only if your database and application are on the same ECS instance.
Can I install the agent in a Docker environment?
Yes. You can install the agent in one of two ways:
Embed the agent in the image: The agent is built into the image. When the container starts, the agent runs automatically. The IP address of the server where the agent is located is not fixed. Join the DingTalk group (ID: 44519396) and contact a product technical expert for help.
Install the agent on the host: After you install the agent on the host, add the host's IP address to the whitelist in the agent management configuration. This ensures proper communication between the agent and the DataBase Audit service. For more information, see Deploy the agent program.
Do I need to consider the database type when I select a DataBase Audit edition?
No. DataBase Audit service editions are based on the number of databases that can be audited. When you purchase the service, select an edition based on the number of databases you plan to audit. For example, to audit one MongoDB database and one MySQL database, select the Professional Edition for three instances.
How do I configure the DataBase Audit service after I purchase it?
After you purchase a DataBase Audit instance, configure the service as follows:
How do I test the network connectivity for DataBase Audit?
You cannot test the network connectivity for DataBase Audit by pinging its IP address over the public network or an internal network. To test the connectivity, use telnet to connect to port 9266 of the DataBase Audit public IP address.
How do I verify that the DataBase Audit service is configured correctly?
After you configure the DataBase Audit service, you can view the statements audited by the system to verify the configuration.
If the number of statements is 0, check the agent program log to troubleshoot configuration issues.
The agent program log is typically stored in the following folders:
Windows: C:\tcmp\rmagent\rmagent_info.log
Linux: /tmp/rmagent/rmagent_info.log
If the following information appears in the agent program log, the agent program failed to connect to the DataBase Audit system: xml[INFO][tid=31235]20170322114351 rmagent.cpp:912:Rma_ConnectServer connect <IP address of the audit system>:9266 failed, Connection timed out
Solutions:
Check whether the IP address that has a connection timeout in the log matches the IP address of the DataBase Audit system that is displayed in the console. If not, change the IP address in the rmagent.ini configuration file to the correct IP address of the audit system.
The agent program communicates with the DataBase Audit system over port 9266. In the security group of the DataBase Audit instance, check whether port 9266 is open for inbound traffic over the internal network.
Why does an unknown user appear in the audit results?
Possible causes:
When you first enable auditing, if there are active sessions that have not been disconnected, they are audited as an unknown user. After a while, user information appears in the audited SQL statements.
If you need the user information to appear immediately, disconnect the application from the database and then reconnect.
When you access a SQL Server database by using a client application such as SqlDbx, the Tabular Data Stream (TDS) protocol is used for data transmission. During authentication, the user credentials are sent over a strongly encrypted SSL connection. As a result, Database Audit cannot decrypt the user information.
To ensure that user information is audited, we recommend that you do not access the SQL Server database through such client applications.
Does DataBase Audit support auditing databases that are connected through an SSH proxy host where rmagent is installed?
Yes, but only if the connection between the proxy host and the database is not SSL-encrypted.
Does DataBase Audit support viewing administrator operation logs?
Yes. You must first enable the system administrator and system auditor roles. Then, log on with the sysauditor account to view the administrator operation logs.
How do I uninstall, enable, and stop the agent program on a server?
Linux server
Uninstall: Run
uninstall.shin the installation folder.Enable: Run
dbagent_start.shin the installation folder.Stop: Run
dbagent_stop.shin the installation folder.
Windows server
Uninstall: Run
uninstall.batin the installation folder.Enable: Run
dbagent_start.batin the installation folder.Stop: Run
dbagent_stop.batin the installation folder.