aws_dlm_lifecycle_policy does not have an option to exclude root volume snapshots

[nazeemmohammed]

While creating dlm policies using AWS UI, there is an option to exclude root volumes from snapshot. There doesn't seem to be similar option available while creating using terraform aws_dlm_lifecycle_policy module.

[justinretzolk]

Hey @nazeemmohammed 👋 Thank you for taking the time to raise this! So that we have all of the necessary information in order to look into this, can you update the issue description to include the information requested in the feature request template?

[nazeemmohammed]

Hi @justinretzolk below is my

variable "tags" {
    default = ["instance1", "instance2", "instance3"]
}
resource "aws_dlm_lifecycle_policy" "DLMCredcas_prd" {
    for_each = toset(var.tags)
    description = "DLM_${each.value}"
    execution_role_arn = "arn:aws:iam::xxxx:role/service-role/AWSDataLifecycleManagerDefaultRole"
    policy_details {
      resource_types = ["INSTANCE"]
      schedule {
        name = "${each.value}-snapshot-12hours"
        create_rule {
          interval      = 12
          interval_unit = "HOURS"
          times         = ["23:00"]
        }         
      retain_rule { count = 28 }
      copy_tags = false
    }
    target_tags = {
      Name = "${each.value}"
    }
   }
}

AWS provides below option to exclude root volumes which I do not find in terraform documentation.

Parameters:
ExcludeBootVolume: True

Also as per terraform documentation resource_types only allows VOLUME type which is not correct - https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/dlm_lifecycle_policy#resource_types

[github-actions]

This functionality has been released in v4.9.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. Thank you!

[github-actions]

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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.