From 58d1cfa354253c97dc1c06146e0eb43d4cbc8f7f Mon Sep 17 00:00:00 2001
From: kaiyan-sheng <kaiyan.sheng@elastic.co>
Date: Wed, 21 Aug 2024 08:28:03 -0600
Subject: [PATCH] Update doc about deploying ESF using SAR AWS console (#767)

This PR is to update the doc about the limitation of deploying ESF using SAR AWS console: one deployment per region.
This PR also sets mypy == 1.10.1 and types-requests<2.31.0.7 as a workaround for fixing CI.
---
 docs/en/aws-deploy-elastic-serverless-forwarder.asciidoc | 7 ++++++-
 requirements-lint.txt                                    | 2 +-
 requirements-tests.txt                                   | 1 +
 3 files changed, 8 insertions(+), 2 deletions(-)

diff --git a/docs/en/aws-deploy-elastic-serverless-forwarder.asciidoc b/docs/en/aws-deploy-elastic-serverless-forwarder.asciidoc
index f16e75b0..cbcd100b 100644
--- a/docs/en/aws-deploy-elastic-serverless-forwarder.asciidoc
+++ b/docs/en/aws-deploy-elastic-serverless-forwarder.asciidoc
@@ -325,6 +325,8 @@ NOTE: To deploy the forwarder directly without using SAR, refer to <<aws-serverl
 [[aws-serverless-forwarder-deploy-console]]
 === Deploy using {aws} Console
 
+NOTE: Only one deployment per region is allowed when using the {aws} console directly. 
+
 . Log in to {aws} console and open **Lambda**.
 . Click **Applications** and then **Create application**.
 . Click **Serverless application** and search for **elastic-serverless-forwarder**.
@@ -333,7 +335,10 @@ NOTE: To deploy the forwarder directly without using SAR, refer to <<aws-serverl
 [role="screenshot"]
 image::images/aws-serverless-forwarder-create-function.png[Create Elastic Serverless Forwarder Lambda function within SAR]
 +
-. Complete the **Application settings** according to <<aws-serverless-forwarder-define-deploy-parameters>>.
+. Complete the **Application settings** according to <<aws-serverless-forwarder-define-deploy-parameters>>. 
+You must specify the parameters even if they already exist in the `config.yaml` file. Depends on the input type, at least
+one if the parameters `ElasticServerlessForwarderSQSEvents`, `ElasticServerlessForwarderS3SQSEvents`, 
+`ElasticServerlessForwarderKinesisEvents`, `ElasticServerlessForwarderCloudWatchLogsEvents` should de defined.
 . After your settings have been added, click **Deploy**.
 . On the Applications page for **serverlessrepo-elastic-serverless-forwarder**, click **Deployments**.
 . Refresh the **Deployment history** until you see the `Create complete` status update. It should take around 5 minutes to deploy &mdash; if the deployment fails for any reason, the create events will be rolled back and you will be able to see an explanation for which event failed.
diff --git a/requirements-lint.txt b/requirements-lint.txt
index fbb48230..d0385b65 100644
--- a/requirements-lint.txt
+++ b/requirements-lint.txt
@@ -2,7 +2,7 @@ black
 flake8
 flake8-per-file-ignores
 isort
-mypy
+mypy==1.10.1
 types-PyYAML
 types-mock
 pyflakes>=3.0.0,<3.3.0
diff --git a/requirements-tests.txt b/requirements-tests.txt
index 9f3a87cd..7daa5b72 100644
--- a/requirements-tests.txt
+++ b/requirements-tests.txt
@@ -9,5 +9,6 @@ pysimdjson==5.0.2
 python-rapidjson==1.14
 cysimdjson==23.8
 responses==0.24.1
+types-requests<2.31.0.7
 testcontainers==3.7.1
 pyOpenSSL==24.0.0