aws_mwaa_environment gets destroyed and recreated unnecessarily

[samperetz]

I'm seeing a behavior in aws_mwaa_environment that I was not seeing previously. With hashicorp/aws v4.64.0, every time I deploy, it destroys and recreates the aws_mwaa_environment with this message shown in the terraform apply:

  ~ network_configuration {
      ~ security_group_ids = [
          - "sg-xxxxxxxxx",
        ] -> (known after apply)
      ~ subnet_ids         = [ # forces replacement
          - "subnet-xxxxxxxxx",
          - "subnet-yyyyyyyyy",
        ] -> (known after apply)
    }
}

Even though the subnet_ids are exactly the same every single time, it indicates that they have changed and therefore that is forcing replacement.

Originally these 2 subnet_ids were coming from an aws_subnet data block, with filter that resulted in those 2 exact same subnet_ids every time. Just as a test, I simply hardcoded the 2 subnet_ids in the aws_mwaa_environment resource block:

subnet_ids = ["subnet-xxxxxxxxx", "subnet-yyyyyyyyy"]

But even hardcoded, I get the same behavior.

[dlleu]

+1 on this issue. Even without any changes at all, whenever I run plan, TF wants to recreate the environment.

[dlleu]

Later update on this matter: This is not an issue of this module, I moved to "vanilla" terraform in my project and the same happens. So, I can only conclude that the issue is in the official terraform aws provider.

[TiansuYu]

I am also seeing the same issue. Though the change I applied is only about tagging.