# CloudWatch alarm for Amazon ECS EBSFilesystemUtilization

CloudWatch alarms · Updated 16 November 2026

**Short answer:** EBSFilesystemUtilization is how full the file systems on EBS volumes attached to a service's ECS tasks are, as a percentage. AWS recommends alarming on the Average for ClusterName and ServiceName above 80% for 5 of 5 one-minute periods. A full volume makes writes fail and often brings the container down.

## What the metric covers

ECS can create and attach an EBS volume to each task at launch, configured in the service's volume configuration rather than on a host. This metric reports how much of those volumes' file systems is used, averaged across the service's tasks. It is only published for services that use ECS-managed EBS volumes; bind mounts and Fargate ephemeral storage have their own metrics.

What fills these volumes depends on how you use them:

- **Active data** (a database, a queue spool, a build cache): growth is expected, and high utilisation means the application will soon fail writes.
- **Volumes created from a snapshot** with reference data: a high percentage may simply mean the volume is sized to fit, and nothing will grow.
- **Logs or temp files** written to the volume and never rotated: a slow, steady climb.

## Recommended alarm settings

| Setting | Value |
|---|---|
| Namespace | `AWS/ECS` |
| Metric | `EBSFilesystemUtilization` |
| Dimensions | `ClusterName`, `ServiceName` |
| Statistic | `Average` |
| Period | 60 seconds |
| Datapoints to alarm | 5 |
| Evaluation periods | 5 |
| Comparison operator | `GreaterThanThreshold` |
| Threshold | 80.0 (percent) |

As given in AWS's [recommended alarms](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Best_Practice_Recommended_Alarms_AWS_Services.html) list for ECS.

## Tuning

For a snapshot-based, read-only volume, either raise the threshold close to the volume's steady value or skip the alarm. For data volumes, base the threshold on growth rate: if usage grows by 2% a day, 80% leaves about ten days to react, which is comfortable; if it can grow 10% in an hour during a batch job, alarm lower. Because the metric is an average across tasks, a single task with a full volume can hide among healthy ones; Container Insights reports task-level EBS metrics (see [task EBS file system utilisation](https://cloudconsole.dev/alarms/ecs-insights-taskebsfilesystemutilization)) if you need that granularity.

## Create it

```
aws cloudwatch put-metric-alarm \
  --alarm-name prod-ingest-ebs-usage \
  --namespace AWS/ECS \
  --metric-name EBSFilesystemUtilization \
  --dimensions Name=ClusterName,Value=prod Name=ServiceName,Value=ingest \
  --statistic Average \
  --period 60 \
  --evaluation-periods 5 \
  --datapoints-to-alarm 5 \
  --threshold 80 \
  --comparison-operator GreaterThanThreshold \
  --alarm-actions arn:aws:sns:eu-west-2:123456789012:ops-alerts \
  --region eu-west-2
```

## When it fires

1. **Find what is using the space.** Open a shell in a task with [ECS Exec](https://cloudconsole.dev/how-to/ecs-exec-into-container) and run `du -xh /data | sort -h | tail` on the mount path.
2. **Clean up what should not be there**: rotated logs, temp files, old cache entries. Add retention to the application so it does not recur.
3. **Increase the size for new tasks.** Update the service's volume configuration with a larger `sizeInGiB`; tasks launched afterwards get the new size, and a forced deployment replaces the existing ones ([force new deployment](https://cloudconsole.dev/how-to/force-new-deployment-ecs)).
4. **Check the impact.** Stopped tasks with write errors show up as exits in the service events; see [essential container exited](https://cloudconsole.dev/errors/ecs-essential-container-exited).

## Questions

### Can I resize the EBS volume of a running ECS task?

Not in place through ECS. Change the volume size in the service configuration and deploy, so new tasks get larger volumes.

### Does EBSFilesystemUtilization cover Fargate ephemeral storage?

No. It covers EBS volumes that ECS attaches to tasks. Fargate ephemeral storage has separate Container Insights metrics.

### Why is my snapshot-based volume always at 95%?

Volumes created from a snapshot are often sized to fit the data. If the task does not write to it, high utilisation is expected.

## When this happens away from your desk

Disks fill up gradually, then fail all at once. CloudConsole, a phone app for AWS, is built to show this alarm with its growth trend on a phone so you can tell whether it is urgent.

[About the CloudConsole app](https://cloudconsole.dev/aws-console-app) · [Download on the App Store](https://apps.apple.com/app/cloudconsole-for-aws/id6835419710)

## Sources

- [Recommended alarms for AWS services (Amazon CloudWatch User Guide)](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Best_Practice_Recommended_Alarms_AWS_Services.html)
- [Monitor Amazon ECS using CloudWatch](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/cloudwatch-metrics.html)

## Related

- [CloudWatch alarm: ECS Container Insights TaskEBSfilesystemUtilization](https://cloudconsole.dev/alarms/ecs-insights-taskebsfilesystemutilization)
- [CloudWatch alarm for ECS EphemeralStorageUtilized (Fargate)](https://cloudconsole.dev/alarms/ecs-insights-ephemeralstorageutilized)
- [How to exec into an ECS container](https://cloudconsole.dev/how-to/ecs-exec-into-container)
- [AWS ECS force new deployment](https://cloudconsole.dev/how-to/force-new-deployment-ecs)
- [aws ecs update-service](https://cloudconsole.dev/cli/ecs-update-service)
- [CloudWatch alarm for Amazon ECS CPUReservation](https://cloudconsole.dev/alarms/ecs-cpureservation)

---

Source: https://cloudconsole.dev/alarms/ecs-ebsfilesystemutilization

CloudConsole is an independent iPhone and Android app for Amazon Web Services by Cloudconcur Ltd. It is not affiliated with Amazon Web Services.
