AWS EFS Integration
Monitor file system throughput, burst credits, and client connection metrics across your EFS file systems. Get AI-powered burst credit depletion prediction before throughput throttling impacts your workloads.
How It Works
Create IAM Role for Metric Streams
Provision an IAM role with CloudWatch permissions scoped to the AWS/EFS namespace. TigerOps uses this role to deliver EFS file system throughput and connection metrics.
Deploy CloudWatch Metric Streams
Run the TigerOps CloudFormation stack to stream the AWS/EFS namespace. Throughput, burst credit balance, and client connection metrics begin flowing to TigerOps immediately.
Tag File Systems by Workload
Apply application and team tags to your EFS file systems. TigerOps uses these tags to route burst credit depletion alerts to the right team and group throughput metrics by application.
Configure Burst Credit Alerts
Set minimum burst credit balance thresholds per file system. TigerOps calculates burst credit depletion rates and alerts before throughput throttling impacts workloads.
What You Get Out of the Box
File System Throughput
Total, read, and write throughput per EFS file system with historical trending. Track throughput utilization against provisioned throughput limits for Provisioned Throughput mode.
Burst Credit Monitoring
BurstCreditBalance tracking with depletion rate analysis. TigerOps predicts when burst credits will be exhausted and alerts before throughput throttling impacts connected workloads.
Client Connection Tracking
Active client connections per file system over time. Detect unexpected connection count spikes or drops that indicate NFS mount issues or application connection leaks.
I/O Operations Metrics
Total, metadata, and data I/O operations per second with read/write breakdown. Identify file systems with metadata-heavy workloads that may benefit from General Purpose vs Max I/O mode.
Provisioned Throughput Utilization
For EFS Provisioned Throughput file systems, track actual throughput as a percentage of provisioned capacity. Right-size provisioned throughput to balance cost and performance.
AI Throughput Saturation Detection
TigerOps establishes per-file-system throughput baselines and alerts when utilization approaches limits, correlating saturation with specific EC2 instances or containers that are heavy consumers.
CloudFormation Stack for EFS Metric Streams
Deploy the TigerOps CloudFormation stack to start streaming EFS throughput and burst credit metrics in minutes.
# TigerOps CloudFormation — EFS Metric Streams
# aws cloudformation deploy \
# --template-file tigerops-efs-streams.yaml \
# --stack-name tigerops-efs \
# --capabilities CAPABILITY_IAM
Parameters:
TigerOpsApiKey:
Type: String
NoEcho: true
Resources:
TigerOpsEFSStream:
Type: AWS::CloudWatch::MetricStream
Properties:
Name: tigerops-efs-stream
FirehoseArn: !GetAtt TigerOpsDeliveryStream.Arn
RoleArn: !GetAtt MetricStreamRole.Arn
OutputFormat: opentelemetry0.7
IncludeFilters:
- Namespace: AWS/EFS
TigerOpsDeliveryStream:
Type: AWS::KinesisFirehose::DeliveryStream
Properties:
HttpEndpointDestinationConfiguration:
EndpointConfiguration:
Url: https://ingest.atatus.net/api/v1/cloudwatch
AccessKey: !Ref TigerOpsApiKey
RequestConfiguration:
CommonAttributes:
- AttributeName: service
AttributeValue: efs
RetryOptions:
DurationInSeconds: 60
# Recommended alert thresholds:
# BurstCreditBalance < 1500000000000 → Warning (1.5TB credits)
# BurstCreditBalance < 500000000000 → Critical (0.5TB credits)
# PercentIOLimit > 80% → Warning (General Purpose mode)
# ClientConnections sudden drop > 50% → Possible NFS mount issueCommon Questions
Which EFS metrics does TigerOps collect?
TigerOps collects all AWS/EFS CloudWatch metrics including BurstCreditBalance, ClientConnections, DataReadIOBytes, DataWriteIOBytes, MetadataIOBytes, TotalIOBytes, PercentIOLimit, PermittedThroughput, and MeteredIOBytes per file system.
Does TigerOps support EFS Elastic Throughput mode monitoring?
Yes. EFS Elastic Throughput mode does not use burst credits. TigerOps detects the throughput mode of each file system and adjusts dashboards accordingly, showing throughput utilization relative to the Elastic mode limits rather than burst credit balance.
How does TigerOps help identify which workloads are consuming burst credits?
TigerOps correlates burst credit consumption rate with EFS ClientConnections and with CloudWatch Container Insights metrics from ECS or EKS tasks that have the file system mounted. This identifies the specific workload driving burst credit depletion.
Can TigerOps monitor EFS replication across regions?
Yes. EFS replication metrics are published to CloudWatch including LastReplicatedTimestamp and replication lag. TigerOps tracks replication lag for disaster recovery file systems and alerts when replication falls behind the configured RPO threshold.
Does TigerOps monitor EFS Access Points?
EFS Access Points are logical endpoints and do not publish separate CloudWatch metrics — all I/O flows through the underlying file system metrics. TigerOps monitors at the file system level and can correlate with application-level tags for access point attribution.
Stop Getting Surprised by EFS Burst Credit Exhaustion at Peak Load
Throughput monitoring, burst credit depletion prediction, and AI saturation detection. Deploy in 5 minutes.