If you were talking to someone whose organization is considering AWS Directory Service, what would you say?
How would you rate it and why? Any other tips or advice?
I would rate this solution 9 out of 10. I have no complaints with the product. It's pretty predefined and user-friendly. AWS is very helpful and very useful for the infrastructure because that's how you can manage your Microsoft Office 365 user accounts with AWS-managed Microsoft Active Directory Services. That is the secure way for users to log in. As a big organization, it is very important to keep the Directory Services in the cloud and manage the Directory Services for the whole infrastructure.
We are an AWS partner. I'd advise new users to take accounting classes. Take cloud accounting and costing classes to help you understand and explain what you mean. That way, when the accounting group from the existing CapEx IT group balks, you can explain the breakdown to them. There's very little training involved, however, you need to get trained in that aspect. I'd rate the solution at a six out of ten, simply based on the cost. It's very expensive. However, I'd give it a nine for ease of use, as it is intuitive.
My advice for anybody who is considering this solution is to first make sure that they want to use other AWS services. If they do not intend to do so, then they can simply use Microsoft Active Directory. This solution does what we want to achieve. I would rate this solution a seven out of ten.
My advice to someone considering this solution is that before working on this it is better to have good theoretical knowledge about this solution, otherwise if something goes wrong it can impact the entire use. The private cloud hypervisor is not so stable so far. They should improve the stability in the next release. I would rate it a nine out of ten.
How do you or your organization use this solution?
Please share with us so that your peers can learn from your experiences.