Add docs FAQ topic about deploying to the wrong region (elastic#9085)

dedemorton · Nov 20, 2018 · 1b8672f · 1b8672f
1 parent f49b928
commit 1b8672f
Show file tree

Hide file tree

Showing 2 changed files with 14 additions and 0 deletions.
diff --git a/x-pack/functionbeat/docs/faq.asciidoc b/x-pack/functionbeat/docs/faq.asciidoc
@@ -6,4 +6,16 @@ This section contains frequently asked questions about {beatname_uc}. Also check
 out the https://discuss.elastic.co/c/beats/{beatname_lc}[{beatname_uc}
 discussion forum].
 
+[float]
+[[unable-to-deploy]]
+=== Deployment to AWS fails with "failed to create the stack"?
+
+Deployment fails if you attempt to deploy the Lambda function to the wrong
+region.
+
+You must deploy the function to the region where your services are running. For
+example, if you want to monitor CloudWatch logs for a service running in the
+`us-east-1` region, you must deploy the Lambda function to the same region, or
+deployment fails.
+
 include::{libbeat-dir}/docs/shared-faq.asciidoc[]
diff --git a/x-pack/functionbeat/docs/getting-started.asciidoc b/x-pack/functionbeat/docs/getting-started.asciidoc
@@ -189,6 +189,8 @@ set AWS_SECRET_ACCESS_KEY=EXAMPLE567890devgHIJKMLOPNQRSTUVZ1234KEY
 set AWS_DEFAULT_REGION=us-east-1
 ----
 
+Set `AWS_DEFAULT_REGION` to the region where your services are running.
+
 After setting credentials, run the `deploy` command to deploy the function.
 The following command deploys a function called `cloudwatch`: