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)
14th
Average Rating
8.6
Reviews Sentiment
7.4
Number of Reviews
14
Ranking in other categories
No ranking in other categories
Okta Workforce Identity
Ranking in Identity and Access Management as a Service (IDaaS) (IAMaaS)
2nd
Average Rating
8.6
Reviews Sentiment
7.2
Number of Reviews
65
Ranking in other categories
Single Sign-On (SSO) (4th), Authentication Systems (6th), Privileged Access Management (PAM) (7th), Access Management (3rd), ZTNA as a Service (8th)
 

Mindshare comparison

As of February 2025, in the Identity and Access Management as a Service (IDaaS) (IAMaaS) category, the mindshare of AWS Directory Service is 2.0%, down from 2.5% compared to the previous year. The mindshare of Okta Workforce Identity is 13.5%, up from 13.5% 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

"We can provide specific access to people based on what they need from our accounts."
"AWS has eliminated the downtime we waste when our on-premises resources go down."
"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 AD Connector is very good and easy to implement."
"The most valuable feature of AWS Directory Service is cost-cutting features."
"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."
"We like the fact that it's got such great redundancy."
"The MFA part is the best. MFA provided most of the security that we were looking at with respect to the second level of authentication. Okta Workforce Identity provides a number of options with respect to multifactor authentication, such as the app, phone call, and text. These options provide different ways of logging in for users, and they were a lot more than what we needed. This is certainly a very good feature of Okta Workforce Identity."
"You can only log in if you have the access, which protects the applications by avoiding cross-site scripting."
"One of the most beneficial features of the solution is the user provisioning and the de-provisioning feature."
"Okta controls all the users. It has context-based access from the user and type of device. It identifies the risk and can do a step of authentication when that user is trying to access some sensitive application from an unknown device."
"A solution that's easy to use, stable, and reliable."
"What I found most valuable in Okta Workforce Identity is that it worked together with VMware Workspace One, so there was this device check at the same time. My company used the trusted device method that enabled you to define that only the trusted devices including the Workspace One agent were able to access the applications directly without an additional authentication step."
"The most valuable features are ease of operation and visibility."
"It's reliable and it does what it is advertised to do."
 

Cons

"To get CloudWatch to monitor your memory and storage, you have to do some configuration within your server, which sometimes results in errors."
"The solution lacks certain features."
"Currently, there is no option to integrate our on-premises Cisco AWS Directory Service, requiring some manual configuration."
"AWS Directory Service needs to improve processing."
"Some of the security protocols are difficult to understand."
"The group policy can be improved."
"I would like to grant partial access to a table contained in a database without having to provide full access to the whole database."
"AWS could improve the number of regions. Azure has passed them. The ned more consistency, as far as the Northeast is concerned."
"The guest user access could be improved."
"This user integration with the Okta integration network could be simplified."
"Okta Workforce Identity could improve the support system, they are too slow."
"A room for improvement in Okta Workforce Identity is its price. It could be cheaper. The biggest benefit of the solution is that everything works securely without extra steps, so you're saving on your workforce's time and effort because your applications work smoothly and securely, but you'd need to pay some amount of money for that. Another area that could be improved, though not necessarily regarding Okta Workforce Identity, is the SSO applications because so many of the source applications charge extra money to put the SSO to work, which means you have to buy a more expensive license. Nowadays, SSO is a mainstream functionality and it should be out-of-the-box in those applications because it's so easy to set up."
"The solution is very expensive."
"Application updates are lacking. Customer support needs to be improved."
"In my country, there's a lot of stealing of mobile phones, and mobile phones are the authentication device through the Okta application. If someone should steal my mobile phone, which is very common in my country, he or she might have access to my company account. That's my concern."
"We experienced some technical glitches that need to be resolved."
 

Pricing and Cost Advice

"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."
"The pricing is reasonable."
"We pay an annual subscription fee."
"AWS' pricing is fair, and costs can be cut if you look carefully at when you're using it."
"The solution is not the cheapest but not the most expensive. They are in the middle rating."
"The price of Okta Workforce Identity is competitively priced. We pay annually for the use of the solution."
"It has a yearly subscription. As compared to its competitors, it is quite expensive. It also has a complex licensing model."
"The licensing is per user per month and includes full technical support."
"The pricing for Okta Workforce Identity could still be improved or made cheaper. It costs from 50 to 100 euros a year per user. Okta Workforce Identity has different packages you can choose from, and my previous company had all of them, particularly the full Okta suite."
"The cost per user for this solution is really high and could be reduced."
"The price of Okta Workforce Identity is reasonable."
"Okta has fairly competitive pricing."
report
Use our free recommendation engine to learn which Identity and Access Management as a Service (IDaaS) (IAMaaS) solutions are best for your needs.
838,713 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
16%
Manufacturing Company
12%
Financial Services Firm
10%
Healthcare Company
9%
Computer Software Company
16%
Financial Services Firm
12%
Manufacturing Company
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?
Currently, there is no option to integrate our on-premises Cisco AWS Directory Service, requiring some manual configuration. If AWS Active Directory Service provided additional domain controller fu...
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 needs improvement with Okta Workforce Identity?
We are facing one issue with Cypress test cases. Whenever I write Cypress test cases, we encounter problems with logging in through Okta. There is no proper documentation on integrating test cases ...
 

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: January 2025.
838,713 professionals have used our research since 2012.