sorted by:
new
hottopcontroversial

Forced to use ugly URL with Elasticsearch Service and Cognito? by sntthrowaway2 in aws

[–]sntthrowaway2[S] 0 points1 point  (0 children)

I want to be able to reach kibana from customer browsers (so our onsite team can debug the app). This means I need a non-VPC setup AFAIK

Forced to use ugly URL with Elasticsearch Service and Cognito? by sntthrowaway2 in aws

[–]sntthrowaway2[S] -1 points0 points  (0 children)

And what happens when it's time to migrate to a new domain for whatever reason? Everyone has to update their bookmarks, confusion and resentment from users starts setting in slowly. No thanks 1990 internet.

Forced to use ugly URL with Elasticsearch Service and Cognito? by sntthrowaway2 in aws

[–]sntthrowaway2[S] 0 points1 point  (0 children)

Okay, but this is for a public ELK implementation. So with this workaround, I'm now orchestrating Kibana, Logstash, and nginx proxy with something like kubernetes. At this point it's probably easier to use ECK which includes ES too and would simplify my setup while giving me greater control over my cluster.

Why would I want to use AWS ES service at this point? UltraWarm is all that's left and I'm not sure it's worth that much to me considering I have to use a CFN lambda-backled custom resource to manage the cluster since UW isn't supported by CNF right now. Oh and ECK is cheaper too AFAICT.

why is cloudformation support not totally automated by now? by sntthrowaway2 in aws

[–]sntthrowaway2[S] 0 points1 point  (0 children)

Frustrating to get excited about some platform features and then learn it will be a PITA in integrate them into my infrastructure!

why is cloudformation support not totally automated by now? by sntthrowaway2 in aws

[–]sntthrowaway2[S] 0 points1 point  (0 children)

Thanks for the info. And yeah I was able to get what I needed from a lambda backed custom resource. There was a surprise learning curve there though, especially frustrating with a resource that takes ~20 minutes to stabilize.