Try our new research platform with insights from 80,000+ expert users

AWS Directory Service vs Okta Workforce Identity comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Dec 2, 2024

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

AWS Directory Service
Ranking in Identity and Access Management as a Service (IDaaS) (IAMaaS)
16th
Average Rating
8.6
Reviews Sentiment
7.3
Number of Reviews
15
Ranking in other categories
No ranking in other categories
Okta Workforce Identity
Ranking in Identity and Access Management as a Service (IDaaS) (IAMaaS)
3rd
Average Rating
8.6
Reviews Sentiment
7.0
Number of Reviews
68
Ranking in other categories
Single Sign-On (SSO) (2nd), Authentication Systems (6th), Privileged Access Management (PAM) (6th), Access Management (4th), ZTNA as a Service (10th)
 

Mindshare comparison

As of August 2025, in the Identity and Access Management as a Service (IDaaS) (IAMaaS) category, the mindshare of AWS Directory Service is 1.6%, down from 2.0% compared to the previous year. The mindshare of Okta Workforce Identity is 11.5%, down from 15.0% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Identity and Access Management as a Service (IDaaS) (IAMaaS)
 

Featured Reviews

Basa Saiteja - PeerSpot reviewer
A valuable access management system with a user-friendly and straightforward setup
The solution is scalable, and we can scale according to our needs. I rate the scalability a nine out of ten. In our organization, our access to our AWS comes from IAM. We use AWS consoles using our credentials and don't have route access, so each person will log in through our IAM programmatic access, and everyone on our team can work on cloud. Over 10,000 people in our organization utilize the solution.
Tor Nordhagen - PeerSpot reviewer
Extremely easy to work with, simple to set up, and reasonably priced
The drawback of this solution is that in our shops, many staff members sometimes have to be borrowed from one shop to another and the solution does not really support having multiple roles. The user experience we would like to have when a person works in shop A which pays their salary is that they should have access to pretty much everything. Maybe you have somebody who is a manager in that shop A, he should be able to order new wear, he should be able to change the pricing, he should be able to empty the cash registry, and ship it to the bank. But when for instance, in COVID, people had to fill in for people in shops where a lot of people were sick, then they had to actually use user accounts of people that work in shop B. If you were employed in shop A, you could not work in shop B without borrowing somebody else's user ID and password. Which is really bad. We haven't been able to work around that and Okta Workforce Identity does not have a solution for it. We are now piloting their identity governance solution. Obviously, it's easy to give somebody access, give them an account, and give them roles, but it's hard to maintain that. For example, if you moved from, say working in a shop to working in a warehouse. But why do you still have all this shop access? The solution has until now not had anything to really support the process of taking away access. But now we are in a better release program of Okta's identity governance solution. Although it's very basic, the solution has started on a journey, but identity governance is something that Okta Workforce Identity really needs to improve. The ability or the options in the solution for changing the look and feel are not good enough because in our partner portal, essentially what they have is an ugly admin interface. The admin interface is good enough for us technical people because that's all we need. We work with the product and we're able to see the data but when it comes to presenting the service portal, Okta Workforce Identity does not have any capabilities really for making it look pretty. To add branding and different graphical user interface elements than Okta basic for essentially delegated admin for the business-to-business portal is horrifying because you're essentially using the tech admin. The only option we had and used, was to take the tech admin console and strip it. so that a vendor that has some goods that are sold in the shops, when they want to add a user on their side, say a driver or a packer on their side who should know how much they've packed in a truck to come to our warehouse, then the user interface that this vendor is using, these functional people will then have to use an extremely basic user interface.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"The solution integrates well with other tools, particularly through single sign-on, allowing users to connect to various applications using just one password, including email."
"The pricing is very good because it is low and there is no management cost."
"I would rate AWS Directory Service nine out of ten."
"AWS handles everything on the backend requiring minimal legwork from our team. We only require a dedicated database administrator while depending on Amazon for RDS."
"AWS Directory Service is secure."
"The most valuable feature is ease of use."
"I like the manageability. Activate Connect makes it easier to assign information and to manage the resources in the network."
"The AD Connector is very good and easy to implement."
"Valuable features include UD, SSO functionality, MFA and Adaptive MFA functionality, ability to link multiple Directory databases with UD."
"The most valuable aspects of the solution are the integration with external websites one-factor authentication."
"It is flexible and easy to install."
"It is a very scalable solution."
"The solution can scale very well."
"First of all, the solution is very simple."
"The most valuable features are ease of operation and visibility."
"Workforce Identity's best features include its user-friendliness and easy setup."
 

Cons

"AWS could improve the number of regions. Azure has passed them. The ned more consistency, as far as the Northeast is concerned."
"AWS Directory Service needs to improve processing."
"Some of the security protocols are difficult to understand."
"To get CloudWatch to monitor your memory and storage, you have to do some configuration within your server, which sometimes results in errors."
"The AWS Directory Service should be easier to integrate."
"The group policy can be improved."
"Currently, there is no option to integrate our on-premises Cisco AWS Directory Service, requiring some manual configuration."
"Accessing the data needs improvement."
"The only aspect in which it can be improved is that the interface could be cleaner. I found this even when I was trying to do my certification exam because the certification is hands-on. You find yourself fumbling around a little bit to find simple things. This happens even when you start to get familiar with the product."
"The solution lacks an on-premises deployment model so it can't offer a hybrid solution. It would be ideal if clients had options that weren't just cloud-based."
"There is no proper documentation on integrating test cases with Okta, and this issue is troubling whenever I try to implement it."
"There should be automated aggregation and complete classification processes included in it."
"It's not compatible with on-premises installations, unless you host it as a SaaS. We were not able to do that. For example, imagine a scenario where the cloud is not available. Then, Okta will not work for you. That use case will readily fail because it doesn't have an on-premises installation that you can use to authenticate or provide identity and access management. If you have a purely on-premises solution that is not connected to the internet, then this will not work. This is one area that can be improved."
"The product is expensive compared to other tools."
"The high cost of the product is an area of concern where improvements are required."
"Okta should have at least a local peering partner for countries that align with or comply with GDPR, so there are no compliance or audit questions."
 

Pricing and Cost Advice

"We pay an annual subscription fee."
"The pricing is reasonable."
"The pricing depends because with AWS there are two types of directory objects: 30,000 and 500,000. It varies. AWS provides the pricing calculators so we can get an estimate from there as per the company requirement of how many users and objects that we need to create. So we can go to that portal, put in the data, and get the quotation. There are no extra licensing fees. It's all included."
"AWS' pricing is fair, and costs can be cut if you look carefully at when you're using it."
"License is around US$20,000 annually."
"It has a yearly subscription. As compared to its competitors, it is quite expensive. It also has a complex licensing model."
"Though I don't know about the licensing model of the product, I wouldn't be surprised if Okta offers a per user license subscription model."
"The solution is not the cheapest but not the most expensive. They are in the middle rating."
"The price of Okta Workforce Identity is reasonable."
"This solution is costly. Pricing is decent if you have less users, but it significantly goes up the more users you have, with its cost not justified."
"The solution's pricing model could be better for SMBs."
"This is an expensive solution but the security makes it worthwhile."
report
Use our free recommendation engine to learn which Identity and Access Management as a Service (IDaaS) (IAMaaS) solutions are best for your needs.
865,295 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
16%
Performing Arts
9%
Healthcare Company
9%
Manufacturing Company
8%
Computer Software Company
13%
Manufacturing Company
10%
Financial Services Firm
9%
Government
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What do you like most about AWS Directory Service?
The most valuable feature of AWS Directory Service is cost-cutting features.
What is your experience regarding pricing and costs for AWS Directory Service?
The pricing is very good because it is low and there is no management cost. You do not need to hire any system administrator to manage your Active Directory.
What needs improvement with AWS Directory Service?
Accessing the data needs improvement. Additionally, integration and compatibility with other AWS ( /products/amazon-aws-reviews ) services, network open LDAP, support for on-premise and cloud envir...
What do you like most about Okta Workforce Identity?
Okta has introduced the Universal Directory. It has custom attribute capability and user permissions to read/write on their profiles or hide them. Profile sources and identity profile sourcing are ...
What is your experience regarding pricing and costs for Okta Workforce Identity?
Pricing for Okta is reasonably not that much, however, I don't have access to the commercial aspect.
What needs improvement with Okta Workforce Identity?
Areas for improvement with Okta Workforce Identity would be in the governance place; for me, it is light. Okta is mostly focused on execution and runtime, which means maintaining authentication and...
 

Also Known As

AWS Managed Microsoft AD
No data available
 

Overview

 

Sample Customers

Expedia, Intuit, Royal Dutch Shell, Brooks Brothers
FedEx, Zoom, Takeda, Lululemon Athletica, GrunHub, jetBlue, McKensson, Bain & Company, Engie, Peloton, Sonos, T-Mobile, Hewlett Packard, MGM Resorts, Ally Financial, Priceline, Albertsons, Itercom, Classy, FICO, Kensho, Live Nation, Drata, Rotary, and others.
Find out what your peers are saying about AWS Directory Service vs. Okta Workforce Identity and other solutions. Updated: July 2025.
865,295 professionals have used our research since 2012.