Help Center/
Relational Database Service/
User Guide/
Working with RDS for MySQL/
Database Usage/
Account Management (Non-Administrator)/
Changing Permissions for a Database Account
Updated on 2024-10-14 GMT+08:00
Changing Permissions for a Database Account
Scenarios
You can authorize database users you have created to specific databases or revoke permissions from authorized database users.
Constraints
- Permissions cannot be changed for DB instances that are in the process of being restored.
- Databases and accounts created using other methods than the RDS console and APIs are also displayed on the RDS console. If the names of the created databases or accounts do not meet the database naming rule or account naming rule, for example, the names containing Chinese characters or unsupported special characters, the databases or accounts cannot be managed on the RDS console or through APIs.
- If the name of any database or account on the source database does not meet the database naming rule or account naming rule, the database or account cannot be managed on the RDS console or through APIs after being migrated to the destination RDS for MySQL instance.
Procedure
- Log in to the management console.
- Click in the upper left corner and select a region.
- Click in the upper left corner of the page and choose Databases > Relational Database Service.
- On the Instances page, click the DB instance name.
- In the navigation pane on the left, choose Accounts. On the Accounts page, locate the target username and click Change Permission in the Operation column.
- In the displayed dialog box, select unauthorized databases and click to authorize them. You can also select authorized databases and click to revoke permissions.
Figure 1 Changing permissions
- If there are no unauthorized databases, you can create one by referring to Creating a Database.
- If you require fine-grained permissions control, log in to the database through the DAS console.
- Click OK.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbot