aws-lambda-provided doesnt work

[misogihagi]

related to #455

I used amazon/aws-lambda-provided:al2 instead lambci/lambda:provided
then
curl -XPOST "http://localhost:9000/2015-03-31/functions/function/invocations" -d '{"key":"hello"}'

responded nothing.

Deployed my function works well but offline docker version doesn't work.

how should I make it closer to running AWS lambda?

[calavera]

👋 hi @misogihagi we're going to need a little bit more information about your code. Do you get any compilation error?
Without more information, or a way to reproduce it, we cannot help you.

[misogihagi]

pulling my code,

git clone https://github.com/misogihagi/lambda-test.git
cd lambda-test

building,

sudo docker run --rm \
    -v ${PWD}:/code \
    -v ${HOME}/.cargo/registry:/root/.cargo/registry \
    -v ${HOME}/.cargo/git:/root/.cargo/git \
    rustserverless/lambda-rust

and running

sudo unzip -o \
    target/lambda/release/lambda-test.zip \
    -d /tmp/lambda && \
sudo  docker run \
    -p 9000:8080 \
    -v /tmp/lambda:/var/task \
    amazon/aws-lambda-provided:al2

then

curl -XPOST "http://localhost:9000/2015-03-31/functions/function/invocations" -d '{"key":"hello"}' 

reproducing above.

[calavera]

@misogihagi I'm not familiar with that docker image, but for what you post, I think you need to modify the function path in the curl request with the name of your binary:

curl -XPOST "http://localhost:9000/2015-03-31/functions/YOUR-BINARY-NAME/invocations" -d '{"key":"hello"}' 

@seanpianka that's unrelated.

[misogihagi]

It looks irrelevant...

curl -XPOST "http://localhost:9000/2015-03-31/functions/lambda-test/invocations" -d '{"key":"hello"}' 

returned
404 page not found

how can I test offline...

[calavera]

My recommendation is to use cargo-lambda. You don't need docker, and I know it works, because I wrote it, and I just tested it with your repository 🤣

This is how you use it for you test repository:

1: Install

cargo install cargo-lambda

2: In the root of your repository, start the server in one terminal with:

cargo lambda watch

3: Send invoke requests from another terminal:

cargo lambda invoke --data-ascii '{"firstName": "David"}'

[bnusunny]

@misogihagi You should mount the custom runtime bootstrap under /var/runtime directory inside the container.

sudo  docker run \
    -p 9000:8080 \
    -v /tmp/lambda:/var/runtime \
    amazon/aws-lambda-provided:al2

[misogihagi]

@calavera
thanks to advice!
cargo-lambda cannot be installed though..

error: `MaybeUninit::<T>::assume_init` is not yet stable as a const fn
   --> /home/user/.cargo/registry/src/github.jparrowsec.cn-1ecc6299db9ec823/kstring-2.0.0/src/string.rs:844:17
    |
844 |                 std::mem::MaybeUninit::uninit().assume_init()
    |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

error: could not compile `kstring` due to previous error
warning: build failed, waiting for other jobs to finish...
error: failed to compile `cargo-lambda v0.6.0`, intermediate artifacts can be found at `/tmp/cargo-installRi8vo2`

Caused by:
  build failed

@bnusunny
Yes!
what you said hit a bullseye!
Thanks!

[davidbarsky]

@misogihagi assume_init was made const in 1.59 (https://doc.rust-lang.org/stable/std/mem/union.MaybeUninit.html#method.assume_init). While that version of Rust was released 7 weeks ago, I suggest updating every 6 weeks if you can—the current stable version of Rust is 1.60.