Creating simple hello world lambda that uses AWS Gateway API

First we will create AWS lambda and then configure our app to point to it via Gateway API. 

Create AWS lambda using the following steps:-

Sign in to the Lambda console at https://console.aws.amazon.com/lambda.

1.Choose Create function. For Function name, enter my-function.

2. For all other options, use the default setting.

Choose Create function.

Gateway API

Configuring the API gateway is abit tricky. Goto https://console.aws.amazon.com/apigateway. And the click on "Create API".  




Then select HTTP API and click on "build".

Provide a name, in this case we will call it "my-http-api" and add the required integration to lambda as shown here:-



Then in the route settings, ensure you have setup the followings



In the define "stage", click "Next" and please verify the configuration is ok. Click "Create".

And then to test it out, go to API Gateway -> APIS -> "my-http-api". Then go to Deploy -> Stage and click on the Invoke URL. And you should the the following layout











Comments

Post a Comment

Popular posts from this blog

vllm : Failed to infer device type

Trying to run vllm without gpu will typicaly lands you into this issue. To resolve this issue: we can use set these both. Setting one does not work for me. So i had to configure both settings below:- 1.  environment variable CUDA_VISIBLE_DEVICES = "" 2. in the command line, change to use device cpu and remove  tensor-parallel-size. For example, python3 -m vllm.entrypoints.openai.api_server --port 8080 --model deepseek-ai/DeepSeek-R1 --device cpu --trust-remote-code --max-model-len 4096" References https://docs.vllm.ai/en/latest/getting_started/troubleshooting.html#failed-to-infer-device-type
Read more

NodeJS: Error: spawn EINVAL in window for node version 20.20 and 18.20

Encounter this issue when running autorest (that uses nodejs).  I am using node version:  v18.20.2 After i revert to use node v18.12.0, then i was able to get my app to run without this error. Since i am working with Azure devops yaml, i was able to use the following to resolve my issue.  - task : NodeTool@0   inputs :     versionSource : 'spec'     versionSpec : '18.18.0'
Read more

android studio kotlin source is null error

Image
This org.jetbrains.kotlin.util.FileAnalysisException with a java.lang.IllegalArgumentException: source must not be null is a known issue that can sometimes occur with the Kotlin compiler. It seems to be related to how the compiler analyzes certain source code structures. When this happens, you need to go clean your project and do another rebuild.  For my case, I was trying to test out the databinding = true feature. 
Read more