resource_aws_security_group: DependencyViolation assumes ENI HyperPlane deletion issue

[amitmi704]

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

Description

When destroying a Security Group the provider assumes a DependencyViolation error is related to the HyperPlane ENI issue and retries.

New or Affected Resource(s)

• aws_security_group

Potential Terraform Configuration

• First.tf

resource "aws_security_group" "SG-1" {
	name = Test
	vpc_id = <VPC_ID>
}

• Second.tf

resource "aws_security_group" "SG-2" {
	name = Test
	vpc_id = <VPC_ID>
	ingress {
		protocol = -1
		from_port = 0
		to_port = 0
		security_groups = [ "<SG-1_SG-ID>" ]
	}
}

Process: Apply First.tf followed by Second.tf. Attempt to destroy First.tf and the system will loop assuming the Hyperplane ENI work-around.

References

• Lambda Associated EC2 Subnet and Security Group Deletion Issues and Improvements #10329

[github-actions]

This functionality has been released in v4.29.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.