From 9f01b349ce2ce451cb72d1f08607615949612fe0 Mon Sep 17 00:00:00 2001 From: Kelly Murphy Date: Wed, 16 Sep 2020 16:57:06 -0500 Subject: [PATCH] Correct bad cross-product links (#384) Old: ec-getting-started-templates.html New: ec-getting-started-solutions.html AND ec-getting-started-profiles.html Updated wording as well. --- docs/ecctl-getting-started.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/ecctl-getting-started.asciidoc b/docs/ecctl-getting-started.asciidoc index 75dd2ff1..c6b0a6b9 100644 --- a/docs/ecctl-getting-started.asciidoc +++ b/docs/ecctl-getting-started.asciidoc @@ -282,7 +282,7 @@ ID NAME ELASTICSEARCH [id="{p}-example-create-deployment"] === Create a deployment -Let's create a basic deployment. Elasticsearch Service supports {cloud}/ec-getting-started-templates.html[deployment templates], which pre-configure the Elastic Stack components in your deployment to best suit your particular use case. For this example, use Google Cloud Platform (GCP) to host the deployment in region `US Central 1 (Iowa)`. To know which deployment options are available by platform, see {cloud}/ec-regions-templates-instances.html[available regions, deployment templates and instance configurations]. +Let's create a basic deployment. Elasticsearch Service supports {cloud}-getting-started-solutions[solutions] and {cloud}/ec-getting-started-profiles.html[hardware profiles], which pre-configure the Elastic Stack components in your deployment to best suit your particular use case. For this example, use Google Cloud Platform (GCP) to host the deployment in region `US Central 1 (Iowa)`. To know which deployment options are available by platform, see {cloud}/ec-regions-templates-instances.html[available regions, deployment templates and instance configurations]. Copy the following JSON payload and save it as file `create-deployment.json`.