-
Notifications
You must be signed in to change notification settings - Fork 400
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error with agent version 9.12.1 and aws-sdk version 3.266.1 #1549
Comments
@atodd sorry for the troubles. Do you mind posting a reproduction case please? |
Our production code broke with same error and after debugging for 2 days when we removed new relic key from env vars everything worked fine |
@bizob2828 the steps to reproduce in nodejs |
@ahmednaser94 and @atodd I was able to triage and provide a fix. This will go out next week as 9.13.0. In the meantime you can pin newrelic to 9.11.0. If you're using 3.290.0+ you will need to pin [email protected] but install @newrelic/[email protected] separately. |
@bizob2828 Thank you for the quick response and fix! |
@atodd this has been released in 9.13.0 of the agent. Please upgrade and let me know how it goes |
I'm using the serverless-newrelic-lambda-layers and I'm facing the same problem when I'm trying to get the pre-signed URL to download some file And this is happening because of this Is this related to this thread? |
@marcoswca The issue you're having is related to this thread. What's the layer ARN your function's using? If it's less than the latest, you can update that in the AWS Lambda console. (Latest layer versions can be found here: https://layers.newrelic-external.com/) |
@mrickard This is happening with the latest layer (version 19). I updated to use version 18 and it's working now. Thank you! |
@marcoswca That's interesting--it's the opposite of what I'd expect. What's the full ARN you're using? Node 18 version 18 contains 9.12.1, which we're aware has this conflict with AWS SDK. |
Hey @bizob2828 @mrickard , currently facing the same issue: Currently we are using latest v3 aws-sdk @ 3.299.0 and newrelic @ 9.14.1 . And node version 18.12.1 As you can see in the screenshot it's happening because of this value. When we disable newrelic, preSignedURL is working fine with value of x-Amz-SignedHeaders as host Is this related to this issue ? |
@pawanakhilMM @marcoswca would either of you be able to provide a repro case or code snippet so we're able to investigate the issues you're having? Particularly interested in how you're generating the presigned urls, as I believe there's a couple different ways to do that. |
@jmartin4563 Here is the code snippet.
|
@pawanakhilMM thank you so much! i'll start digging into this |
@pawanakhilMM I've confirmed the issue you and @marcoswca are seeing with Presigned URLs, since this is a separate issue from this current thread, I've opened up newrelic/node-newrelic-aws-sdk#176 to keep things clean/separate, and will do my investigation/fixes off that issue. Thank you again for the report, closing this issue in lieu of newrelic/node-newrelic-aws-sdk#176 |
Description
The latest release of this agent is causing issues with aws-sdk:
Expected Behavior
Troubleshooting or NR Diag results
Steps to Reproduce
Your Environment
Node version: 18.12.1
New Relic version: 9.12.1
AWS SDK version: 9.266.1
Additional context
The text was updated successfully, but these errors were encountered: