AWS® Cloud Directory vs JumpCloud® Directory-as-a-Service®

AWS® Cloud Directory vs JumpCloud® Directory-as-a-Service®

There’s recently been some confusion about what a cloud directory is. Last year, Amazon announced their AWS® Cloud Directory service. Then, there is another cloud directory service called JumpCloud® Directory-as-a-Service® that is changing the way IT admins think about directory services.  So, what’s what here and is this a situation where it is AWS Cloud Directory vs JumpCloud Directory-as-a-Service in the marketplace?

The short answer is that you are talking about apples and oranges when it comes to AWS Cloud Directory vs JumpCloud Directory-as-a-Service. The confusion is understandable though, considering that the term cloud directory has taken on some interesting interpretations over the years. Let’s start clearing the air by taking a look at Amazon’s interpretation.

What AWS Cloud Directory Is and Is Not

AWS Cloud Directory

AWS Cloud Directory is “not a directory service for IT Administrators who want to manage or migrate their directory infrastructure” (AWS). Rather, AWS Cloud Directory is a database where organizations can store object information and hierarchically relate that information together along with various attributes. It’s a useful tool and can be thought of as a platform as a service offering. AWS is hoping that IT organizations and developers will leverage the platform and build all kinds of interesting solutions on top of it. Their examples include HR systems, organizational charts, and automobile fleet management systems. That’s a far cry from the traditional directory services definition that IT admins know. However, the definition of what is a directory service is changing as JumpCloud Directory-as-a-Service bends the idea of what a directory service is and the cloud directory moniker.

The Old Definition for Directory Services

Legacy Active Directory

Most IT organizations equate directory services with legacy, on-prem solutions such as Microsoft® Active Directory® and OpenLDAP™. These solutions connected users to all of their IT resources, but they only support on-prem resources that are based on a sole protocol, provider, and platform. For example, most in the IT space know that Active Directory manages users and systems best in on-prem, Microsoft-centric environments. OpenLDAP, on the other hand, works great for managing technical, open source (Read more...)

*** This is a Security Bloggers Network syndicated blog from Blog – JumpCloud authored by Zach DeMeyer. Read the original post at: https://jumpcloud.com/blog/aws-cloud-directory-vs-jumpcloud-directory-as-a-service/

Zach DeMeyer

Zach DeMeyer

Zach is a writer and researcher for JumpCloud with a degree in Mechanical Engineering from the Colorado School of Mines. He loves being on the cutting edge of new technology, and when he's not working, he enjoys all things outdoors, making music, and soccer.

zach-demeyer has 130 posts and counting.See all posts by zach-demeyer