Closed chroju closed 2 years ago
Unfortunately, this works with aws provider v4, but seems to cause an error with v3. It was my environmental issue.
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.
Description
Please provide a clear and concise description of the issue you are encountering, and a reproduction of your configuration (see the
examples/*
directory for references that you can copy+paste and tailor to match your configs if you are unable to copy your exact configuration). The reproduction MUST be executable by runningterraform init && terraform apply
without any further changes.If your request is for a new feature, please use the
Feature request
template.⚠️ Note
Before you submit an issue, please perform the following first:
.terraform
directory (! ONLY if state is stored remotely, which hopefully you are following that best practice!):rm -rf .terraform/
terraform init
Versions
Module version [Required]: v3.23.1
Terraform version: v1.3.3
Provider version(s): v4.34.0
Reproduction Code [Required]
Steps to reproduce the behavior:
This is example, not actually code. The key point is that EFS is used instead of Fargate ephemeral storage.
Expected behavior
Works fine.
Actual behavior
This error.
Terminal Output Screenshot(s)
Additional context
This is probably the same issue reported for the
terraform-aws-security-group
module.