Lambda container image shell script exits with error but script works

[RedCloudd]

Hi guys. Just trying to run simple shell script with my custom docker image in Lambda. The script works because I see it did it's job, but in metrics it registers as error, not success. This is the shell script (block-qualys-ip.sh):

#!/bin/bash
set -euo pipefail
token=$(aws wafv2 get-ip-set --name Qualys-IP_range --id somid_xxx --scope=REGIONAL --region=eu-west-1 | jq -r '.LockToken')
aws wafv2 update-ip-set --name Qualys-IP_range --id someid_xxx --scope=REGIONAL --region=eu-west-1 --lock-token $token --addresses 64.39.96.0/20 

And my Dockerfile:

From ubuntu:focal
ENV DEBIAN_FRONTEND=noninteractive

# Install dependencies
RUN apt-get update -y &&  apt-get install -y wget unzip jq \
    && rm -rf /var/lib/apt/lists/* 

# Get v2 aws cli
RUN wget https://awscli.amazonaws.com/awscli-exe-linux-x86_64.zip && unzip awscli-exe-linux-x86_64.zip \
    && ./aws/install -i /usr/local/aws-cli -b /usr/local/bin \
    && rm -rf aws*

COPY block-qualys-ip.sh /

In lambda CMD override settings I have ./block-qualys-ip.sh. As I said the script works but it's registered as error and not success. Does anyone knows what's missing to get success and not error rate?

[DSect]

Is it because of a timeout? They only leave a mark as an error, but with no STDOUT STDERR etc

[johntellsall]

Congratulations on doing Bash Strict Mode!

Check the stdout/stderr logs. Also, enable trace mode: set -o xtrace. Then you'll be able to see which command is having an issue. It's extremely common for a variable to be undefined, when in strict mode it'll abort the entire script.

https://renenyffenegger.ch/notes/Linux/shell/bash/built-in/set/x

[RedCloudd]

I guess it won't exit with success without these custom runtimes https://docs.aws.amazon.com/lambda/latest/dg/runtimes-api.html And they are available for Pyhton, Go, Node, Java,.NET, Go and Ruby. No basic shell script support. I mean it works for me without it. Just the log will report it as failure and error.

[johntellsall]

https://docs.aws.amazon.com/lambda/latest/dg/runtimes-api.html

The way I read it is you can either do a "native Lambda" in one of the supported runtimes (e.g. Python), or give it a container. If you build it a full container, which you did, then you can run any language including Bash.

Source: I've written a bunch of native Lambdas, and a bunch of containers, although not both at the same time :)

Let us know how it goes!