From d32887f1ca6111f24464b157dfdccccf520af628 Mon Sep 17 00:00:00 2001 From: Benjamin Ironside Goldstein Date: Fri, 24 May 2024 15:16:37 -0700 Subject: [PATCH 1/6] updates cloud security section of billing page --- docs/serverless/billing.mdx | 22 +++++++++++++++++++--- 1 file changed, 19 insertions(+), 3 deletions(-) diff --git a/docs/serverless/billing.mdx b/docs/serverless/billing.mdx index 3f6575852e..c42bd1e87d 100644 --- a/docs/serverless/billing.mdx +++ b/docs/serverless/billing.mdx @@ -32,6 +32,22 @@ Cloud Protection is an _optional_ add-on to Security Analytics that provides val * **Cloud Protection Essentials** — Protects your cloud workloads, continuously tracks posture of your cloud assets, and helps you manage risks by detecting configuration issues per CIS benchmarks. * **Cloud Protection Complete** — Adds response capabilities and configuration drift prevention for Cloud Workloads. -You pay based on the number of protected cloud workload and other cloud assets you configure for use with Elastic Cloud Security. Note that logs, events, alerts, and configuration data ingested into your security project are billed using the **Ingest** and **Retention** pricing described above. - -For detailed ((elastic-sec)) serverless project rates, check [Elastic Cloud pricing table](https://cloud.elastic.co/cloud-pricing-table?productType=serverless&project=security). +Your total cost depends on the number of protected cloud workloads and other billable cloud assets you configure for use with Elastic Cloud Security. The following types of assets are considered billable: + +- VMs: + - **AWS:** EC2 instances + - **Azure:** Virtual machines + - **GCP:** Compute engine instances +- Storage resources: + - **AWS:** S3, S3 Glacier, EBS + - **Azure:** Archive, Blob, Managed disk + - **GCP:** Cloud storage, Persistent disk, Coldline storage +- SQL databases and servers: + - **AWS:** RDS, DynamoDB, Redshift + - **Azure:** SQL database, Cosmos DB, Synapse Analytics + - **GCP:** Cloud SQL, Firestore, BigQuery +- Open-source databases + +Note that logs, events, alerts, and configuration data ingested into your security project are billed using the **Ingest** and **Retention** pricing described above. + +For more details about ((elastic-sec)) serverless project rates and billable assets, refer to the [Elastic Cloud pricing table](https://cloud.elastic.co/cloud-pricing-table?productType=serverless&project=security). From b37fd09947787df3fdeee4b10433d2f1f571b3f0 Mon Sep 17 00:00:00 2001 From: Benjamin Ironside Goldstein Date: Fri, 31 May 2024 08:11:40 -0700 Subject: [PATCH 2/6] updates --- docs/serverless/billing.mdx | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/docs/serverless/billing.mdx b/docs/serverless/billing.mdx index c42bd1e87d..0cfe2a612c 100644 --- a/docs/serverless/billing.mdx +++ b/docs/serverless/billing.mdx @@ -32,7 +32,9 @@ Cloud Protection is an _optional_ add-on to Security Analytics that provides val * **Cloud Protection Essentials** — Protects your cloud workloads, continuously tracks posture of your cloud assets, and helps you manage risks by detecting configuration issues per CIS benchmarks. * **Cloud Protection Complete** — Adds response capabilities and configuration drift prevention for Cloud Workloads. -Your total cost depends on the number of protected cloud workloads and other billable cloud assets you configure for use with Elastic Cloud Security. The following types of assets are considered billable: +Your total cost depends on the number of protected cloud workloads and other billable cloud assets you configure for use with Elastic Cloud Security. + +For the following types of assets are considered billable: - VMs: - **AWS:** EC2 instances @@ -46,8 +48,9 @@ Your total cost depends on the number of protected cloud workloads and other bil - **AWS:** RDS, DynamoDB, Redshift - **Azure:** SQL database, Cosmos DB, Synapse Analytics - **GCP:** Cloud SQL, Firestore, BigQuery -- Open-source databases + +For , only Kubernetes nodes are considered billable. Note that logs, events, alerts, and configuration data ingested into your security project are billed using the **Ingest** and **Retention** pricing described above. -For more details about ((elastic-sec)) serverless project rates and billable assets, refer to the [Elastic Cloud pricing table](https://cloud.elastic.co/cloud-pricing-table?productType=serverless&project=security). +For more details about ((elastic-sec)) serverless project rates and billable assets, refer to Cloud Protection in the [Elastic Cloud pricing table](https://cloud.elastic.co/cloud-pricing-table?productType=serverless&project=security). From a50b7ae9b8c9e77d3529b4ebc80c6f890477d8ee Mon Sep 17 00:00:00 2001 From: Benjamin Ironside Goldstein Date: Fri, 31 May 2024 08:40:00 -0700 Subject: [PATCH 3/6] adds detail --- docs/serverless/billing.mdx | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/docs/serverless/billing.mdx b/docs/serverless/billing.mdx index 0cfe2a612c..4d1529a436 100644 --- a/docs/serverless/billing.mdx +++ b/docs/serverless/billing.mdx @@ -34,7 +34,7 @@ Cloud Protection is an _optional_ add-on to Security Analytics that provides val Your total cost depends on the number of protected cloud workloads and other billable cloud assets you configure for use with Elastic Cloud Security. -For the following types of assets are considered billable: +For billing is per billable, monitored `resource.id`. The following types of assets are considered billable: - VMs: - **AWS:** EC2 instances @@ -49,7 +49,11 @@ For the following types of as - **Azure:** SQL database, Cosmos DB, Synapse Analytics - **GCP:** Cloud SQL, Firestore, BigQuery -For , only Kubernetes nodes are considered billable. +For , billing is per monitored Kubernetes nodes (per `agent.id`). + +For , billing is per monitored cloud asset (per `cloud.instance.id`). + +For , billing is per agent (per `agent.id`). Note that logs, events, alerts, and configuration data ingested into your security project are billed using the **Ingest** and **Retention** pricing described above. From cef5ac13fc779b622e4d48c5a8fce62a837a2ecf Mon Sep 17 00:00:00 2001 From: Benjamin Ironside Goldstein Date: Fri, 31 May 2024 08:57:55 -0700 Subject: [PATCH 4/6] minor updates --- docs/serverless/billing.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/serverless/billing.mdx b/docs/serverless/billing.mdx index 4d1529a436..6830e02ade 100644 --- a/docs/serverless/billing.mdx +++ b/docs/serverless/billing.mdx @@ -34,7 +34,7 @@ Cloud Protection is an _optional_ add-on to Security Analytics that provides val Your total cost depends on the number of protected cloud workloads and other billable cloud assets you configure for use with Elastic Cloud Security. -For billing is per billable, monitored `resource.id`. The following types of assets are considered billable: +For billing is per monitored and billable resource (per `resource.id`). The following types of assets are considered billable: - VMs: - **AWS:** EC2 instances @@ -53,7 +53,7 @@ For , billing is per monitored For , billing is per monitored cloud asset (per `cloud.instance.id`). -For , billing is per agent (per `agent.id`). +For , billing is per protected agent (per `agent.id`). Note that logs, events, alerts, and configuration data ingested into your security project are billed using the **Ingest** and **Retention** pricing described above. From 44864c6c96733b550db76dc52d918e28ffa78d9b Mon Sep 17 00:00:00 2001 From: Benjamin Ironside Goldstein Date: Fri, 31 May 2024 11:25:40 -0700 Subject: [PATCH 5/6] incorporates Nastasha's review --- docs/serverless/billing.mdx | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/serverless/billing.mdx b/docs/serverless/billing.mdx index 6830e02ade..aa1a311b96 100644 --- a/docs/serverless/billing.mdx +++ b/docs/serverless/billing.mdx @@ -34,7 +34,7 @@ Cloud Protection is an _optional_ add-on to Security Analytics that provides val Your total cost depends on the number of protected cloud workloads and other billable cloud assets you configure for use with Elastic Cloud Security. -For billing is per monitored and billable resource (per `resource.id`). The following types of assets are considered billable: +For billing is based on how many billable resources (`resource.id`s) you monitor. The following types of assets are considered billable: - VMs: - **AWS:** EC2 instances @@ -49,12 +49,12 @@ For billing is per monitored - **Azure:** SQL database, Cosmos DB, Synapse Analytics - **GCP:** Cloud SQL, Firestore, BigQuery -For , billing is per monitored Kubernetes nodes (per `agent.id`). +For , billing is based on how many Kubernetes nodes (`agent.id`s) you monitor. -For , billing is per monitored cloud asset (per `cloud.instance.id`). +For , billing is based on how many cloud assets (`cloud.instance.id`s) you monitor. -For , billing is per protected agent (per `agent.id`). +For , billing is based on how many agents (`agent.id`s) you use. -Note that logs, events, alerts, and configuration data ingested into your security project are billed using the **Ingest** and **Retention** pricing described above. +Logs, events, alerts, and configuration data ingested into your security project are billed using the **Ingest** and **Retention** pricing described above. For more details about ((elastic-sec)) serverless project rates and billable assets, refer to Cloud Protection in the [Elastic Cloud pricing table](https://cloud.elastic.co/cloud-pricing-table?productType=serverless&project=security). From 7244ed7d4e5dcee2c1b9783f1511d37505a1e3e7 Mon Sep 17 00:00:00 2001 From: Benjamin Ironside Goldstein <91905639+benironside@users.noreply.github.com> Date: Fri, 31 May 2024 13:09:24 -0700 Subject: [PATCH 6/6] Update docs/serverless/billing.mdx Co-authored-by: Nastasha Solomon <79124755+nastasha-solomon@users.noreply.github.com> --- docs/serverless/billing.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/serverless/billing.mdx b/docs/serverless/billing.mdx index aa1a311b96..72662c191f 100644 --- a/docs/serverless/billing.mdx +++ b/docs/serverless/billing.mdx @@ -34,7 +34,7 @@ Cloud Protection is an _optional_ add-on to Security Analytics that provides val Your total cost depends on the number of protected cloud workloads and other billable cloud assets you configure for use with Elastic Cloud Security. -For billing is based on how many billable resources (`resource.id`s) you monitor. The following types of assets are considered billable: +For , billing is based on how many billable resources (`resource.id`s) you monitor. The following types of assets are considered billable: - VMs: - **AWS:** EC2 instances