Re:OpenSearch: AWS fork of Elasticsearch and Kibana
by StreamBright on Monday April 12, 2021 @02:53PM
(#26783511)
Do you know can I migrate my sophisticated security setup easily over? Including users, groups, roles, policies and instance policies.
[ Parent
| on HN ]
Re:OpenSearch: AWS fork of Elasticsearch and Kibana
by fastball on Monday April 12, 2021 @02:59PM
(#26783588)
Everything on AWS is accessible via API, which means you can easily automate the migration process. So do that?
Obviously the more complex a system is the harder it will be to migrate, but that has nothing to do with Amazon trying to "lock you in" and everything to do with it just being a complex system that there is no industry standard solution for.
Re:OpenSearch: AWS fork of Elasticsearch and Kibana
by JamesSwift on Wednesday April 14, 2021 @09:43AM
(#26806937)
It appears you are using one definition of lock in while others are using another. What your version of lock in seems to entail is deliberate actions by the hosting provider to force you to stay with their offering. When I (and others it seems) use it, it just means the natural friction that keeps you in the provider. It doesnt have to be a deliberate strategy to be lock in. That doesnt make it any less difficult/painful to migrate.