Comparing JumpCloud® vs AWS® Directory Service

Comparing JumpCloud® vs AWS® Directory Service

The cloud directory space has been heating up as of late. With what seems like an endless number of alternatives to Active Directory® (MAD or AD) emerging, one particular area of interest for IT admins is the comparison of JumpCloud® Directory-as-a-Service®platform vs AWS® Directory Services.

How IDaaS has Changed

How IDaaS has changed over the years

Before we look at JumpCloud vs AWS Directory Service, we should look at how the identity management realm has evolved. If you were to look back in time at the traditional office space, you would find a whole slew of Windows® products. This in turn made Active Directory the on-prem directory of choice, due to its seamless integration with Windows resources.

Nearly a decade ago, however, we saw the first generation of IDaaS, or Identity-as-a-Service, platforms emerge. Known as web application single sign-on solutions, these resources worked very closely with AD in order to extend on-prem identities to the resources Active Directory couldn’t integrate with as easily. While this may have worked at the time, the IT landscape is constantly evolving and we’ve started to see the repercussions of building on top of an antiquated directory service.

What is AWS Directory Service?

What is AWS Directory Service?

Interestingly, the comparison between JumpCloud vs AWS Directory Services is really a comparison between JumpCloud and Active Directory, since AWS’ core directory services offering is simply a hosted AD instance. Now, AWS does have what they call Simple AD, which is essentially Samba under the covers, but their primary focus has been on reselling Active Directory to their customers.

It is important to understand the use case here with AWS. Their goal is to increase the utilization of their infrastructure and enabling IT and DevOps organizations to extend their existing identity infrastructure to their cloud offerings. Because most organizations leverage AD as their on-prem identity provider, AWS saw it tactful to simply build a compatible stack in their cloud. This made a lot of sense from their perspective, a user management tool for AWS Windows servers. However, this made AWS Directory Service a nonviable or less viable solution for Linux (Read more...)

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