Skip to content

Commit

Permalink
Add docs FAQ topic about deploying to the wrong region (#9085) (#9185)
Browse files Browse the repository at this point in the history
  • Loading branch information
dedemorton authored Nov 21, 2018
1 parent 57d85d6 commit 8eec851
Show file tree
Hide file tree
Showing 2 changed files with 14 additions and 0 deletions.
12 changes: 12 additions & 0 deletions x-pack/functionbeat/docs/faq.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -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[]
2 changes: 2 additions & 0 deletions x-pack/functionbeat/docs/getting-started.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -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`:

Expand Down

0 comments on commit 8eec851

Please sign in to comment.