Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[DOCS] Mention that ESF may result in additional charges #446

Merged
merged 4 commits into from
Aug 8, 2023
Merged

[DOCS] Mention that ESF may result in additional charges #446

Show file tree
Hide file tree
Changes from 3 commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
772eedb
[DOCS] Mention that ESF may result in additional charges
dedemorton Aug 1, 2023
f352004
Merge branch 'main' into issue#444
kaiyan-sheng Aug 3, 2023
04bcd47
Apply changes from kaiyan-sheng
dedemorton Aug 8, 2023
8869243
Delete repeated text.
dedemorton Aug 8, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions docs/en/aws-elastic-serverless-forwarder.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,11 @@ The Elastic Serverless Forwarder is an Amazon Web Services ({aws}) Lambda functi

The Elastic Serverless Forwarder works with {stack} 7.16 and later.

IMPORTANT: Using Elastic Serverless Forwarder may result in additional charges
on your next cloud provider billing statement due to increased usage. To learn
dedemorton marked this conversation as resolved.
Show resolved Hide resolved
IMPORTANT: Using Elastic Serverless Forwarder may result in additional charges. To learn
how to minimize additional charges, refer to <<preventing-unexpected-costs>>.
dedemorton marked this conversation as resolved.
Show resolved Hide resolved

[discrete]
[[aws-serverless-forwarder-overview]]
= Overview
Expand Down
1 change: 1 addition & 0 deletions docs/en/aws-serverless-troubleshooting.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,6 +20,7 @@ NOTE: For example, if you don't increase the visibility timeout for an SQS queue
If the Elastic Serverless Forwarder is attached to a VPC, you need to https://docs.aws.amazon.com/vpc/latest/privatelink/create-interface-endpoint.html[create VPC Endpoints] for S3 and SQS, and for *every* service you define as an input for the forwarder. S3 and SQS VPC Endpoints are always required for reading the `config.yaml` uploaded to S3 and managing the _Continuing queue_ and the _Replay queue_, regardless of the <<aws-serverless-forwarder-inputs>> used.

[discrete]
[[preventing-unexpected-costs]]
== Preventing unexpected costs
It is important to monitor the Elastic Serverless Forwarder Lambda function for timeouts to prevent unexpected costs. You can use the https://docs.elastic.co/en/integrations/aws/lambda[AWS Lambda integration] for this. If the timeouts are constant, you should throttle the Lambda function to stop its execution before proceeding with any troubleshooting steps. In most cases, constant timeouts will cause the records and messages from the event triggers to go back to their sources and trigger the function again, which will cause further timeouts and force a loop that will incure unexpected high costs. For more information on throttling Lambda functions, refer to https://docs.aws.amazon.com/lambda/latest/operatorguide/throttling.html[AWS docs].

Expand Down