How to calculate Elasticsearch Cloud in Azure TCO

Elastic Stack Elasticsearch
1

Apologies I couldn't find a better category to raise this question.

I want to consider moving diagnostics indices to Elasticsearch Cloud and I can use their following link to calculate the costs of subscription. But I cannot find anywhere information on how to calculate other costs, unless they are already accommodated in this calculation?
Azure infrastructure costs?
Data transfer costs?
Snapshot storage costs?
Any other costs I am missing?

Elasticsearch Service pricing calculator — Elastic Cloud

Thank you all in advance.

2

Hi @kdwolf Thanks for looking at Elastic Cloud...

That is included in the Calculator / Price.
The price includes Product + Infrastructure + Support (depending on the Level)

Yes, sorry, that is not in the calculator because that can vary by use case.

For an an observability Use case DTS (Data Transfer and Storage) will typically be 10-20%

For other use cases you will need to POC etc.

If you use Enterprise / Frozen... there is more in Snapshot but less in Disk :slight_smile:

The actual costs can be found here:
https://cloud.elastic.co/cloud-pricing-table?productType=stack_hosted&provider=gcp&region=gcp-us-central1

The best thing to do is run a small POC and do some estimates.

One other thing if you are open to AWS You could also look at the new Serverless Offering .... Azure is coming soon...

3

Thank you, @stephenb
It has to remain within Azure ecosystem. I could see there is 14 days free trial we could use for PoC, but I am not sure if it will provide us with any guidelines at the end, based on our traffic and volumes?

Kind regards

4

You will be able to see what you used at the end of the trial ... Consumption is shown daily I believe...

Really if you are considered elastic cloud.. you should do a 30 day paid monthly to look at the TCO in my opinion...

The trial will give you a taste but it size and duration is limited as expected...

2 Likes
5

Thank you, @stephenb
With regards to the Frozen - I think it says 6.5TB with 360GB cached.
Can you elaborate on how it works, please?
I would think of the smallest Hot tear on offer (35GB) and then straight to Frozen.
The diagnostics in our case is fire and forget: we won't touch it, unless an issue with our product was identified and we need to investigate.

6

@stephenb may I use this opportunity and ask you to elaborate on the following, please:

  1. Security of Elasticsearch Cloud in Azure: as it is machine to machine communication, API Keys? ClientID?
  2. If our app is in Azure and we write the logs into Elasticsearch Cloud on Azure, do the data leave Azure's private network at any point, traveling to Elasticsearch Cloud?
7

A Frozen node has local SSD that acts as a cache to the data that's living in the S3 blob Storage...The SSD is provisioned at the time the frozen node is setup.. and support the S3 as it grows

At that scale you should test...
Hot -> Direct to Frozen is a completely valid architecture and is used widely.

We do no comment on that level of detail on the public forum.
I suggest you look at the following

This depends on your architecture... If you use Azure Private -Link the traffic remains within the azure network

1 Like