---
title: "DELETE /2015-02-01/file-systems/{FileSystemId}"
method: DELETE
path: "/2015-02-01/file-systems/{FileSystemId}"
---

# DELETE /2015-02-01/file-systems/{FileSystemId}

`DELETE /2015-02-01/file-systems/{FileSystemId}`

Deletes a file system, permanently severing access to its contents. Upon return, the file system no longer exists and you can't access any contents of the deleted file system.

You need to manually delete mount targets attached to a file system before you can delete an EFS file system. This step is performed for you when you use the Amazon Web Services console to delete a file system.

You cannot delete a file system that is part of an EFS Replication configuration. You need to delete the replication configuration first.

You can't delete a file system that is in use. That is, if the file system has any mount targets, you must first delete them. For more information, see DescribeMountTargets and DeleteMountTarget.

The `DeleteFileSystem` call returns while the file system state is still `deleting`. You can check the file system deletion status by calling the DescribeFileSystems operation, which returns a list of file systems in your account. If you pass file system ID or creation token for the deleted file system, the DescribeFileSystems returns a `404 FileSystemNotFound` error.

This operation requires permissions for the `elasticfilesystem:DeleteFileSystem` action.

## Path parameters

- `FileSystemId` string, required

## Response `204`

Success

## Other responses

- `480` — BadRequest
- `481` — InternalServerError
- `482` — FileSystemNotFound
- `483` — FileSystemInUse

---

[API](https://skmtc.net/aws/apis/elasticfilesystem.md) · [All operations](https://skmtc.net/aws/apis/elasticfilesystem/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/aws/elasticfilesystem/revisions/bd410c1b597a/schema)