We can enable and disable Enhanced Monitoring in AWS RDS using the AWS Management Console, AWS CLI, or RDS API.

Here, at Bobcares, we assist our customers with several AWS queries as part of our AWS Support Services.

Today, let us discuss Enhanced Monitoring in AWS RDS.

Enable and Disable Enhanced Monitoring in AWS RDS

We can do this when we create a DB instance or read replica, or when we modify a DB instance.

If we modify a DB instance to enable Enhanced Monitoring, the changes will take effect without a reboot.

• Console

Moving ahead, let us see how our Support Techs perform this using the RDS console.

Initially, we scroll to the Monitoring section.

Here, we select Enable Enhanced Monitoring for the DB instance or read replica.

Similarly, to disable Enhanced Monitoring, we select the Disable option.

For Amazon RDS to communicate with Amazon CloudWatch Logs, we set the Monitoring Role property to the IAM role.

Or we can select Default to have RDS create the role, rds-monitoring-role.

We also set the Granularity property to the interval, in seconds, between points when metrics are collected.

For this, we can use one of the following values: 1, 5, 10, 15, 30, or 60.

• AWS CLI

To do this, we need to set the –monitoring-interval option to a value other than 0.

This option specifies the interval, in seconds, between points when Enhanced Monitoring metrics are collected.

On the other hand, to disable, we set the –monitoring-interval option to 0.

For example, here our Support Techs enables Enhanced Monitoring for a DB instance:

Linux, macOS, or Unix:

aws rds modify-db-instance \
--db-instance-identifier mydbinstance \ --monitoring-interval 30 \ --monitoring-role-arn arn:aws:iam::123456789012:role/emaccess

Windows:

aws rds modify-db-instance ^
--db-instance-identifier mydbinstance ^ --monitoring-interval 30 ^ --monitoring-role-arn arn:aws:iam::123456789012:role/emaccess

• RDS API

In the case of RDS API, we set the MonitoringInterval parameter to a value other than 0.

We can set these parameters in the following actions:

1. CreateDBInstance
2. CreateDBInstanceReadReplica
3. ModifyDBInstance

To disable, we set the MonitoringInterval to 0.

Conclusion

in short, we saw how our Support Techs enable and disable Enhanced Monitoring for our customers.