RDS for Mysql maridadb audit plugin lead to seriously high readthroughput

Question

I am using RDS for mysql, t3.micro with 200GB storage (gp2) 
I enabled MARIADB_AUDIT_PLUGIN in my option group. 
It works well but my readthroughput went too high(**UP to 100MB/seconds **) that my EBSbytebalance is exhausted.
My readthroughput is still **10MB/s** after EBSBytebalance exhausted.
I have no heavy query.
Any other meterics like writethroughput (only a few hundred bytes per second) , cpu, memory are just normal.

Answer

Dear Customer,

Thanks for reaching out to us via the re-post forum.

I have gone through your question and here are my findings/suggestions

Please check what parameters are being logged through the plug in. You can reduce the parameters and select lesser parameters between CONNECT, QUERY, QUERY_DDL, QUERY_DML, QUERY_DML_NO_SELECT, QUERY_DCL

https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Appendix.MySQL.Options.AuditPlugin.html#Appendix.MySQL.Options.AuditPlugin.Options
Also you can further filter down the logging by using SERVER_AUDIT_INCL_USERS or SERVER_AUDIT_EXCL_USERS

Please also check the Write Throughput that the instance is serving. On a side note I would also like to add that IF possible, please add a read replica to the instance to offload read workload and keep the primary load under check.

I sincerely hope I was able to shed some light on the matter for you today. In case you have any further queries please feel free to respond. Have a great rest of the day!

RDS for Mysql maridadb audit plugin lead to seriously high readthroughput

Relevant content