This alert monitors unusual spikes in client connections to an AWS EFS. Such spikes can indicate unexpected usage patterns, potential security issues, or misconfigured applications. The alert is triggered when the number of client connections exceeds a predefined threshold, representing a significant deviation from the typical connection baseline within a 10-minute period. Monitoring this metric helps ensure that the EFS operates securely and efficiently, avoiding potential performance degradation or unauthorized access. Customization Guidance: - Threshold: Set the threshold based on normal connection patterns for your EFS usage. Consider historical data and usage trends when defining this value. - Monitoring Period: Adjust the monitoring period to detect spikes more effectively during high-usage or off-peak hours. - Notification Frequency: Configure notifications to minimize noise while ensuring timely response to unusual spikes. Action: If this alert is triggered, consider investigating the source of the connections, reviewing access permissions, and validating application configurations. If necessary, take steps to mitigate unauthorized or excessive usage.

This alert monitors the depletion of burst credits in an AWS EFS. Burst credits are used to sustain higher throughput for file operations, and their depletion can result in reduced performance. The alert is triggered when the burst credit balance falls below a predefined threshold, indicating that the system may soon experience throughput throttling. Monitoring this metric helps ensure consistent file system performance and prevents application slowdowns due to throughput limitations. Customization Guidance: - Threshold: Set the threshold based on the typical burst credit consumption pattern and workload requirements. For critical workloads, use a higher threshold to allow proactive action. - Monitoring Period: Adjust the monitoring period to reflect your workload's typical burst usage cycles (e.g., hourly, daily peaks). - Notification Frequency: Configure notifications to avoid excessive alerts but ensure timely awareness of credit depletion. Action: If this alert is triggered, consider increasing the provisioned throughput, optimizing workload patterns to reduce burst credit usage, or scaling up the file system to handle higher demands.

This alert monitors the I/O utilization of an AWS Elastic File System (EFS) nearing its configured limits. High I/O utilization can lead to performance bottlenecks, impacting application functionality and user experience. The alert is triggered when I/O operations approach 80% or more of the provisioned or burst throughput capacity over a 10-minute period. Monitoring this metric helps ensure the EFS maintains optimal performance and prevents throughput throttling that can disrupt dependent applications. Customization Guidance: - Threshold: Adjust the threshold based on your file system's provisioned throughput or observed workload patterns. Lower thresholds can provide earlier warnings. - Monitoring Period: Modify the monitoring period to capture sustained high usage rather than transient spikes. - Notification Frequency: Set notification frequency to avoid alert fatigue while ensuring timely response to sustained high utilization. Action: If this alert is triggered, consider increasing the provisioned throughput, optimizing application I/O patterns, or distributing the workload across multiple file systems to prevent performance degradation.

This alert monitors the I/O utilization of an AWS Elastic File System (EFS) nearing its configured limits. High I/O utilization can lead to performance bottlenecks, impacting application functionality and user experience. The alert is triggered when I/O operations approach more of the provisioned or burst throughput capacity over a 10-minute period. Monitoring this metric helps ensure the EFS maintains optimal performance and prevents throughput throttling that can disrupt dependent applications. Customization Guidance: - Threshold: Adjust the threshold based on your file system's provisioned throughput or observed workload patterns. Lower thresholds can provide earlier warnings. - Monitoring Period: Modify the monitoring period to capture sustained high usage rather than transient spikes. - Notification Frequency: Set notification frequency to avoid alert fatigue while ensuring timely response to sustained high utilization. Action: If this alert is triggered, consider increasing the provisioned throughput, optimizing application I/O patterns, or distributing the workload across multiple file systems to prevent performance degradation.