You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to use Bugsnag to diagnose issues with my AWS Lambda Function which runs ruby code. I use the Serverless framework to deploy my function, which runs on a cron timer every 15 minutes.
Unfortunately when I include this library, the function fails to run. Here is the relevant log line from CloudWatch logs:
Does the Bugsnag gem require concurrent-ruby as a runtime dependency? If that dependency could be eliminated, the gem could be used by default in an AWS lambda context. In the meantime, I will pursue the workaround of building a Docker container on top of the AWS base image for Lambda.
For reference, here are the relevant parts of my serverless.yml file
Hi @gburgett - concurrent-ruby is currently a runtime dependency. We do have an item on our backlog already to look at official support for AWS Lambdas with Ruby in the future - I'll make sure we keep this thread updated on that 👍
Hello,
I am trying to use Bugsnag to diagnose issues with my AWS Lambda Function which runs ruby code. I use the Serverless framework to deploy my function, which runs on a cron timer every 15 minutes.
Unfortunately when I include this library, the function fails to run. Here is the relevant log line from CloudWatch logs:
I believe this is because the
bugsnag
gem depends onconcurrent-ruby
, which includes native C code that must be compiled. The AWS Lambda Runtime does not handle native code by default, it must be packaged into a docker file.Does the Bugsnag gem require
concurrent-ruby
as a runtime dependency? If that dependency could be eliminated, the gem could be used by default in an AWS lambda context. In the meantime, I will pursue the workaround of building a Docker container on top of the AWS base image for Lambda.For reference, here are the relevant parts of my
serverless.yml
fileThe text was updated successfully, but these errors were encountered: