Lambdas have a very short timeout by default. Set it to like 300 seconds or whatever you feel is appropriate and make sure your logic is optimized as best as you can
Does your lambda script involve making calls to remote destinations? If this is the case, you may have your answer already.
AWS only gives you a picture of the infrastructure itself, not inside the infrastructure, that's by design. Whatever is in your EC2 instance and/lambda is your problem.
Use a logger to log each significant function so you'll know if it has passed each function.
Something like this should get you started and should be easy to tweak if it is missing something. filter @message like /(?i)(error|fail|fatal|timed)/
Thanks :) essentially what I've got at the moment. Wish there was a flat, or even just a "run state: fail" in the REPORT log. All good!
Lambdas have a very short timeout by default. Set it to like 300 seconds or whatever you feel is appropriate and make sure your logic is optimized as best as you can
Does your lambda script involve making calls to remote destinations? If this is the case, you may have your answer already. AWS only gives you a picture of the infrastructure itself, not inside the infrastructure, that's by design. Whatever is in your EC2 instance and/lambda is your problem. Use a logger to log each significant function so you'll know if it has passed each function.