Terraform-provider-aws: EFS with infrequent access life cycle

Created on 20 Feb 2019  ·  13Comments  ·  Source: hashicorp/terraform-provider-aws

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description


EFS now allows for setting life cycle / IA configuration for saving costs on infrequently accessed data. This seems to be for new EFS filesystems only though.

Please have terraform efs resource to leverage and enable this configuration
https://aws.amazon.com/about-aws/whats-new/2019/02/amazon-efs-introduces-lower-cost-storage-class/

New or Affected Resource(s)

  • aws_efs_*

Potential Terraform Configuration

# Copy-paste your Terraform configurations here - for large Terraform configs,
# please use a service like Dropbox and share a link to the ZIP file. For
# security, you can also encrypt the files using our GPG public key.

References

  • 0000

  • enhancement good first issue servicefs

    Most helpful comment

    All 13 comments

    It appears this should be implemented via a new lifecycle_policy configuration block in aws_efs_file_system, e.g.

    # Potential Terraform configuration, details may change during development
    resource "aws_efs_file_system" "example" {
      # ... other configuration ...
      lifecycle_policy {
        transition_to_ia = "AFTER_30_DAYS"
      }
    }
    

    +1

    this would be an AWS specific question I guess. In the event that terraform resource is updated with the new lifecycle policy change, can I make changes to an existing EFS filesystem using this change in the resource block?

    hi @bflad just checking for your suggestions on this

    can I make changes to an existing EFS filesystem using this change in the resource block?

    ~According to the docs, only if you created your file system after 13th Feb this year.~

    EDIT: As of 9th July, the above is no longer the case:

    Additionally, you can now enable Lifecycle Management for all EFS file systems.

    @bflad anybody working this issue to your knowledge? Was thinking of knocking it out.

    ^ And the above announcement also releases IA to _existing_ file systems created before the previous 13th Feb cutoff. 🎉

    @ewbankkit do you think it would be best to include the SDK version bump and new lifecycles as part of my PR (#9250)?

    @ryno75 Yes it looks like you should git rebase onto the upstream master to address some of the changes that @bflad suggested.

    Support for a new lifecycle_policy configuration block has been merged and will release with version 2.23.0 of the Terraform AWS Provider, in the next day or two. Thanks to @ryno75 for the implementation. 👍

    This has been released in version 2.23.0 of the Terraform AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

    For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template for triage. Thanks!

    I'm going to lock this issue because it has been closed for _30 days_ ⏳. This helps our maintainers find and focus on the active issues.

    If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!

    Was this page helpful?
    0 / 5 - 0 ratings