You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/reference/aws-deploy-elastic-serverless-forwarder.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -566,7 +566,7 @@ continuing-queue:
566
566
567
567
A bash script for publishing the Elastic Serverless Forwarder directly to your AWS account is available from the [Elastic Serverless Forwarder repository](https://github.com/elastic/elastic-serverless-forwarder).
568
568
569
-
Download the [`publish_lambda.sh` script](https://raw.githubusercontent.com/elastic/elastic-serverless-forwarder/lambda-v1.20.1/publish_lambda.sh) and follow the instructions below.
569
+
Download the [`publish_lambda.sh` script](https://raw.githubusercontent.com/elastic/elastic-serverless-forwarder/lambda-v1.21.0/publish_lambda.sh) and follow the instructions below.
You can update the version of a published Elastic Serverless Forwarder without changing its configuration by running the publishing script again and passing a **new** [`forwarder-tag`](https://github.com/elastic/elastic-serverless-forwarder/tags):
The above examples show the forwarder being updated from `lambda-v1.19.0` to `lambda-v1.20.1`.
620
+
The above examples show the forwarder being updated from `lambda-v1.19.0` to `lambda-v1.21.0`.
621
621
::::
622
622
623
623
@@ -627,11 +627,11 @@ The above examples show the forwarder being updated from `lambda-v1.19.0` to `la
627
627
If you want to change the configuration of a published Elastic Serverless Forwarder without changing its version, you can update the `publish-config.yaml` and run the script again using the **same** `forwarder-tag`:
The above example shows an existing `lambda-v1.20.1` configuration being updated without changing version.
634
+
The above example shows an existing `lambda-v1.21.0` configuration being updated without changing version.
635
635
::::
636
636
637
637
@@ -641,9 +641,9 @@ The above example shows an existing `lambda-v1.20.1` configuration being updated
641
641
If you want to use the publish script for deploying the forwarder with different configurations, create two different `publish-config.yaml` files with unique names and run the publishing script twice, with correct references to the `config-path` and `lambda-name`:
0 commit comments