Documentation Home
MySQL Enterprise Monitor 8.0 Manual
Related Documentation Download this Manual
PDF (US Ltr) - 6.0Mb
PDF (A4) - 6.0Mb

16.4 Monitoring Amazon RDS

This section describes how to monitor a MySQL instance in an cloud environment, such as the Amazon Relational Database Service (Amazon RDS).


It is recommended that you use MySQL 5.6, or later, on RDS. It is also possible to use MySQL 5.5, but you must disable backup and replicas before attempting to monitor it using MySQL Enterprise Service Manager. After the agent has connected, you can enable backup and replicas again.

Remote monitoring is used when monitoring on a cloud. You can use any MySQL Enterprise Monitor Agent to monitor MySQL instances remotely, including the built-in agent that is automatically installed and started with MySQL Enterprise Service Manager.

When configuring a MySQL instance to monitor from the Instances view, do the following:

  • Do not configure MySQL Enterprise Monitor to auto-create the less privileged Limited and General accounts, and instead use the Admin account for all monitoring.

    This is set in the Connection Settings tab when adding or editing a MySQL instance to be monitored. The Auto-Create Less Privileged Users setting defaults to Yes, ensure it is set to No.

  • Also under Connection Settings is the Instance Address parameter. Set this to your endpoint, which is the entry point for your MySQL Server web service.

  • Change the inventory table schema for MySQL Enterprise Monitor Agent from "mysql" to an existing, alternative schema.

    This is set in the Advanced Settings tab when adding (or editing) a MySQL instance to be monitored. The Inventory Table Schema setting defaults to mysql, which is typically not accessible to the Agent user in a cloud (or shared) environment. Change it to a schema you created.

Your MySQL instance is displayed on the Instances view.


MySQL Performance Schema is not enabled by default on Amazon RDS. If you intend to use Query Analyzer, you must enable Performance Schema by setting the performance_schema parameter to 1 in instance parameter group on the AWS console and restart the instance.