AWS Managed Active Directory - Disk error and restart capability

0

Problem

We are getting the following error message in our Directory Service

The server disk could be full or corrupted or the maximum permissible size for the server registry has been reached

The DNS server could not open a registry key. Reinstall the DNS server if it was not able to be started. If the DNS server started, but couldn't load a zone, reload the zone or restart the DNS server.

We followed the suggestions in this doc [ms_ad_troubleshooting_low_storage_spac] but found that our disk is not full.

Currently, storage configuration is not supported.

Questions

  • The error message suggests we restart the server, but this function seems to be out of our hands. Is there a way to do this in AWS managed AD?
  • Has a similar problem been brought up and was there a solution?
asked 3 years ago171 views
1 Answer
0

In AWS Managed Active Directory (AD), you do not have direct access to the underlying servers to restart them or perform low-level configurations directly. However, there are still several steps you can take to address the issue based on the information provided and the limitations of AWS Managed AD:

Check Directory Health: Use the AWS Management Console to check the health status of your Managed AD. Navigate to the AWS Directory Service console, select your directory, and review any health or status messages. AWS may provide insights or automated troubleshooting steps directly in the console.

Review AWS CloudWatch Logs: Ensure that CloudWatch logging is enabled for your AWS Managed AD. Review the logs for any additional error messages or warnings that can give more context to the issue. These logs can also be shared with AWS support to expedite troubleshooting.

Perform a Directory Snapshot and Restore: If you suspect corruption or other issues that cannot be immediately resolved, you might consider creating a snapshot of your directory and restoring it. This can be done through the AWS Management Console:

Create a Snapshot: Go to the AWS Directory Service console, select your directory, and create a manual snapshot. Restore from Snapshot: If needed, you can restore the directory from a previous snapshot. Verify DNS Configuration: Ensure that your DNS settings within AWS are correctly configured. Misconfigurations can sometimes lead to the DNS server being unable to access certain registry keys.

Regular Maintenance and Monitoring: Regularly monitor the storage and health of your managed directory services to preemptively address issues before they escalate.

profile picture
EXPERT
answered a year ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions