EFS Monitoring tab can help you look into those metrics, there is a settings icon above the charts on the right side, which then you can add Permitted throughput & Burst Credit balance. If those are critical metrics for you, I'd recommend adding AWS CloudWatch alarms (https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/AlarmThatSendsEmail.html) when reaching specific threshold.
Regarding burst credits accumulated in Provisioned mode, they won't be used unless you switch back to Burst mode.
With 20GB storage being used in Burst mode, EFS can drive a throughput of 1 MiB/s, and up to 100 Mib/s if burst credits are available. Burst credits accrue in proportion to the file system's size at the file system's base rate. 50 MBps of burst credits are accrued for every TB of storage. Your EFS file storage will accumulate burst credits if it is inactive or driving throughput below its baseline rate. For example, your 20-GiB file system can burst (at 100 MiB/s) for 1 percent of the time if it's inactive for the remaining 99 percent. Over a 24-hour period, the file system earns 86,400 MiBs worth of credit, which can be used to burst at 100 MiB/s for 14.4 minutes.
One solution is you could be adding dummy data to increase the system storage size so you accumulate more burst credits and get a higher baseline throughput.
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 months ago
- How can I troubleshoot the error "nfs: server 127.0.0.1 not responding" when mounting my EFS file system?AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 3 months ago
- EXPERTpublished 5 months ago
- EXPERTpublished a year ago