AWS has a post re:Invent surprise as it enters the single sign-on market



Steve Jobs used to famously end his keynotes with “there is one more thing…” AWS decided to wait a week after their re:Invent conference ended to announce their more thing when it quietly released a single sign on product for the AWS cloud yesterday.

While the announcement was pretty thin on details, it appears to be focused solely on providing single sign on for the AWS family of products. “With AWS SSO, you can easily manage SSO access and user permissions to all of your accounts in AWS Organizations centrally,” AWS explained in the announcement. That’s very different from what other single sign on products like Okta or OneLogin are doing.

These companies provide a much more comprehensive approach to single sign on, giving you a central way to log into all of your cloud services (and in some cases on-prem too). This saves you the pain of having separate user names and passwords for every account. You log in once and you have access to all of the included cloud services.

AWS doesn’t seem to be going after that market (at least for now). It’s worth noting, however that AWS has a history of starting off by introducing a tool with a simple set of functionality, then layering on additional functionality over time.

Okta is really the key player in this market right now, having introduced cloud single sign-on back in 2009. It went public in April this year after raising over $229 million. It just reported its earnings the other day with revenue of at $68.2 million, surpassing analyst expectations $62.84 million. It has over 3000 customers with 40 million users on the Okta platform.

Just because a large vendor enters a market doesn’t guarantee it success, but that doesn’t mean there isn’t likely some unease at Okta and OneLogIn this morning, just as you would expect when AWS turns its attention to anything in the cloud. One more thing indeed.

Featured Image: Richard Newstead/Getty Images



Source link

Leave a Reply

Your email address will not be published. Required fields are marked *