EFS file system missing lifecycle policy

An EFS file system with no lifecycle policy to transition infrequently accessed data to Infrequent Access.

Last updated July 7, 2026

This finding is distinct from the other EFS findings Parsivex surfaces:

  • Idle EFS file system — the file system has no or near-zero read/write throughput over the lookback window, suggesting no active workloads are using it.
  • Missing lifecycle policy (this page) — the file system has no TransitionToIA lifecycle policy, so all data stays in Standard storage even when infrequently accessed. Savings estimates assume a conservative share of data could move to Standard-IA once lifecycle management is enabled.

What triggers this finding

An EFS file system with no lifecycle management policy to transition infrequently accessed files to Infrequent Access.

Typical fix

Enable EFS lifecycle management to transition files to IA after a set number of days without access.

Example savings

Up to ~92% savings on cold data — e.g. $5–$50+/month on file systems with large infrequently accessed datasets.

See also: Severity and savings estimates for how Parsivex calculates figures on your report.

Related articles