- Newest
- Most votes
- Most comments
It appears you've encountered a common and frustrating issue with deleting AWS Directory Service resources, particularly SimpleAD directories. Despite your thorough efforts to remove all dependencies and authorized applications, the directory remains undeletable.
This situation often occurs due to lingering associations or internal references that are not easily visible or accessible through the standard AWS console or CLI commands. In some cases, there may be hidden or orphaned resources still linked to the directory, preventing its deletion.
Unfortunately, in many such scenarios, the resolution typically requires intervention from AWS Support. They have access to internal tools and processes that can manually remove these stubborn associations and force the deletion of the directory.
Since you've already taken extensive steps to remove all visible dependencies, your best course of action at this point would be to contact AWS Support. If you don't have a support plan that allows you to open a technical support case, you can still submit a billing support request. Explain that you're unable to delete the directory and that you don't want to be charged for a resource you can't remove.
When contacting support, provide them with all the details of the steps you've already taken. This will help them understand the situation more quickly and potentially expedite the resolution process.
In some cases, support may need to escalate the issue to the Directory Service team to manually remove any remaining authorized applications or hidden dependencies. Once they've done this, you should be able to delete the directory.
For future reference, it's worth noting that this is a known issue that has affected other AWS users as well. While AWS has safety precautions in place to prevent accidental deletion of resources that are still in use, sometimes these precautions can be overly restrictive and cause difficulties like the one you're experiencing.
In the meantime, continue to monitor your account for any unexpected charges related to this directory. If charges do occur while you're waiting for support to resolve the issue, make sure to include this information in your support request, as AWS may be able to provide credits for charges incurred due to this inability to delete the resource.
Sources
I cannot disable my Directory Service | AWS re:Post
Directory Service Deletion Issues | AWS re:Post
Cannot delete AD connector | AWS re:Post
Cannot delete AD connector | AWS re:Post
Relevant content
asked 6 years ago
asked a year ago
- AWS OFFICIALUpdated 5 years ago
- AWS OFFICIALUpdated 2 years ago
