- 최신
- 최다 투표
- 가장 많은 댓글
Actually I find out better solution then those two. For people who have the same issue follow this steps:
1- Open your rds instance page
2- Click "Actions" button at the top right.
3- Click "Set up ec2 connection"
4- Create your database - ec2 connection by following the steps that is showed up when you clicked
5- Connect to the instance that is connected with your database
6- If you are using linux as ec2 instance write this command,
mysql -h <DBendpoint> -P <DBport> -u <username> -p
7- after executing this command mysql should be opened, run this query,
ALTER USER 'your_username'@'%' IDENTIFIED WITH caching_sha2_password BY 'your_new_password';
After this steps all of my problems I just mentioned solved.
⚡ This article might help you resolve the error MySQL 8.0.34 Upgrade and tons of MY-013360 ‘mysql_native_password’ is deprecated warnings. A similar issue was addressed three months ago in this repost.aws article: Getting rid of warning: plugin mysql_native_password reported 'mysql_native_password is deprecated'.
ATTENTION: This operation will not work if you intend to use the rds proxy endpoint read only or read write, because the "Authentication" with Secrets have only Client Authentication type: MySQL Native password.
Confirmed in https://docs.aws.amazon.com/pt_br/AmazonRDS/latest/UserGuide/rds-proxy.html
"RDS Proxy doesn't support the MySQL sha256_password and caching_sha2_password authentication plugins. These plugins implement SHA-256 hashing for user account passwords."
If you use, do you receive this message: Error: "ERROR 1045 (28000): Access denied for user 'DB_USER'@'%' (using password: YES)"
Causes or workarounds: "The Secrets Manager secret used by the proxy doesn't match the user name and password of an existing database user. Either update the credentials in the Secrets Manager secret, or make sure the database user exists and has the same password as in the secret."
관련 콘텐츠
- AWS 공식업데이트됨 3년 전