>The issue that Elastic had is that their entire business model was offering a managed elasticsearch solution. Amazon then created their own offering of the same thing
Amazon first offered Elasticsearch as a managed service in 2015.
Elastic began offering managed services in 2018.
This is not correct. ISPs cannot see the actual URL being requested. Your DNS provider can see the hostname. The ISP may be able to see the hostname unless encrypted SNI is in place. The ISP can see the IP address you are connecting to.
It might have been called something else like cloud hosting, but it was definitely equivalent to a shared hosting model. We didn't manage the web servers, no root access etc and the database server was shared between 300+ of their customers.
>Highly trained people handled the company’s incoming telephone and online inquiries
Not sure I can agree with this. Almost a decade ago we had some shared hosting accounts at Rackspace for some very legacy clients (ones that even accounting had forgotten about and not billed them for years). We had an issue with accessing one of the databases to export for handover, and so I got in touch with their online support. They gave me full admin access to their database server which had several hundred other clients on there. I could also see the historical metrics for the server which were interesting. I told them immediately but it took them almost a day to revoke my access.
Amazon first offered Elasticsearch as a managed service in 2015. Elastic began offering managed services in 2018.
https://en.wikipedia.org/wiki/Elasticsearch#Managed_services