ecs_task_definition volume root_directory does not take effect

[jonb-ifit]

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

Terraform CLI and Terraform AWS Provider Version

terraform 1.2.9

Affected Resource(s)

• aws_ecs_task_definition

Terraform Configuration Files

      efs_volume_configuration {
        file_system_id     = var.file_system_id
        root_directory     = "/cache"
        transit_encryption = "ENABLED"
        authorization_config {
          iam = "ENABLED"
        }
      }

Debug Output

The plan output generated this as expected:

      - volume { # forces replacement
          - name = "cache" -> null

          - efs_volume_configuration {
              - file_system_id          = "fs-0ae3f67bc10ac8ed6" -> null
              - root_directory          = "/" -> null
              - transit_encryption      = "ENABLED" -> null
              - transit_encryption_port = 0 -> null

              - authorization_config {
                  - iam = "ENABLED" -> null
                }
            }
        }
      + volume { # forces replacement
          + name = "cache"

          + efs_volume_configuration {
              + file_system_id     = "fs-0ae3f67bc10ac8ed6"
              + root_directory     = "/cache"
              + transit_encryption = "ENABLED"

              + authorization_config {
                  + iam = "ENABLED"
                }
            }
        }

Expected Behavior

New task definition revision should have the correct root directory

Actual Behavior

The new task definition revision was created, but still says that the root directory is /

This means the next apply to also create a new revision with the same issue.

Steps to Reproduce

1. create an aws_ecs_task_definition resource with a volume block with an efs_volume_configuration with a root directory other than /
2. Run terraform apply and observe the plan output. The plan shows that root_directory is being set
3. Look at the new task definition revision in the AWS console. The volume root directory is set to /

[odie5533]

This issue is mentioned in #19549 (and the closed ticket #18010). Does make it impossible to mount two directories to a Docker container using the same aws_efs_access_point. Also it silently ignores your configuration, which is not good. Ended up clobbering my deployment files.

[a087674]

This issue is mentioned in #19549 (and the closed ticket #18010). Does make it impossible to mount two directories to a Docker container using the same aws_efs_access_point. Also it silently ignores your configuration, which is not good. Ended up clobbering my deployment files.

@odie5533 - You actually cannot mount multiple directories using access points as the access point itself is tied to a specific directory. See documentation. However multiple directories via a Mount Point are possible.

[github-actions]

This functionality has been released in v5.3.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.