News for hackers. Stuff that matters.
Re:Uncomfortable AWS Truths by BoorishBears on Sunday September 15, 2019 @10:05PM (#20980580)
I don't fault ES for this necessarily, but the biggest problem with ES is, it's easy to build something that looks like it works, right until it doesn't.

This is a problem for most DBs. You put stuff in, you take stuff out, and it works... but you're putting it in the DB in a way that will make the queries you need nearly impossible to do within your real-world/production constraints (response time, resources required, etc.)

The thing is ES is so different from most DBs, so you need to relearn how to do things right. And to make matters a little more difficult, all DBs have a lot of knobs, but ES just has way more knobs you need to know how to turn to get something that won't fall on it's face in production.

I don't remember my experience with ES on AWS that well besides it was behind on major versions for a while at one point, and if you set up ES resource with CloudFormation... god help you if you need to roll them back.

Using serverless with ES looked something like

api-1 api-2-because-1-is-frozen-rolling-back-cloudformation-es-instances api-3-because-2-is-also-frozen-rolling-back-cloudformation-es-instances api-4-...

Re:Uncomfortable AWS Truths by shiredude95 on Sunday September 15, 2019 @10:19PM (#20980624)
Have you tried elasticcloud? They solve a lot of access problems present in AWS Elasticsearch along with providing the most recent version for deployment.
Re:Uncomfortable AWS Truths by Redsquare on Monday September 16, 2019 @02:07AM (#20981492)
Elasticcloud has terrible security features - they removed IP whitelisting.
Re:Uncomfortable AWS Truths by t0mbstone on Monday September 16, 2019 @04:50PM (#20988473)
They do have user/password authentication though, which is something that barebones ElasticSearch doesn't normally have out of the box by default.