cannot purge GTID for Aurora RDS mysql

To purge the GTID on the Aurora MySQL database after restoring from an on-premises MySQL database, you need the SUPER or SYSTEM_VARIABLES_ADMIN privilege. By default, the primary database user for Aurora MySQL clusters does not have these privileges.

A few things you can try:

Reset the primary database user password using the process documented in the AWS documentation. This will ensure you are using the latest credentials.

Check the permissions for the primary user by running

SHOW GRANTS FOR username;

. You may need to explicitly grant the required privileges.

Create a new database user with the required privileges and use that user to purge the GTIDs. You can grant privileges using commands like:

GRANT SUPER ON *.* TO 'username'@'host';

Check that the DB cluster parameter group associated with the Aurora cluster has gtid_mode set to OFF to disable GTID-based replication before purging GTIDs.

Refer to the AWS documentation on resetting GTID parameters and troubleshooting connection errors for more guidance. The documentation provides up-to-date information on required permissions and configuration.