Skip to content

Commit b12b5bf

Browse files
authored
Add pricing info everywhere (#45)
1 parent c0a08ac commit b12b5bf

File tree

7 files changed

+25
-4
lines changed

7 files changed

+25
-4
lines changed

serverless/pages/get-started.mdx

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -5,6 +5,8 @@ description: Get started with ((es3)) in a few steps
55
tags: [ 'serverless', 'elasticsearch', 'getstarted', 'overview' ]
66
---
77

8+
import MinimumVcusDetail from '../partials/minimum-vcus-detail.mdx'
9+
810
<DocBadge template="technical preview" />
911
Follow along to set up your ((es)) project and get started with some sample documents.
1012
Then, choose how to continue with your own data.
@@ -30,6 +32,8 @@ Use your ((ecloud)) account to create a fully-managed ((es)) project:
3032

3133
You should now see **Get started with ((es))**, and you're ready to continue.
3234

35+
<MinimumVcusDetail />
36+
3337
## Create API key
3438

3539
Create an API key, which will enable you to access the ((es)) API to ingest and search data.

serverless/pages/manage-billing-monitor-usage.mdx

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -21,3 +21,6 @@ On the **Usage** page you can:
2121
The usage breakdown information is an estimate. To get the exact amount you owe for a given month, check your invoices in the <DocLink slug="/serverless/general/billing-history" text="billing history"/>.
2222
</DocCallOut>
2323

24+
<DocCallOut color="warning" title="Elasticsearch minimum runtime VCUs">
25+
When you create an Elasticsearch Serverless project, a minimum number of VCUs are always allocated to your project to maintain basic ingest and search capabilities. These VCUs incur a minimum cost even with no active usage. Learn more about [minimum VCUs on Elasticsearch Serverless](https://www.elastic.co/pricing/serverless-search#what-are-the-minimum-compute-resource-vcus-on-elasticsearch-serverless).
26+
</DocCallOut>

serverless/pages/manage-billing-pricing-model.mdx

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,12 +7,11 @@ tags: [ 'serverless', 'general', 'billing', 'pricing model' ]
77

88
<DocBadge template="technical preview" />
99

10-
Elastic Cloud serverless billing is based on your actual usage across these dimensions:
10+
Elastic Cloud serverless billing is based on your usage across these dimensions:
1111

1212
* <DocLink slug="/serverless/general/serverless-billing" section="offerings">Offerings</DocLink>
1313
* <DocLink slug="/serverless/general/serverless-billing" section="add-ons">Add-ons</DocLink>
1414

15-
1615
<div id="offerings"></div>
1716

1817
## Offerings

serverless/pages/manage-billing.mdx

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -25,3 +25,5 @@ From the **Billing pages**, you can perform the following tasks:
2525

2626
If you have a project that you're no longer using, refer to <DocLink slug="/serverless/general/billing-stop-project" text="Stop charges for a project"/>.
2727

28+
To learn about the serverless pricing model, refer to <DocLink slug="/serverless/general/serverless-billing" text="Serverless billing dimensions"/> and our [pricing page](https://www.elastic.co/pricing/serverless-search).
29+

serverless/pages/pricing.mdx

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,17 +5,21 @@ description: Learn about how Elasticsearch usage affects pricing.
55
tags: [ 'serverless', 'elasticsearch', 'overview' ]
66
---
77

8+
import MinimumVcusDetail from '../partials/minimum-vcus-detail.mdx'
9+
810
<p><DocBadge template="technical preview" /></p>
911

1012
Elasticsearch is priced based on the consumption of the underlying
1113
infrastructure used to support your use case, with the performance
1214
characteristics you need. We measure by Virtual Compute Units (VCUs), which is a
1315
slice of RAM, CPU and local disk for caching. The number of VCUs required will
1416
depend on the amount and the rate of data sent to Elasticsearch and retained,
15-
and the number of searches and latency you require for Searches. In addition, if
17+
and the number of searches and latency you require for searches. In addition, if
1618
you required ((ml)) for inference or NLP tasks, those VCUs are also
1719
metered and billed.
1820

21+
<MinimumVcusDetail />
22+
1923
## Information about the VCU types (Search, Ingest, and ML)
2024

2125
There are three VCU types in Elasticsearch:

serverless/pages/sign-up.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -60,7 +60,7 @@ To remove limitations, subscribe to [Elastic Cloud](https://www.elastic.co/guide
6060
- Third availability zone for your deployments.
6161
- Access to additional features, such as cross-cluster search and cross-cluster replication.
6262

63-
You can subscribe to Elastic Cloud at any time during your trial. Billing starts when you subscribe. To maximize the benefits of your trial, subscribe at the end of the free period. To monitor charges, anticipate future costs, and adjust your usage, check your [account usage](https://www.elastic.co/guide/en/cloud/current/ec-account-usage.html) and [billing history](https://www.elastic.co/guide/en/cloud/current/ec-billing-history.html).
63+
You can subscribe to Elastic Cloud at any time during your trial. [Billing](/serverless/general/serverless-billing) starts when you subscribe. To maximize the benefits of your trial, subscribe at the end of the free period. To monitor charges, anticipate future costs, and adjust your usage, check your [account usage](https://www.elastic.co/guide/en/cloud/current/ec-account-usage.html) and [billing history](https://www.elastic.co/guide/en/cloud/current/ec-billing-history.html).
6464

6565
## How do I get started with my trial?
6666

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
<DocCallOut color="warning" title="Minimum runtime VCUs">
2+
When you create an Elasticsearch Serverless project, a minimum number of VCUs are always allocated to your project to maintain basic capabilities. These VCUs are used for the following purposes:
3+
4+
- **Ingest**: Ensure constant availability for ingesting data into your project (4 VCUs).
5+
- **Search**: Maintain a data cache and support low latency searches (8 VCUs).
6+
7+
These minimum VCUs are billed at the standard rate per VCU hour, incurring a minimum cost even when you're not actively using your project.
8+
Learn more about [minimum VCUs on Elasticsearch Serverless](https://www.elastic.co/pricing/serverless-search#what-are-the-minimum-compute-resource-vcus-on-elasticsearch-serverless).
9+
</DocCallOut>

0 commit comments

Comments
 (0)