Terraform update SGR duplicate

Terraform Providers AWS
1

In the process of updating a SGR it creates a new SGR causing a duplicate with the old SGR since it hasn’t delete it yet.
So the SGR would need to remain the same name or the SGR would need to delete old before creating new:

  # module.eks.aws_security_group_rule.cluster["limit_internet_443_access"] must be replaced
+/- resource "aws_security_group_rule" "cluster" {
      ~ cidr_blocks              = [ # forces replacement
            "10.200.0.0/17",
          + "10.224.40.215/32",
        ]
      ~ id                       = "sgrule-3308378098" -> (known after apply)
      ~ security_group_rule_id   = "sgr-0f04a9bd223b52511" -> (known after apply)
      + source_security_group_id = (known after apply)
        # (7 unchanged attributes hidden)
    }

error:

╷
│ Error: [WARN] A duplicate Security Group rule was found on (sg-0e6a02f2a45f7f541). This may be
│ a side effect of a now-fixed Terraform issue causing two security groups with
│ identical attributes but different source_security_group_ids to overwrite each
│ other in the state. See https://github.com/hashicorp/terraform/pull/2376 for more
│ information and instructions for recovery. Error: InvalidPermission.Duplicate: the specified rule "peer: 10.200.0.0/17, TCP, from port: 443, to port: 443, ALLOW" already exists
│ 	status code: 400, request id: 818ca30f-3e1e-4fd1-ae24-3aba738b548e
│
│   with module.eks.aws_security_group_rule.cluster["limit_internet_443_access"],
│   on .terraform/modules/eks/main.tf line 192, in resource "aws_security_group_rule" "cluster":
│  192: resource "aws_security_group_rule" "cluster" {
│
╵