We block the deletion of the AD Connector when there are still applications linked to it as a safety precaution to prevent customers from unintentionally breaking an AWS application that is still using the directory. However, that can sometimes be more frustrating than helpful. This post is a good example. The error about "the role’s trust with AWS Directory Service no longer exists" means that the AD Connector is Inoperable because it no longer has access to your domain controllers. So you have to update your network settings to reestablish connectivity between the AD Connector and your domain in order to delete those roles. As you have pointed out, this is a lot of work just to delete something. Therefore, I have manually unauthorized the AWS Management Console from your AD connector. This will allow you to delete the AD Connector with out any additional work.
Thank you, that worked well. The domain this was connected to is no longer accessible so it would have been impossible to delete otherwise!
How do I go about requesting a manual fix to this problem?
AD Connector MFA Setup Completed but AD Connector not sending RADIUSasked 2 years ago
¿Is it posible to change a workdocs connection to an AD Connector?asked a year ago
AD Connector-Unable to connect to the On-Premises Active Directoryasked 3 months ago
Cannot delete AD connectorasked 2 months ago
AD Connector inoperable state - Unable to deleteasked 10 months ago
AD Connector DNS not in ADasked 2 years ago
Cannot delete AD connectorasked 3 years ago
I am not able to delete AD connector and need assistanceasked a month ago
WorkSpaces - Inoperable AD Connectorasked 4 months ago
Unable to delete Directory Service AD Connectorasked 7 months ago