OpenSearch: AWS fork of Elasticsearch and Kibana

Re:OpenSearch: AWS fork of Elasticsearch and Kibana by fastball on Monday April 12, 2021 @02:58PM (#26783571)

What would you say they lock you into? What is AWS doing specifically that makes it harder to move between providers than if they were not doing that thing?

[ Parent | on HN ]

Re:OpenSearch: AWS fork of Elasticsearch and Kibana by JamesSwift on Monday April 12, 2021 @03:39PM (#26784135)

1) A vast majority of users are relying on managed services to some degree.

2) Permissions as a whole are usually very ingrained into much of what orgs rely on.

[ Parent | on HN ]

Re:OpenSearch: AWS fork of Elasticsearch and Kibana by fastball on Monday April 12, 2021 @04:15PM (#26784586)

What do you mean when you say managed services? Because to me managed services are definitely not vendor lock-in because you can self-host most of those services and just migrate your data over.

With regards to permissions, I don't feel like it's possible to permission across an entire platform and not make it difficult to migrate over – do you know of any provider or platform that allows for cross-platform authentication with permissions?

[ Parent | on HN ]

Re:OpenSearch: AWS fork of Elasticsearch and Kibana by JamesSwift on Monday April 12, 2021 @04:44PM (#26784915)

I generally think of managed services as anything not run directly on EC2.

I agree about permissions. I'm just illustrating where the lock in occurs.

[ Parent | on HN ]