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.

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

Update doc about deploying ESF using SAR AWS console #767

Merged
merged 8 commits into from
Aug 21, 2024
Merged
Show file tree
Hide file tree
Changes from 3 commits
Commits
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: 4 additions & 1 deletion docs/en/aws-deploy-elastic-serverless-forwarder.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -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**.
Expand All @@ -333,7 +335,8 @@ 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>>.
Please specify the parameters even if they already exist in the `config.yaml` file.
kaiyan-sheng marked this conversation as resolved.
Show resolved Hide resolved
. 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.
Expand Down
1 change: 1 addition & 0 deletions requirements-tests.txt
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,7 @@ ujson==5.9.0
pysimdjson==5.0.2
python-rapidjson==1.14
cysimdjson==23.8
urllib3==1.26.18
responses==0.24.1
testcontainers==3.7.1
pyOpenSSL==24.0.0
Loading