diff --git a/docs/guides/elasticstack-and-cloud.md b/docs/guides/elasticstack-and-cloud.md
new file mode 100644
index 000000000..2dacd3c01
--- /dev/null
+++ b/docs/guides/elasticstack-and-cloud.md
@@ -0,0 +1,119 @@
+---
+subcategory: ""
+page_title: "Using the Elastic Stack provider with Elastic Cloud"
+description: |-
+    An example of how to spin up a deployment and configure it in a single plan.
+---
+
+# 
+
+A common scenario for using the Elastic Stack provider, is to manage & configure Elastic Cloud deployments.
+In order to do that, we'll use both the Elastic Cloud provider, as well as the Elastic Stack provider.
+Start off by configuring the two providers in a `provider.tf` file for example:
+
+```terraform
+terraform {
+  required_version = ">= 1.0.0"
+
+  required_providers {
+    ec = {
+      source  = "elastic/ec"
+      version = "~>0.3.0"
+    }
+    elasticstack = {
+      source  = "elastic/elasticstack"
+      version = "~>0.1.0"
+    }
+  }
+}
+provider "ec" {
+  # You can fill in your API key here, or use an environment variable instead
+  apikey = "<api key>"
+}
+
+provider "elasticstack" {
+  # In this example, connectivity to Elasticsearch is defined per resource,
+  # so it can be used together with the Elastic Cloud terraform provider.
+}
+```
+
+Notice that the Elastic Stack  provider is not configured, since we'll be using an `elasticsearch_connection` block
+for each of our resources, to point to the Elastic Cloud deployment. This is because `terraform` can not configure providers that are dependent on one another.
+
+Next, we'll set up an Elastic Cloud `ec_deployment` resource, which represents an Elastic Stack deployment on Elastic Cloud.
+We shall configure the deployment using the credentials that it outputs once created
+
+```terraform
+# Creating a deployment on Elastic Cloud GCP region,
+# with elasticsearch and kibana components.
+resource "ec_deployment" "cluster" {
+  region                 = "gcp-us-central1"
+  name                   = "mydeployment"
+  version                = data.ec_stack.latest.version
+  deployment_template_id = "gcp-storage-optimized"
+
+  elasticsearch {}
+
+  kibana {}
+}
+
+data "ec_stack" "latest" {
+  version_regex = "latest"
+  region        = "gcp-us-central1"
+}
+
+# Defining a user for ingesting
+resource "elasticstack_elasticsearch_security_user" "user" {
+  username = "ingest_user"
+
+  # Password is cleartext here for comfort, but there's also a hashed password option
+  password = "mysecretpassword"
+  roles    = ["editor"]
+
+  # Set the custom metadata for this user
+  metadata = jsonencode({
+    "env"    = "testing"
+    "open"   = false
+    "number" = 49
+  })
+
+  # Use our Elastic Cloud deployemnt outputs for connection details.
+  # This also allows the provider to create the proper relationships between the two resources.
+  elasticsearch_connection {
+    endpoints = ["${ec_deployment.cluster.elasticsearch[0].https_endpoint}"]
+    username  = ec_deployment.cluster.elasticsearch_username
+    password  = ec_deployment.cluster.elasticsearch_password
+  }
+}
+
+# Configuring my cluster with an index template as well.
+resource "elasticstack_elasticsearch_index_template" "my_template" {
+  name = "my_ingest_1"
+
+  priority       = 42
+  index_patterns = ["server-logs*"]
+
+  template {
+    aliases {
+      name = "my_template_test"
+    }
+
+    settings = jsonencode({
+      number_of_shards = "3"
+    })
+
+    mappings = jsonencode({
+      properties : {
+        "@timestamp" : { "type" : "date" },
+        "username" : { "type" : "keyword" }
+      }
+    })
+  }
+
+  elasticsearch_connection {
+    endpoints = ["${ec_deployment.cluster.elasticsearch[0].https_endpoint}"]
+    username  = ec_deployment.cluster.elasticsearch_username
+    password  = ec_deployment.cluster.elasticsearch_password
+  }
+}
+```
diff --git a/examples/cloud/deployment.tf b/examples/cloud/deployment.tf
new file mode 100644
index 000000000..0a4a722cb
--- /dev/null
+++ b/examples/cloud/deployment.tf
@@ -0,0 +1,72 @@
+# Creating a deployment on Elastic Cloud GCP region,
+# with elasticsearch and kibana components.
+resource "ec_deployment" "cluster" {
+  region                 = "gcp-us-central1"
+  name                   = "mydeployment"
+  version                = data.ec_stack.latest.version
+  deployment_template_id = "gcp-storage-optimized"
+
+  elasticsearch {}
+
+  kibana {}
+}
+
+data "ec_stack" "latest" {
+  version_regex = "latest"
+  region        = "gcp-us-central1"
+}
+
+# Defining a user for ingesting
+resource "elasticstack_elasticsearch_security_user" "user" {
+  username = "ingest_user"
+
+  # Password is cleartext here for comfort, but there's also a hashed password option
+  password = "mysecretpassword"
+  roles    = ["editor"]
+
+  # Set the custom metadata for this user
+  metadata = jsonencode({
+    "env"    = "testing"
+    "open"   = false
+    "number" = 49
+  })
+
+  # Use our Elastic Cloud deployemnt outputs for connection details.
+  # This also allows the provider to create the proper relationships between the two resources.
+  elasticsearch_connection {
+    endpoints = ["${ec_deployment.cluster.elasticsearch[0].https_endpoint}"]
+    username  = ec_deployment.cluster.elasticsearch_username
+    password  = ec_deployment.cluster.elasticsearch_password
+  }
+}
+
+# Configuring my cluster with an index template as well.
+resource "elasticstack_elasticsearch_index_template" "my_template" {
+  name = "my_ingest_1"
+
+  priority       = 42
+  index_patterns = ["server-logs*"]
+
+  template {
+    aliases {
+      name = "my_template_test"
+    }
+
+    settings = jsonencode({
+      number_of_shards = "3"
+    })
+
+    mappings = jsonencode({
+      properties : {
+        "@timestamp" : { "type" : "date" },
+        "username" : { "type" : "keyword" }
+      }
+    })
+  }
+
+  elasticsearch_connection {
+    endpoints = ["${ec_deployment.cluster.elasticsearch[0].https_endpoint}"]
+    username  = ec_deployment.cluster.elasticsearch_username
+    password  = ec_deployment.cluster.elasticsearch_password
+  }
+}
diff --git a/examples/cloud/provider.tf b/examples/cloud/provider.tf
new file mode 100644
index 000000000..ec03f6bff
--- /dev/null
+++ b/examples/cloud/provider.tf
@@ -0,0 +1,23 @@
+terraform {
+  required_version = ">= 1.0.0"
+
+  required_providers {
+    ec = {
+      source  = "elastic/ec"
+      version = "~>0.3.0"
+    }
+    elasticstack = {
+      source  = "elastic/elasticstack"
+      version = "~>0.1.0"
+    }
+  }
+}
+provider "ec" {
+  # You can fill in your API key here, or use an environment variable instead
+  apikey = "<api key>"
+}
+
+provider "elasticstack" {
+  # In this example, connectivity to Elasticsearch is defined per resource,
+  # so it can be used together with the Elastic Cloud terraform provider.
+}
diff --git a/templates/guides/elasticstack-and-cloud.md.tmpl b/templates/guides/elasticstack-and-cloud.md.tmpl
new file mode 100644
index 000000000..c3dbb6457
--- /dev/null
+++ b/templates/guides/elasticstack-and-cloud.md.tmpl
@@ -0,0 +1,22 @@
+---
+subcategory: ""
+page_title: "Using the Elastic Stack provider with Elastic Cloud"
+description: |-
+    An example of how to spin up a deployment and configure it in a single plan.
+---
+
+# 
+
+A common scenario for using the Elastic Stack provider, is to manage & configure Elastic Cloud deployments.
+In order to do that, we'll use both the Elastic Cloud provider, as well as the Elastic Stack provider.
+Start off by configuring the two providers in a `provider.tf` file for example:
+
+{{ tffile "examples/cloud/provider.tf" }}
+
+Notice that the Elastic Stack  provider is not configured, since we'll be using an `elasticsearch_connection` block
+for each of our resources, to point to the Elastic Cloud deployment. This is because `terraform` can not configure providers that are dependent on one another.
+
+Next, we'll set up an Elastic Cloud `ec_deployment` resource, which represents an Elastic Stack deployment on Elastic Cloud.
+We shall configure the deployment using the credentials that it outputs once created
+
+{{ tffile "examples/cloud/deployment.tf" }}