Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>I followed the above but it did not work for me. I spent almost a day to figure out why it is not working and now I know why. I am listing down steps that I followed to make it work.</p> <p>Created mysql parameters group using aws web console (make sure that it should have same family as the default parameter group. Earlier, I had created a parameter group but it had different family and so it did not work. This is critical step.</p> <p>Using aws web console change value of <code>log_bin_trust_function_creators</code> to <code>1</code></p> <p>Apply new parameter group. This is another critical step</p> <pre><code>rds-modify-db-instance –I $AWS_ACCESS_KEY –S $AWS_SECRET_KEY –region $EC2_REGION \ –db-instance-identifier $DB_INSTANCE \ –db-parameter-group-name $DB_GROUPNAME \ –apply-immediately </code></pre> <p>You need RDSCli from - <a href="http://s3.amazonaws.com/rds-downloads/RDSCli.zip" rel="nofollow">http://s3.amazonaws.com/rds-downloads/RDSCli.zip</a></p> <p>Then verify if parameter group is associated with your db instance</p> <pre><code>rds-describe-db-instances \ –I $AWS_ACCESS_KEY \ –S $AWS_SECRET_KEY \ –region $EC2_REGION </code></pre> <p>And then reboot before you try creating trigger</p> <pre><code>rds-reboot-db-instance \ –I $AWS_ACCESS_KEY \ –S $AWS_SECRET_KEY \ –region $EC2_REGION \ –db-instance-identifier $DB_INSTANCE </code></pre> <p>Remember to set below environment variable before you try above commands.</p> <pre><code>export AWS_ACCESS_KEY=’*****’ export AWS_SECRET_KEY=’*****’ export EC2_REGION=’region’ export AWS_RDS_BIN=”$AWS_RDS_HOME/bin” export PATH=$PATH:$AWS_RDS_BIN export JAVA_HOME=c:/jdk1.6_25 (in most cases this is already set) </code></pre> <p>Thanks to <a href="http://blog.iprofs.nl/2013/03/20/rds-database-triggers-for-mysql/" rel="nofollow">http://blog.iprofs.nl/2013/03/20/rds-database-triggers-for-mysql/</a> for full details.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload