ECS - Incident Detection and Response Alarming Best Practices

2 minuto de leitura
Nível de conteúdo: Intermediário
0

The intention of this documentation is to provide the building blocks to create critical CloudWatch alarms which are fit for onboarding to Incident Detection and Response. It contains specific alarm best practices for AWS Services.

Overview

Here we have included Alarm Best Practices for ECS that Incident Detection and Response (IDR) customers can refer to. They can use these best practices as a starting point in creating alarms fit to be onboarded to IDR. There are also AWS recommended alarms available, which customers may make use of.

The CloudWatch alarm best practices provided on this page are intended solely as general guidelines to assist you in configuring alarms for the Incident Detection and Response service. The final selection, configuration, and implementation of CloudWatch alarms should be tailored to the unique requirements of your environment, workloads, and operational needs. The recommendations we provide do not guarantee comprehensive coverage or detection of all issues, incidents, or outages. For more information on detailed configuration, we recommend consulting with your technical team.

Recommended Metrics to Monitor

Prerequisite: Use CloudWatch Container Insights to collect, aggregate, and summarize metrics and logs from your containerized applications and microservices. The feature is disabled by default, so an admin will need to enable manually for each ECS cluster.

ECS Best Practices Alarms

Additional Resources

For additional information on CloudWatch metrics and dimensions for ECS please refer to the following documentation: ECS CloudWatch Metrics.

For additional information on general recommended best practice alarming for ECS with Container Insights please see the following documentation: CloudWatch - Recommended alarms for ECS with Container Insights.