Why DaaS Replaces AWS Directory Service

Written by Greg Keller on April 4, 2017

Share This Article

The need for managing and controlling users from a cloud-based service is now becoming clearly understood by the IT and sys admin communities with announcements by Amazon’s AWS, Google Identity Management Services, and our own IDaaS platform, Directory-as-a-Service®.

The evolution of cloud identity management approaches is easy to see.

The Evolution of IDaaS

identity management active directory
IDaaS Evolution

Traditionally, IT admins started with on-prem solutions such as Microsoft Active Directory®. Nearly a decade ago, the first generation of IDaaS platforms appeared. These solutions were essentially web application single sign-on solutions that worked closely with AD. They were effectively an extension to the on-prem AD for web applications. This fit the bill at the time. As time went on, though, IT environments were changing.

The shift to the cloud was not only with web applications but also cloud servers. Internal IT changes included the shift to non-Windows platforms as well as the move to WiFi from wired networks. These changes were dramatically altering how IT admins needed to manage user access. Active Directory and web application SSO solutions weren’t enough.

That’s when modern cloud identity management platforms appeared. Directory-as-a-Service® took the lead and was the first cloud directory service introduced. This cloud directory from JumpCloud® is meant to be a replacement to Active Directory where IT organizations can centralize user management across platforms, providers, protocols, and locations.

Enter AWS Directory Service

AWS Directory Service

AWS introduced a number of flavors to their directory service solution. While one solution is based on the open-source software SAMBA, the other is the commercial Microsoft Active Directory. AWS Directory Service will appeal to AWS administrators as a simplification of their current user provisioning chores for that specific platform with Windows devices. What a welcome and necessary set of efficiencies! AWS Directory Service isn’t a viable solution for Linux, Mac, on-prem resources, and more. Think of AWS Directory Service as a user management tool for AWS Windows servers.

The Next Generation of Directory Services

cloud identity management jumpcloud

On the other hand, JumpCloud’s cloud identity management platform extends beyond authentication and authorization of users into more robust directory capabilities. The Directory-as-a-Service cross-platform approach enables administrators to integrate and manage users on AWS in exactly the same transparent fashion as they can with Rackspace, Softlayer/IBM, Digital Ocean, co-located clouds or any on-premises systems. Moreover, our IDaaS platform will enable administrators to manage users against any cross-platform server or employee device (Linux, Windows, or macOS). JumpCloud’s cloud directory also pushes to deeper areas of system management, thereby creating cross-platform GPO-like capabilities. Furthermore, JumpCloud’s IDaaS platform has True Single Sign-On capabilities, multi-factor authentication, hosted LDAP, cloud RADIUS, and more. Think of JumpCloud as the next generation of directory services that has vendor neutrality.

JumpCloud IDaaS Replaces AWS Directory Service

We invite you to talk with us about directory services and learn more about JumpCloud’s IDaaS platform and our broader cross-platform capabilities. Sign up today to begin using DaaS free for the first 10 users. We’d be happy to walk you through how JumpCloud compares to AWS Directory Service and other cloud identity management solutions.

Continue Learning with our Newsletter