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
* - update code
* - fast solve build
* - fix tests
* - fix nuget conflicts
* - catch "HttpStatusCode.TooManyRequests" exception
* - save before returns when "TooManyRequests" received
* - include logic to process only N users in one lambda execution
* - refactor code
* - add `GetHttpResponseAsync` func
* - refactor exist code
- update net6 to net8
* - work with users by statuses
* - use `Poly` library for rate limit stategy
- rename `LambdaFunction` to `AdminKycProxyLambda`
* - bugfix with path segment adding
- bugfix with async context working
* - simplify code
- clear users table by status if has changes
* - fix the code
* - try to use `contextFactory` for processing async each status
* - solve work with context
* - simplify code
* - remove useless env variable
* - use prod context connection
* - add logging when call deleting rows
* - use .sln from master branch
* - just fix exist test
- add attributes to mark envs as required
* LambdaFunction.cs - class file containing a class with a single function handler method
5
+
* aws-lambda-tools-defaults.json - default argument settings for use with Visual Studio and command line deployment tools for AWS
6
+
7
+
You may also have a test project depending on the options selected.
8
+
9
+
The generated function handler is a simple method accepting a string argument that returns the json object with the input string. Replace the body of this method, and parameters, to suit your needs.
10
+
11
+
## Here are some steps to follow from Visual Studio:
12
+
13
+
To deploy your function to AWS Lambda, right click the project in Solution Explorer and select *Publish to AWS Lambda*.
14
+
15
+
To view your deployed function open its Function View window by double-clicking the function name shown beneath the AWS Lambda node in the AWS Explorer tree.
16
+
17
+
To perform testing against your deployed function use the Test Invoke tab in the opened Function View window.
18
+
19
+
To configure event sources for your deployed function, for example to have your function invoked when an object is created in an Amazon S3 bucket, use the Event Sources tab in the opened Function View window.
20
+
21
+
To update the runtime configuration of your deployed function use the Configuration tab in the opened Function View window.
22
+
23
+
To view execution logs of invocations of your function use the Logs tab in the opened Function View window.
24
+
25
+
## Here are some steps to follow to get started from the command line:
26
+
27
+
Once you have edited your template and code you can deploy your application using the [Amazon.Lambda.Tools Global Tool](https://github.com/aws/aws-extensions-for-dotnet-cli#aws-lambda-amazonlambdatools) from the command line.
28
+
29
+
#### Amazon.Lambda.Tools
30
+
31
+
Install `Amazon.Lambda.Tools` Global Tools if not already installed.
32
+
```
33
+
dotnet tool install -g Amazon.Lambda.Tools
34
+
```
35
+
36
+
If already installed check if new version is available.
37
+
```bash
38
+
dotnet tool update -g Amazon.Lambda.Tools
39
+
```
40
+
41
+
#### Amazon.Lambda.TestTool-8.0
42
+
43
+
Install `Amazon.Lambda.TestTool-8.0` Global Tools if not already installed.
44
+
```
45
+
dotnet tool install -g Amazon.Lambda.TestTool-8.0
46
+
```
47
+
48
+
If already installed check if new version is available.
0 commit comments