Amazon Aurora Publishes General, Slow Query and Error Logs to Amazon CloudWatch
You can now configure the MySQL-compatible edition of Amazon Aurora to publish general logs, slow query logs, and error logs to Amazon CloudWatch Logs. Previously, you could only publish audit logs.
Publishing Aurora logs to CloudWatch Logs allows you to maintain continuous visibility into database activity, query performance, and database errors. For example, you can set up CloudWatch Alarms to notify you on frequent restarts that are recorded in the error log.
Similarly, alarms for events recorded in general or audit logs can be created to alert on unwanted changes made to your databases. Alarms on the slow query log may, for example, enable timely detection of long-running queries. Aurora uses a Service Linked Role (SLR) for publishing logs to CloudWatch Logs.
CloudWatch Logs provide a durable archive destination for your database logs, and you can specify the desired retention period. Additionally, CloudWatch Logs supports ad hoc searches across multiple logs. This is particularly useful for troubleshooting, audits, and log analysis, combining logs generated by the database with logs from other layers of the application stack.
Read more about Aurora and CloudWatch on the AWS Database blog, and refer to the Aurora MySQL documentation for more information. To start publishing logs from Aurora to CloudWatch Logs, visit the RDS management console or download the latest AWS SDK or CLI.
Aurora combines the performance and availability of high-end commercial databases with the simplicity and cost-effectiveness of open source databases. See the AWS Region Table for complete regional availability.