Home/ Questions/Q 7893651
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-03T07:11:13+00:00

I’m trying to create a trigger on a table in my Amazon RDS database,

  • 0

I’m trying to create a trigger on a table in my Amazon RDS database, and I can’t seem to make it happen.

I tried to create a trigger on a table in the mysql client I use (Navicat), and got the error that I needed the SUPER privilege to do so. After some searching, I found that you could SET GLOBAL log_bin_trust_function_creators = 1 to get around this. I tried that using these instructions: http://getasysadmin.com/2011/06/amazon-rds-super-privileges/ (and then restarting the DB server for good measure), but no luck.

I also tried creating the trigger and setting the variable via the mysql commmand line to make sure Navicat wasn’t adding anything unwanted to my sql commands, but that failed, too. It also seems from searching that there’s no way to grant yourself the SUPER privilege.

So … is creating a trigger possible in RDS?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    No it is actually not impossible it just takes far too much extra work.

    First off it seems to be impossible to apply Super Privileges to a default parameter group.
    So what I had to do was to create a new DB Parameter group either through the Console, or the CLI.

    What I found was, the key is that the default region was not the region I was trying to use so I had to use a –region parameter to apply it to the group in the correct region where I was deploying my DB Instance 

    rds-create-db-parameter-group --db-parameter-group-name allow-triggers --description 'parameter group to allow triggers' --region your-region

    Next I had to create a DB Instance which used that parameter group. (Again through the console or CLI)

    rds-create-db-instance

    Then I had to modify the Parameter group to allow log_bin_trust_function_creators only accomplishable through the CLI

    rds-modify-db-parameter-group --db-parameter-group-name yourgroupname --region yourRegion --parameters 'name=log_bin_trust_function_creators,value=true,method=immediate'

    Lastly I had to modify the created DB Instance to allow triggers, also CLI only.

    rds-modify-db-instance --db-instance-identifier your-db-instance-id --db-parameter-group-name allow-triggers --apply-immediately
    • 0