AWS MySQL error 1419 usually happens in the process of copying databases to Amazon RDS.
Here at Ibmi Media, as part of our Server Management Services, we regularly help our Customers to resolve related AWS queries.
In this context, we shall look into methods to resolve AWS MySQL error 1419.
When automated backup is enabled for a MySQL DB instance, it also enables binary logging.
You might receive the following error message when creating a trigger:
ERROR 1419 (HY000): You do not have the SUPER privilege and binary logging is enabled (you might want to use the less safe log_bin_trust_function_creators variable)
This error can happen when the log_bin_trust_function_creators parameter is missing.
Amazon RDS is a managed service, and it doesn’t provide SYS access (SUPER privileges).
If binary logging is enabled on your MySQL DB instance, set the log_bin_trust_function_creators parameter to true in the custom DB parameter group that you create for your DB instance.
If you create a DB instance without specifying a DB parameter group, Amazon RDS creates a new default DB parameter group.
Now, do the following steps to resolve the error:
You can modify parameter values in a customer-created DB parameter group. Changes to parameters in a customer-created DB parameter group are applied to all DB instances that are associated with the DB parameter group.
The RDS console shows the status of the DB parameter group associated with a DB instance on the Configuration tab.
For example, if the DB instance isn’t using the latest changes to its associated DB parameter group, the RDS console shows the DB parameter group with a status of pending-reboot.
To apply the latest parameter changes to that DB instance, manually reboot the DB instance.
Follow the steps below to modify a DB parameter group:
This article covers methods to resolve AWS MySQL error 1419. When automated backup is enabled for a MySQL DB instance, it also enables binary logging.
You might receive the following error message when creating a trigger: "ERROR 1419 (HY000): You do not have the SUPER privilege and binary logging is enabled (you might want to use the less safe log_bin_trust_function_creators variable)".