aws_efs_file_system: Create additional resource for lifecycle policy: aws_efs_file_system_lifecycle_policy

[jornfranke]

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 other comments that do not add relevant new information or questions, 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

Currently, one can create a EFS filesystem using efs_file_system and attach in the same resource a lifecycle policy. However, in certain cases, such as an aws_sagemaker_domain the EFS is not directly created by TF. In order to avoid manual imports etc., I suggest to create a resource aws_efs_file_system_lifecycle_policy to update the lifecycle policy also for those cases with the same cotnent as lifecycle policy.

New or Affected Resource(s)

• aws_efs_file_system_lifecycle_policy

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.

resource "aws_efs_file_system" "foo" {
  creation_token = "my-product"

  tags = {
    Name = "MyProduct"
  }
}

  resource "aws_efs_file_system_lifecycle_policy" "example" {
    efs_file_system_id = aws_efs_file_system.foo.id
    transition_to_ia = "AFTER_30_DAYS"
    transition_to_primary_storage_class = "AFTER_1_ACCESS"
  }

More complex example with a AWS Sagemaker Domain

  resource "aws_efs_file_system_lifecycle_policy" "example" {
    efs_file_system_id = aws_sagemaker_domain.example.home_efs_file_system_id
    transition_to_ia = "AFTER_30_DAYS"
    transition_to_primary_storage_class = "AFTER_1_ACCESS"
  }

resource "aws_sagemaker_domain" "example" {
  domain_name = "example"
  auth_mode   = "IAM"
  vpc_id      = aws_vpc.test.id
  subnet_ids  = [aws_subnet.test.id]

  default_user_settings {
    execution_role = aws_iam_role.test.arn
  }
}

resource "aws_iam_role" "example" {
  name               = "example"
  path               = "/"
  assume_role_policy = data.aws_iam_policy_document.example.json
}

data "aws_iam_policy_document" "example" {
  statement {
    actions = ["sts:AssumeRole"]

    principals {
      type        = "Service"
      identifiers = ["sagemaker.amazonaws.com"]
    }
  }
}

References

• #0000

[jornfranke]

See also: https://docs.aws.amazon.com/efs/latest/ug/API_PutLifecycleConfiguration.html

[fabriciocarboni]

following up.

[Alexj12]

This would be helpful, as I believe it would allow a lifecycle policy on EFS systems created by efs_replication_configuration.