Hey there, let's walk through your problems one by one to get you connected properly:

Why is MySQL Workbench still rejecting your root login after changing the password? #

There are a few common culprits here:

• Network/security group restrictions: This is the most frequent issue. Your RDS instance's security group might not have inbound rules allowing your local machine's IP address to access port 3306. Double-check the security group attached to your RDS instance—add a rule for MySQL/Aurora (3306) with your public IP as the source.
• Incorrect connection endpoint: Make sure you're using the full RDS endpoint URL (found in the RDS console under your instance details) instead of an EC2 IP or custom domain.
• Instance status delay: After modifying the root password, wait until the RDS instance status returns to available (it might show modifying for 30-60 seconds). Trying to connect during this window can fail.
• Password entry errors: Double-check for typos, case sensitivity, or special characters that might be misinterpreted (e.g., if your password has # or !, make sure you're entering them correctly without escaping).
• Public accessibility setting: If you're connecting from your local machine, ensure the RDS instance's Public accessibility is set to Yes (in the instance's connectivity settings). If it's No, you can only connect from resources within the same VPC.

Can you create a new user and password? #

Absolutely—and this is actually the recommended best practice (avoid using the root/master user for application connections). Here's how to do it once you get logged in:

1. First, connect to your RDS instance via command line (if Workbench is still giving trouble):

   mysql -h your-rds-endpoint.rds.amazonaws.com -P 3306 -u root -p
   

2. Create a new user (replace placeholders with your details):

   CREATE USER 'app_user'@'%' IDENTIFIED BY 'strong_unique_password';
   

   The % allows connections from any IP—you can restrict this to your application's IP if needed (e.g., 'app_user'@'192.168.1.100').
3. Grant necessary permissions to the user (adjust the database name and privileges based on your app's needs):

   GRANT SELECT, INSERT, UPDATE, DELETE ON your_app_database.* TO 'app_user'@'%';
   

4. Flush privileges to apply the changes:

   FLUSH PRIVILEGES;
   

How long does a new master password take to take effect? #

In most cases, the new master password takes effect immediately once the RDS instance finishes modifying its settings. This process usually takes 30 seconds to 2 minutes, and you'll see the instance status switch back to available. If you're still having issues after waiting, it's almost certainly not a password delay—go back and check the network/connection settings mentioned earlier.

内容的提问来源于stack exchange，提问作者Boris K