Elastic Cloud Billing Setup

• Manual setup
• Terraform / API

Open Costory and go to Billing > Import new billing datasource > Elastic Cloud. The stepper guides you through each field.

1. In the Elastic Cloud Console, open your organization and copy the Organization ID (you need it for the Costory form).

2. Create an Elastic Cloud Organization API key with access to billing scope. Only organization owners can create these keys. See Elastic Cloud API keys.
3. In Costory, enter a datasource name, paste the API key and Organization ID, then submit. Validation calls the Billing API to confirm access.
4. Start Date is optional. Use it to narrow the first sync window or cap the range Costory ingests. If you leave them empty, Costory uses its default initial backfill (see Historical data).

On first sync, Costory backfills approximately 6 months of historical billing data (one day at a time). Incremental syncs then keep data current.

1. In the Elastic Cloud Console, copy your Organization ID and ensure you have an Elastic Cloud Organization API key with billing scope. Elastic does not provide Terraform resources for these credentials; create them in the console or via Elastic’s APIs. See Elastic Cloud API keys.

2. Add the datasource to Costory with the Costory Terraform provider:

terraform {
  required_providers {
    costory = {
      source  = "costory-io/costory"
      version = ">= 0.1.0"
    }
  }
}

variable "costory_api_token" {
  type        = string
  description = "Costory API token."
  sensitive   = true
}

variable "elastic_cloud_api_key" {
  type        = string
  description = "Elastic Cloud API key used to fetch billing data."
  sensitive   = true
}

variable "elastic_cloud_organization_id" {
  type        = string
  description = "Elastic Cloud organization ID."
}

provider "costory" {
  token = var.costory_api_token
}

resource "costory_billing_datasource_elastic_cloud" "main" {
  name             = "Elastic Cloud Billing"
  api_key          = var.elastic_cloud_api_key
  organization_id  = var.elastic_cloud_organization_id
}

​

Data in Costory

• Search VCU (regional usage)
  • Service name / SKU Description: Elasticsearch - General Purpose - Search VCU (GCP us-central1)
  • SKU ID: elasticsearch.general-purpose-search-vcu_gcp-us-central1
  • Category: VCU
  • Consumed quantity / Pricing quantity: 0.0016008
  • Consumed unit / Pricing unit: VCU
• Retained storage
  • Service name / SKU Description: Elastic’s full label for that storage line (same style as other product lines).
  • SKU ID: elasticsearch.retained_gcp-us-central1
  • Category: Depends on Elastic’s type for that line (for example storage-related).
• Support (often zero rate)
  • Service name / SKU Description: Elastic’s label for the support tier.
  • SKU ID: serverless.support-tier1
  • Category: support

​

API reference

​

Field reference

​

Historical data

• Product-line-level costs for Elastic Cloud projects in your organization: each row is a project × usage day × product line (see Data in Costory).
• Deployments Elastic bills through the org (for example Elasticsearch and other Elastic Cloud project types returned by the API).
• SKUs and service names from Elastic’s billing lines, plus region when Elastic encodes it on the SKU.
• ECU context as labels on each line, and USD amounts aligned with Elastic line quantity × rate.

​

Related