Monitor EFS file systems with CloudWatch metrics and alarms
Michael Wittig – 27 Mar 2018 (updated 17 Aug 2021)
Many applications depend on a shared file system to exchange state. An Amazon EFS file system can be mounted to multiple EC2 instances to share files between the instances. But the EFS file system is a finite resource that can be exhausted. That’s why you need to add monitoring to be alerted if the file system gets a bottleneck.
Each EFS file system sends metrics to CloudWatch that we can monitor with CloudWatch alarms. We recommend creating alarms for the following metrics:
BurstCreditBalance: The number of burst credits that a file system has.
PercentIOLimit: Shows how close a file system is to reaching the I/O limit of the General Purpose performance mode. If this metric is at 100 percent more often than not, consider moving your application to a file system using the Max I/O performance mode.
Unfortunately, EFS does not report a single metric on the throughput utilization of the file system. But we can calculate throughput by using CloudWatch metric math. Luckily, AWS shares the formula to calculate the percentage of permitted throughput utilization.
CloudWatch metric math sounds complicated? We have you covered! Monitor EFS and receive alerts in Slack or Microsoft Teams!
Take your AWS monitoring to a new level! Chatbot for AWS Monitoring: Configure monitoring, escalate alerts, solve incidents.