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)
2nd
Average Rating
8.6
Reviews Sentiment
7.2
Number of Reviews
65
Ranking in other categories
Single Sign-On (SSO) (3rd), Authentication Systems (5th), Privileged Access Management (PAM) (6th), Access Management (2nd), ZTNA as a Service (10th)
 

Mindshare comparison

As of April 2025, in the Identity and Access Management as a Service (IDaaS) (IAMaaS) category, the mindshare of AWS Directory Service is 1.8%, down from 2.5% compared to the previous year. The mindshare of Okta Workforce Identity is 13.3%, up from 13.3% 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 AD Connector is very good and easy to implement."
"I like the manageability. Activate Connect makes it easier to assign information and to manage the resources in the network."
"The most valuable feature is ease of use."
"The support is very good. I would rate the technical support as a 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."
"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."
"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."
"It's reliable and it does what it is advertised to do."
"The product’s most valuable feature is multifactor authentication."
"It's easy to use and straightforward."
"It is a very stable solution."
"The most useful features of Okta for my organization are identity and access management, single sign-on, and the flexibility for hybrid setups."
"I find the provisioning features and the integration with other applications useful."
"It made things a lot easier, especially with passwords."
"I like the tool's workflows, which is user-friendly. It can integrate with different applications. I particularly like that users are delighted to access their applications without the hassle of entering their username and password each time. It truly enhances user-friendliness."
 

Cons

"I would like to see better integration with other business solutions."
"The group policy can be improved."
"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."
"Can be improved by including on-premises access for services through Identity Access Management."
"Accessing the data needs improvement."
"Our only complaint is that you cannot integrate your Exchange server. Or, if you are planning to install an Exchange server on your Amazon EC2 instance, then you need to configure Active Directory on EC2 instance. We would like for this limitation to be lifted."
"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 functionalities, like other on-premises Active Directory, it would be very helpful."
"Okta doesn't have a partial push. It pushes down the full profile schema for lifecycle management or provisioning."
"It would be pricing, which is a tough one because it goes against Microsoft. A lot of companies say they're a Microsoft partner, and they get all their software for free. Okta is like a luxury product, and it's not the most affordable one. I would say if they could work on pricing, it would help. Other than that, they've done great strides in developing a product that is really good. The companies that do see the value tend to invest in it."
"The solution is very expensive."
"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 error logging could be improved. Okta doesn't provide enough details when you are troubleshooting an issue. It's often difficult to fix it from our end, so we always need additional support from Okta."
"The product is expensive compared to other tools."
"We still had to write several internal programs/scripts to complete the user-provisioning process. Okta does not have the ability to provision mailbox accounts for on-premise Exchange or in a hybrid O365 environment. The Group Push function from Okta to AD did not work reliably in our environment."
"SSO and MFA for improved end-user experience, and protection against password spray attacks, account password self-service."
 

Pricing and Cost Advice

"We pay an annual subscription fee."
"The pricing is reasonable."
"AWS' pricing is fair, and costs can be cut if you look carefully at when you're using it."
"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."
"Workforce Identity is well-priced."
"The price of Okta Workforce Identity is competitively priced. We pay annually for the use of the solution."
"License is around US$20,000 annually."
"This is an expensive solution but the security makes it worthwhile."
"The pricing is reasonable."
"The solution is not the cheapest but not the most expensive. They are in the middle rating."
"The solution’s pricing needs to be reasonable. You are dealing with a lot of components and the pricing is component-based."
"The price of this product could be lower."
report
Use our free recommendation engine to learn which Identity and Access Management as a Service (IDaaS) (IAMaaS) solutions are best for your needs.
848,207 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
17%
Financial Services Firm
11%
Healthcare Company
11%
Manufacturing Company
8%
Computer Software Company
16%
Financial Services Firm
11%
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 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?
Okta should have at least a local presense for countries that align with or comply with GDPR or data sovereignty, so there are no compliance or audit questions. There are integration issues with Of...
 

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: March 2025.
848,207 professionals have used our research since 2012.