- Newest
- Most votes
- Most comments
Thank you for bringing this to our attention. The situation you're describing is not uncommon and there are a few potential explanations for why you're seeing charges for Directory Services despite not actively using it.
First, it's important to note that AWS implemented some changes related to Directory Services and Amazon WorkDocs in late 2023. If you previously had an Amazon WorkDocs site without active users, AWS may have removed it. As a result, any associated Directory Service directories that were previously free under certain conditions may now be incurring charges.
The charges starting from February 10th, 2025, could be related to this change, although the exact date you mentioned is in the future. It's possible there was a similar policy change closer to that date that affected your account.
To address this issue:
- Check all AWS regions for any active Directory Service resources. Sometimes these can exist in regions you don't typically use.
- Review your detailed billing information in the AWS Billing and Cost Management dashboard. This can help identify the specific Directory Services being charged.
- If you find any directories you're not using, you can delete them to stop the charges. Make sure to follow AWS's proper deletion process to ensure all associated resources are removed.
- If you can't locate the source of the charges, it's recommended to contact AWS Support. They can provide a detailed breakdown of your charges and help identify and remove any resources you're no longer using.
- Check if there are any lingering components like snapshots or backups that might be incurring charges even if the main directory is no longer in use.
As for why this started being charged seemingly randomly, it's likely due to changes in AWS's pricing policies or the expiration of certain free tier benefits. Always keep an eye on AWS communications about service changes and pricing updates to stay informed about potential impacts to your bill.
If you need further assistance, don't hesitate to reach out to AWS Support for a more detailed investigation of your account and charges.
Sources
Why am I being billed for directory services? | AWS re:Post
Directory charges on my account | AWS re:Post
If you are using Cost Explorer, you can figure out in which region you are using Directory Service. Find you deployed Directory Service and then check if there are applications using. If so, you will need to update the applications. For example, if you are using Amazon Connect or even for Identity management, you might have enabled Directory Service. Once confirmed there are no applications with Directory Service, you can delete it.
https://repost.aws/knowledge-center/remove-directory-service
Relevant content
asked a year ago
asked 3 years ago
asked 3 years ago
- AWS OFFICIALUpdated 4 years ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 5 years ago
I don't see how a change implemented in late 2023 would suddenly start affecting the account, now. Furthermore, February 10th, 2025, is NOT in the future. It was two months ago.
As far as the suggestions go, I'm not even sure how to check how something would be connected to this "simple AD," nor do I know how to get a detailed-enough breakdown of this charge in the Billing and Cost Management console.