Monitoring#

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.

Note

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

Access rights#

All users from the InstanceAdministrators group get access to the Monitoring service automatically. If necessary, you can create a separate policy or group to work with the service (or add the respective privilege to the groups or policies you created) and assign it to a user.

To create a policy, go to the Policies subsection in the IAM section, click Create, and select the monitoring service actions allowed for it. You can also use predefined policies CloudWatchFullAccess and CloudWatchReadOnlyAccess . The former grants all permissions to work with the service, while the latter provides read-only access. Then, if necessary, create a group and add the created policy to the group.

For more details on working with groups and policies, see IAM documentation.

Monitoring service limitations#

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

Value

Limitation

Number of alarms

100

Number of notification recipients (emails)

5

Storage time for metric values, days

7

The retention period for alarm history, days

7

Metric collection period (except bucket metrics), minutes

1

Metric collection period for bucket metrics, hours

1

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