ISSUE - Adding EBS Volume forces EC2 Replacement

[cfsb-jrose]

Description

Re-raising #401 as it is still an issue.

If your request is for a new feature, please use the Feature request template.

• ✋ I have searched the open/closed issues and my issue is not listed.

⚠️ Note

Before you submit an issue, please perform the following first:

1. Remove the local .terraform directory (! ONLY if state is stored remotely, which hopefully you are following that best practice!): rm -rf .terraform/
2. Re-initialize the project root to pull down modules: terraform init
3. Re-attempt your terraform plan or apply and check if the issue still persists

Versions

• Module version [Required]: v5.8.0

• Terraform version:

  Terraform v1.11.4
  on linux_amd64
  

• Provider version(s):

  Terraform v1.11.4
  on linux_amd64
  + provider registry.terraform.io/hashicorp/aws v5.97.0
  

Reproduction Code [Required]

Steps to reproduce the behavior: refer to #401

Expected behavior

refer to #401

Actual behavior

refer to #401

Terminal Output Screenshot(s)

refer to #401

Additional context

While the workaround noted in #401 does mitigate the risk of replacing EC2 instances, it doesn't solve the issue from a CloudOps/DevOps perspective. A better solution would be to create a sub-module to handle EBS volumes and attachments.

[bryantbiggs]

upstream issue hashicorp/terraform-provider-aws#21806