Hi @gb-ckedzierski
I don't think this is a problem with this module, it's common error with terraform 0.11:
hashicorp/terraform#17928
hashicorp/terraform#16824

I think there are 2 ways around it:

1. Instead of removing the module definition, you can run terraform destroy -target=module.eks`
2. Just run terraform state rm module.eks.data.http.workstation_external_ip

I usually do option 2.

Thanks for your help! This worked deleting those items from the state directly.

Note to future me, these are the things that needed to be deleted

terraform state rm module.eks.null_resource.tags_as_list_of_maps
terraform state rm module.eks.data.template_file.kubeconfig
terraform state rm module.eks.data.http.workstation_external_ip
terraform state rm module.eks.data.template_file.config_map_aws_auth
terraform state rm module.eks.data.template_file.userdata

I wonder if the workaround is to pass modules like recommend in the link issues? I'll test and create a PR if I find anything that could work here. Thanks again for the help!

I had to do this just now. Is this really closed?

@pessoa Yes and no, new issue is opened up here with the real fix to the issue.

I am unable to delete the EKS cluster provsioned with this module.
Here is how I provisioned the EKS cluster.

https://github.com/terraform-aws-modules/terraform-aws-eks/blob/master/examples/eks_test_fixture/main.tf

terraform destroy fails
terraform destroy -target=module.eks also fails.

It fails to delete the security group after 10 minutes.
module.eks.aws_security_group.workers: Still destroying... (ID: sg-0f2da422658faa936, 10s elapsed)
Error: Error applying plan:

1 error(s) occurred:

• module.eks.aws_security_group.workers (destroy): 1 error(s) occurred:

• aws_security_group.workers: DependencyViolation: resource sg-0f2da422658faa936 has a dependent object
  status code: 400, request id: 5fab7838-61cf-4b1d-8b57-e1cf3360c58a

Terraform does not automatically rollback in the face of errors.
Instead, your Terraform state file has been partially updated with
any resources that successfully completed. Please address the error
above and apply again to incrementally change your infrastructure.

Let me know if anybody has any suggestions for successfully deleting the cluster.

@rajpolaris

If you created any ELBs from k8s, referenced any security groups in other SG rules, enabled scale in protection (or many more things), then this will prevent terraform destroy.

Just do to the AWS console and try to delete the SG sg-0f2da422658faa936 manually and see what the error is.

@rajpolaris add delete_on_termination = true in the network_interfaces part of the aws_launch_template as mentioned here: hashicorp/terraform-provider-aws#1671 (comment). That worked for me.

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.