Not able to access, edit or delete a directory after deleting a subnet it uses

This is a common issue when a directory's critical networking components are removed. When you deleted the subnet that your AWS Directory Service was using, you likely removed the elastic network interface (ENI) that was created during directory creation to establish network connectivity with your VPC.

Unfortunately, when the ENI is deleted, the directory becomes permanently unusable. According to AWS documentation, if the critical elastic network interface that connects your directory to your VPC is deleted, there is no way to resolve this issue. The directory is essentially broken and cannot be recovered.

In this situation, your only option is to:

1. Contact AWS Support to help you delete the now-inaccessible directory. Even with full admin permissions, you might not be able to delete it through normal means since the underlying network components are gone.

2. After the old directory is removed, create a new directory with the proper network configuration.

This is a safety mechanism in AWS Directory Service - the ENIs are critical components that, when removed, render the directory unusable since it can no longer connect to your VPC or any on-premises networks.

If you're unable to delete the directory through the console and continue to receive errors, opening a support case with AWS is your best course of action. If you don't have a support plan that allows technical support cases, you can still submit it as a billing request to avoid being charged for a resource you can no longer use.
Sources
Troubleshooting Simple AD directory status messages - AWS Directory Service
Cannot Delete AWS Directory Service (SimpleAD) | AWS re:Post