Overview
Enable lifecycle management for your Amazon EFS file systems so that infrequently accessed data is automatically transitioned to the Infrequent Access (IA) storage class. This plan helps you understand your current EFS landscape, assess which file systems are good candidates for IA, guide you through choosing transition policies, apply those policies, and then validate that everything is configured as intended.
The workflow starts by discovering all relevant EFS file systems and their existing lifecycle configurations. It then analyzes usage and capacity patterns to flag strong and weak IA candidates, presents those findings so you can choose which file systems to modify, and guides you in defining appropriate IA transition ages. Finally, it applies the lifecycle changes and validates that IA policies are correctly configured and aligned with your decisions.
Execution Details
Phase 1: Assessment
Inventory EFS file systems and current lifecycle settings
This phase begins by building a complete inventory of all in-scope EFS file systems across the specified AWS accounts and regions. For each file system, it gathers core attributes such as:
- Identification and configuration details (FileSystemId, region, creation time, lifecycle state, performance and throughput modes, encryption status, and size).
- Tags and metadata (for example, Name, environment, application, owner) to support later decision-making.
- Existing lifecycle configuration, including any lifecycle policies and whether lifecycle management is currently enabled or effectively disabled.
Each file system is classified according to its current lifecycle posture: not configured for IA, configured with a specific IA transition age, or configured but not aligned with target organizational settings. All of this data is stored in a structured format for later phases.
Identify EFS file systems suitable for IA lifecycle transitions
Using the inventory, this step focuses on understanding how each file system is used so you can target IA where it delivers the most value. It:
- Collects recent usage and access characteristics (over a window such as 30–90 days), including approximate read/write throughput, periods of low or no activity, and general read/write patterns.
- Summarizes capacity details such as current logical size and simple growth trends to highlight where IA could provide meaningful cost savings.
- Flags file systems that are poor IA candidates (for instance, those used as scratch or temp storage, or for highly write-intensive or latency-sensitive workloads).
- Highlights strong IA candidates, such as large, mostly read-heavy file systems with low ongoing access and stable or slow growth.
- Incorporates environment and application context from tags (for example, production, development, analytics, transactional).
Each file system receives a preliminary classification: clearly suitable for IA, clearly unsuitable, or requiring user review. These results and supporting metrics are stored to be presented in the next step.
User: Select EFS file systems to enable or adjust IA lifecycle management
You are then guided through choosing which EFS file systems to modify. This step:
- Presents the full inventory along with current lifecycle settings, size, tags, and IA suitability classification.
- Clearly calls out strong IA candidates and file systems that need closer review due to mixed access patterns.
- Lets you decide, for each file system, whether to enable IA lifecycle management for the first time, adjust existing settings, leave them unchanged, or explicitly avoid IA.
- Encourages grouping file systems with similar characteristics (for example, by environment or application) so you can apply consistent lifecycle strategies.
- Captures and documents any file systems that are intentionally excluded from IA, along with the reasons (such as performance or compliance needs).
The outcome is a structured list of target file systems, each marked with the intended action: enable IA, update existing IA settings, or no change.
User: Define IA transition ages for selected EFS file systems
For the file systems you chose to enable or adjust, this step focuses on defining specific lifecycle transition policies. It:
- Presents each selected file system with its usage summary and any existing lifecycle rules.
- Explains the supported IA transition options (for example, transitioning files after 7, 14, 30, 60, or 90 days of no access, or choosing to keep IA disabled).
- Guides you to choose a transition age per file system, taking into account environment and workload (for example, more aggressive transitions for development or test than for production).
- Allows you to confirm situations where IA remains disabled even if technically suitable, and records the rationale.
- Ensures that other lifecycle rules (such as transition back to primary storage) are either preserved or intentionally updated based on your input.
The result is a structured set of lifecycle policy definitions for each selected file system, including IA enablement choices, transition ages, and any constraints or related lifecycle rules, ready to be applied in the configuration phase.
Phase 2: Configuration
Enable IA lifecycle management on selected EFS file systems
This step takes your chosen policies and applies them to file systems that are either newly adopting IA or adding IA to an existing configuration. It:
- Uses the list of targeted file systems and their specified IA transition ages and any related policy requirements.
- Creates new lifecycle configurations for file systems with no existing policies, adding a transition to IA with the chosen age and any additional rules you requested.
- Extends existing lifecycle configurations that currently lack IA, adding a transition-to-IA rule without altering other policies unless explicitly directed to do so.
- Applies each lifecycle configuration to the corresponding file system and then retrieves the resulting configuration to confirm that the IA rule and transition age are correct.
Any file systems where configuration changes fail are identified, with reasons and the resulting state captured. A summary is produced that lists which file systems now have IA enabled, the configured transition ages, and whether the final configuration matches the intended policy.
Adjust IA transition settings on EFS file systems with existing policies
For file systems that already had lifecycle policies but require modifications to IA settings, this step:
- References the list of file systems and their target IA policies defined during assessment.
- Reviews the current lifecycle configuration for each, including existing IA transition rules and any other lifecycle rules.
- Updates or adds the transition-to-IA policy so that the transition age matches your chosen value, ensuring only supported IA age options are used.
- Preserves any non-IA lifecycle rules (such as transition to primary storage) unless you explicitly requested changes, and clearly records any modifications.
- Applies the updated lifecycle configuration and then verifies that the IA rule, transition age, and other intended policies are present and correct.
File systems that could not be updated as requested are documented with error details and their effective configuration. A change summary outlines all file systems whose IA lifecycle settings were altered, including original and new IA transition ages and any other lifecycle adjustments.
Phase 3: Validation
Validate EFS lifecycle management to IA on targeted file systems
The final phase confirms that all targeted EFS file systems are configured correctly and remain healthy. It:
- Consolidates the list of file systems where lifecycle changes were made, including both new and updated IA configurations.
- Retrieves the current lifecycle configuration from EFS for each one.
- Confirms that a transition-to-IA policy exists wherever IA was requested and is absent only where IA was intentionally not enabled.
- Verifies that the configured IA transition ages (for example, 7, 14, 30, 60, or 90 days of no access) match the values you selected.
- Checks that any non-IA lifecycle policies intended to be preserved remain in place and unchanged unless documented otherwise.
- Identifies any discrepancies, such as missing IA rules, incorrect transition ages, or unexpected changes to other policies, and records them for follow-up.
Where practical, basic health checks confirm that file systems remain available and report no lifecycle-related configuration issues. The phase concludes with a validation report summarizing the final lifecycle configuration for each targeted file system, highlighting any items that require additional remediation.