We performed a comparison between AWS Directory Service and Okta Workforce Identity based on real PeerSpot user reviews.
Find out in this report how the two Identity and Access Management as a Service (IDaaS) (IAMaaS) solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."Two-step authentication is very useful and important."
"We can provide specific access to people based on what they need from our accounts."
"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 has eliminated the downtime we waste when our on-premises resources go down."
"The most valuable feature of AWS Directory Service is cost-cutting features."
"We like the fact that it's got such great redundancy."
"I like the manageability. Activate Connect makes it easier to assign information and to manage the resources in the network."
"Provides good performance and availability."
"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."
"I am able to authenticate my users on cloud and SaaS applications such as Workday through Okta workflows."
"The most valuable aspects of the solution are the integration with external websites one-factor authentication."
"Its simplicity and its integration with various vendor-agnostic platforms are the most valuable features."
"The product is easy to use."
"We face no challenges in integrating the product with our legacy systems."
"It's reliable and it does what it is advertised to do."
"I find the provisioning features and the integration with other applications useful."
"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."
"We had a problem with the schema uploading and setting up the directory when we are migrating our users from on-premises to cloud infrastructure."
"AWS Directory Service needs to improve processing."
"Can be improved by including on-premises access for services through Identity Access Management."
"The AWS Directory Service should be easier to integrate."
"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."
"AWS could improve the number of regions. Azure has passed them. The ned more consistency, as far as the Northeast is concerned."
"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."
"The pricing could be improved."
"They should focus on improving them to provide top-notch team access management while still offering those typical features."
"Application updates are lacking. Customer support needs to be improved."
"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."
"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."
"The solution can be quite expensive."
"The guest user access could be improved."
AWS Directory Service is ranked 10th in Identity and Access Management as a Service (IDaaS) (IAMaaS) with 12 reviews while Okta Workforce Identity is ranked 2nd in Identity and Access Management as a Service (IDaaS) (IAMaaS) with 59 reviews. AWS Directory Service is rated 8.6, while Okta Workforce Identity is rated 8.4. The top reviewer of AWS Directory Service writes "Extends AD identity and management capabilities to AWS resources". On the other hand, the top reviewer of Okta Workforce Identity writes "Extremely easy to work with, simple to set up, and reasonably priced ". AWS Directory Service is most compared with Microsoft Entra ID, Microsoft Entra External ID, Google Cloud Identity and SailPoint Identity Security Cloud, whereas Okta Workforce Identity is most compared with Microsoft Entra ID, Google Cloud Identity, SailPoint Identity Security Cloud, Saviynt and Auth0. See our AWS Directory Service vs. Okta Workforce Identity report.
See our list of best Identity and Access Management as a Service (IDaaS) (IAMaaS) vendors.
We monitor all Identity and Access Management as a Service (IDaaS) (IAMaaS) reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
