Summary

Recently, Amazon announced a new storage class for Amazon EFS, known as the Amazon EFS Archive Storage Class. This update can be found in their recent post: Amazon EFS Archive Storage Class Announcement.

The current Ansible community.aws.efs module does not yet support some of the latest features introduced by Amazon for EFS, particularly the "elastic" mode and the new storage class transitions. This limitation hinders the ability to fully manage EFS configurations via Ansible, especially for use cases requiring these new features.

To address this, I have initiated a pull request (PR #2026) which is an updated version of the original PR (PR #1960). This PR aims to introduce support for the "elastic" mode in the EFS module.

However, to fully leverage the new capabilities of Amazon EFS, we should also consider implementing additional functionalities:

1. Transition to Archive Storage Class: Introduce a new configuration parameter, transition_to_archive, allowing users to automate the transition of EFS files to the Archive Storage Class.

2. Transition Back to Standard Storage Class: Similarly, a transition_to_standard parameter should be added to enable the reverse transition, moving files from the Archive Storage Class back to the Standard Storage Class.

3. Enhanced Lifecycle Management: These new parameters would complement the existing transition_to_ia parameter, providing a comprehensive set of options for managing the lifecycle of EFS files in accordance with storage requirements and cost optimization strategies.

By implementing these features, the Ansible community.aws.efs module would offer more robust and up-to-date capabilities for managing Amazon EFS resources, aligning with the latest AWS offerings and ensuring that users can fully automate their EFS configurations through Ansible.

I look forward to feedback and contributions from the community to bring these enhancements to fruition, and, I am also willing to contribute to the implementation of these features.

Issue Type

Feature Idea

Component Name

efs

Additional Information

No response

Code of Conduct

• I agree to follow the Ansible Code of Conduct