The monitoring service allows you to monitor in real time the parameters of instances, volumes, Auto Scaling Groups and buckets. By creating alarms, you can setup automatic actions when parameters of a monitored resource fall beyond the pre-defined range.

You can configure monitoring of specific resources via the web interface in the Monitoring section. In the monitoring service, there are two main types of entities: alarms and metrics. Accordingly, the main menu contains two subsections: Alarms and Metrics.


In addition to the web interface, you can also use CloudWatch API to handle metrics and alarms.

Access rights#

All users with the VM administrator role get access to the Monitoring service automatically. If necessary, you can create a separate role to work with the service (or add the respective privilege to other roles).

Go to the IAM section to create a role, then switch to the Roles subsection and click Create. After creating the role, select the actions with the monitoring service, which will be permitted for the role. To learn how to work with role templates, read here.

Monitoring service limitations#

When working with the monitoring service, you should take into account the following limitations.



Number of alarms


Number of notification recipients (emails)


Storage time for metric values, days


The retention period for alarm history, days


Metric collection period (except bucket metrics), minutes


Metric collection period for bucket metrics, hours


If necessary, you can increase quotas. To do this, contact the support service.