Lambda Architecture vs. Container Architecture

ACM.300 Resolving errors caused by architecture mismatch

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

⚙️ Check out my series on Automating Cybersecurity Metrics | Code.

🔒 Related Stories: Lambda | Container Security | Application Security

💻 Free Content on Jobs in Cybersecurity | ✉️ Sign up for the Email List

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

In the last post I showed you how to enable CloudWatch logging for Lambda.

Testing a Lambda function with the AWS Console and Enabling CloudWatch Logs and Metrics

In the process I got the following error:

"errorType*: "Runtime.InvalidEntrypoint,
"errorMessage": "Requestld: [id] Error: fork/exec /entry.sh: exec format error"

What’s that all about? I’m going to tell your up front that I think this error could be better. It seems like when running the Lambda AWS could determine the problem and present a better error message, but I figured it out based on the pain others have faced.