I have a question regarding shared resources in our AWS instances. We are running multiple clusters at the same time as we are running the tests synchronously. For each test, we create a cluster with a separate environment name, i.e. “run-1”, “run-2", etc. After the run completes, the cluster is deleted automatically. Sometimes the deletion of the cluster fails, because it tries to delete a resource that is still in use. This strikes me as odd, because I would assume that all resources are specific to that environment, and as such it should not have an issue deleting the resources. Could it be that there are still “shared” resources that are created in the AWS account without taking account the specific environment name? Or is this a different issue and is it just an error in the termination script with regard to the order of deletion?

Could not delete subnet subnet-0ba60ad90daf63be2, An error occurred (DependencyViolation) when calling the DeleteSubnet operation: The subnet 'subnet-0ba60ad90daf63be2' has dependencies and cannot be deleted.