Release v1.20.1 (#904)

Update the ESF version to trigger the release of v1.20.1. Also, update examples in docs and the CHANGELOG file.

This release only contains docs updates. The most important is a fix for a 404 on the `README-AWS.md` file, used as the SAR (Serverless Application Repository) content on the AWS console.

Author: zmoog

CHANGELOG.md

@@ -1,8 +1,13 @@
+### v1.20.1 - 2025/05/23
+##### Docs
+* Fix 404 link in README-AWS.md [903](https://github.com/elastic/elastic-serverless-forwarder/pull/903)
+* Add note about Python 3.12 for Terraform users [901](https://github.com/elastic/elastic-serverless-forwarder/pull/901)
+
 ### v1.20.0 - 2025/05/22
 ##### Features
 * Use Python runtime 3.12 [874](https://github.com/elastic/elastic-serverless-forwarder/pull/874)
 
-Note for Terraform users: to deploy the forwarder from Terraform, you need to pull the latest version of the [`esf-terraform` repository](https://github.com/elastic/terraform-elastic-esf) repository, or use at least the repository version [v1.1.0](https://github.com/elastic/terraform-elastic-esf/releases/tag/v1.1.0).
+Note for Terraform users: to deploy ESF 1.20.0+ from Terraform, you need to pull the latest version of the [`esf-terraform`](https://github.com/elastic/terraform-elastic-esf) repository, or use at least the repository version [v1.1.0](https://github.com/elastic/terraform-elastic-esf/releases/tag/v1.1.0).
 
 ##### Bug fixes
 * logstash shipper does not clear event buffer after sending data [880](https://github.com/elastic/elastic-serverless-forwarder/pull/880)

docs/reference/aws-deploy-elastic-serverless-forwarder.md

@@ -566,7 +566,7 @@ continuing-queue:
 
 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).
 
-Download the [`publish_lambda.sh` script](https://raw.github.com/elastic/elastic-serverless-forwarder/lambda-v1.20.0/publish_lambda.sh) and follow the instructions below.
+Download the [`publish_lambda.sh` script](https://raw.github.com/elastic/elastic-serverless-forwarder/lambda-v1.20.1/publish_lambda.sh) and follow the instructions below.
 
 
 #### Script arguments [_script_arguments]
@@ -604,7 +604,7 @@ $ pip3 install awscli aws-sam-cli ruamel.yaml
 Assuming `publish-config.yaml` in saved in the same directory you intend to run `publish_lambda.sh` from, here’s an example:
 
 ```bash
-$ ./publish_lambda.sh publish-config.yaml forwarder-lambda lambda-v1.20.0 s3-lambda-artifact-bucket-name eu-central-1
+$ ./publish_lambda.sh publish-config.yaml forwarder-lambda lambda-v1.20.1 s3-lambda-artifact-bucket-name eu-central-1
 ```
 
 
@@ -613,11 +613,11 @@ $ ./publish_lambda.sh publish-config.yaml forwarder-lambda lambda-v1.20.0 s3-lam
 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):
 
 ```bash
-$ ./publish_lambda.sh publish-config.yaml forwarder-lambda lambda-v1.20.0 s3-lambda-artifact-bucket-name eu-central-1
+$ ./publish_lambda.sh publish-config.yaml forwarder-lambda lambda-v1.20.1 s3-lambda-artifact-bucket-name eu-central-1
 ```
 
 ::::{note}
-The above examples show the forwarder being updated from `lambda-v1.19.0` to `lambda-v1.20.0`.
+The above examples show the forwarder being updated from `lambda-v1.19.0` to `lambda-v1.20.1`.
 ::::
 
 
@@ -627,11 +627,11 @@ The above examples show the forwarder being updated from `lambda-v1.19.0` to `la
 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`:
 
 ```bash
-$ ./publish_lambda.sh publish-config.yaml forwarder-lambda lambda-v1.20.0 s3-lambda-artifact-bucket-name eu-central-1
+$ ./publish_lambda.sh publish-config.yaml forwarder-lambda lambda-v1.20.1 s3-lambda-artifact-bucket-name eu-central-1
 ```
 
 ::::{note}
-The above example shows an existing `lambda-v1.20.0` configuration being updated without changing version.
+The above example shows an existing `lambda-v1.20.1` configuration being updated without changing version.
 ::::
 
 
@@ -641,9 +641,9 @@ The above example shows an existing `lambda-v1.20.0` configuration being updated
 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`:
 
 ```bash
-$ ./publish_lambda.sh publish-config-for-first-lambda.yaml first-lambda lambda-v1.20.0 s3-lambda-artifact-bucket-name eu-central-1
+$ ./publish_lambda.sh publish-config-for-first-lambda.yaml first-lambda lambda-v1.20.1 s3-lambda-artifact-bucket-name eu-central-1
 
-$ ./publish_lambda.sh publish-config-for-second-lambda.yaml second-lambda lambda-v1.20.0 ss3-lambda-artifact-bucket-name eu-central-1
+$ ./publish_lambda.sh publish-config-for-second-lambda.yaml second-lambda lambda-v1.20.1 ss3-lambda-artifact-bucket-name eu-central-1
 ```
 
 ::::{note}

share/version.py

@@ -2,4 +2,4 @@
 # or more contributor license agreements. Licensed under the Elastic License 2.0;
 # you may not use this file except in compliance with the Elastic License 2.0.
 
-version = "1.20.0"
+version = "1.20.1"