Support for log_error_suppression_list in MySQL8 Parameter Groups

We have the same problem. The error logs aren't usable anymore. RDS team: please add support for log_error_suppression_list in MySQL 8 parameter group

Just spoke with AWS and they mentioned that "I would like to let you know that our development team is aware of this limitation and there is already plan in place to have "default_authentication_plugin" modifiable in the future. Currently, we are unable to provide ETA when this will be done, however, as soon as its gets released, it will be publicly announced in either one of the following links noted below".

AWS RDS Blog: https://aws.amazon.com/blogs/aws/category/amazon-rds/ AWS RDS forum: https://forums.aws.amazon.com/forum.jspa?forumID=60 What's new blog: https://aws.amazon.com/new/

This is still an ongoing issue with the 8.0.35 release..

Also having the same issue after updating user credentials to use caching_sha2_password. I wonder if it's related to the rdsadmin account still being set to mysql_native_password, which I don't think we can update. It is unclear whether rdsadmin may be getting used by AWS for duplication, monitoring, etc.

We would also like to see support added for this parameter, especially as the rdsadmin account does not support the caching_sha2_password setting and our logs have a good number of warning messages related to the deprecated authentication plugin.

We're having the same problem, as over 7million alarms are being logged in Cloudwatch each month, that's burning the AWS bill badly.

Can the RDS team add support for log_error_suppression_list in MySQL 8 parameter groups please?

I'm about to update my Mysql 5 RDS instance to Mysql 8, given that now Mysql 5 will only be supported via extended support, which for my usage is x3-x4 the price of my current RDS bill.

We need a way to remove the warning message but also a way to configure the mysql_native_password in the related default group so everyone impacted has multiple choices at hand to ease their migration process.

I believe support for similar needs will rise until February 24th, when newcomers start to work on it.

The issue still continues.

We've recently upgraded MySQL Engine from 5.7.44 to 8.0.36 (April 22, 2024, 21:00, UTC). And I still got the same log.

2024-04-24T08:10:00.229029Z 8097847 [Warning] [MY-013360] [Server] Plugin mysql_native_password reported: ''mysql_native_password' is deprecated and will be removed in a future release. Please use caching_sha2_password instead'

Has anyone upgraded to .36 ? Does it fix the [MY-013360] [Server] Plugin mysql_native_password reported: ''mysql_native_password' is deprecated errors? I also see that **rdsrepladmin **and **rdsproxyadmin **are still using mysql_native_password. Can these be changed to caching_sha2_password?

Same issue.

My environment is: Wordpress 6.4.2 / php-fpm 8.2 and Mysql 8.0.35. I've change the field "plugin" on users table from "mysql_native_password" to "caching_sha2_password" and warning logs still reporting. Hope a deploying for this log_error_suppression_list feature.

The absence of support for log_error_suppression_list and default_authentication_plugin is a significant inconvenience.

To address this issue, we've disabled automatic minor version upgrades on the majority of our databases. However, for those left enabled for testing purposes, the warning surfaced in logs following the upgrade from 8.0.33 to 8.0.35. Oracle's decision to log this warning at every login poses a substantial challenge, particularly for high-traffic databases.

Presently, the available options are either setting log_error_verbosity to 1 to suppress all warnings from being logged, or ensuring that the upgrade does not go beyond version 8.0.33.

Code changes and updates to users in the database to use the new authentication plugin will not fully resolve the issue due to the absence of default_authentication_plugin support.

AWS must promptly notify customers about this issue due to the restricted workaround options, or address it accordingly. Failure to address this could result in unforeseen high bills and complications in diagnosing other issues triggered by warnings now obscured by this particular warning.

This issue is still in July 2024, anyone from AWS has any answer for us the customers? this scenario impacts the bills and the user's database connection.

[MY-010926] [Server] Access denied for user '' (using password: YES) (sql_authentication.cc:1459)

facing same error