A difficult company to work with

• By Disappointed
• on 10/21/2022

The CloudFormation template seems to have a slight bug in it when you try to use it outside of us-east-1. That or there is an alternative bucket name beside the default I should be using. It was easy to work around in main stack, but the stack references templates for sub-stacks in an S3 bucket. I'm sure I could have grabbed the contents of the bucket, made my own bucket, made my own templates, and made it all work, but it bugged me to bill a client for time spent doing all of this to make a SaaS solution, which should save us time, work.

I've explained the issue to Elastic seven times in the last week. I even included snips of their problematic template, highlighted the offending lines, and suggested how they might fix the issue. But they won't help themselves or me. Instead, they seem terrified that I'm going to get free support out of them, and the free support has taken days to demonstrate that they don't know what I am saying. I still could have worked around this, but I fear it foreshadows what future interaction might be like if I did get cornered by an issue.

Two stars vs. one, because I've used the product under Docker Compose. Elastic Stack has issues, but it is generally an exciting and powerful product. I don't want to be stuck working with a company that acts this way and I believe that it is primarily the managed service they are offering that I am reviewing.