Skip to content
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

Support for AWS SDK for JavaScript v3 #294

Closed
coder17934 opened this issue May 12, 2020 · 13 comments
Closed

Support for AWS SDK for JavaScript v3 #294

coder17934 opened this issue May 12, 2020 · 13 comments

Comments

@coder17934
Copy link

Is there a branch parked somewhere with support for the new JavaScript AWS SDK? The new SDK uses middleware to intercept and transform requests/responses, which is a bit different to how the xray-sdk hooks into the 2.x version. If not, happy to get started and send a PR, just thought I would check beforehand.

Thanks!

@willarmiros
Copy link
Contributor

Hi @Anvar,
We are not yet developing support for AWS SDK for JS v3. We'd be open to a pull request if you're interested. The only caveats are that we'd like to keep dependencies to an absolute minimum, although that shouldn't be an issue with v3's modular design. We'll also need to discuss with the AWS SDK team about the stability of the middleware APIs before we can mainline our own middleware, since they are still in beta.

Otherwise, contribute away!

@coder17934
Copy link
Author

Great, thank you, I will have a look!

@trivikr
Copy link
Member

trivikr commented Dec 22, 2020

Update: The general availability of the AWS SDK for JavaScript, version 3 (v3) was announced on December 15th, 2020.

This was referenced Dec 31, 2020
@awssandra
Copy link
Contributor

Reviewing pull request in flight.

monken added a commit to emdgroup/aws-xray-sdk-node that referenced this issue Mar 8, 2021
monken added a commit to emdgroup/aws-xray-sdk-node that referenced this issue Mar 8, 2021
willarmiros pushed a commit that referenced this issue Mar 22, 2021
* refs #294, add support for AWS SDK v3

* make test-d happy

* #refs #294, add documentation and export for captureAWSv3Client

* fix undefined err.$metadata

* replace signingName with serviceId

* update package-lock.json

* expect new segment to be created with proper serviceId
@bfaulk96
Copy link

bfaulk96 commented Apr 1, 2021

Hey all, I noticed #386 got merged, but it seems I still get the TypeError: service.customizeRequests is not a function error when trying to capture the Dynamo Document Client from the sdk v3... Any updates?

@willarmiros
Copy link
Contributor

@bfaulk96 see #395

@willarmiros
Copy link
Contributor

Released in 3.3.0!

@willarmiros
Copy link
Contributor

Reopening because we had to temporarily rollback AWS SDK V3 support in patch release v3.3.1 to address #411. We are actively working on another patch that will add back AWS SDK v3 support in 3.3.2.

@bfaulk96
Copy link

Any updates on this being re-implemented?

@awssandra
Copy link
Contributor

We are actively addressing this to re-release. Stay tuned!

@jwoehrle
Copy link

I've tested some of my code with 3.3.3... works now as expected 🎉

Thank you!

@willarmiros
Copy link
Contributor

willarmiros commented May 14, 2021

As @jwoehrle said, AWS SDK v3 support is here to stay as of v3.3.3. Closing this out.

@andres-sinapsis
Copy link

I'm running "aws-xray-sdk-core": "3.4.1" with "@aws-sdk/*": "^3.282.0", and I doesn't seem to be stable yet. For instance using DynamoDB:
const client = new DynamoDBClient({}); AwsXRay.captureAWSv3Client(client);
I got typescript error about incompatibility between the packages because of the middleware. If a use as any apparently x-ray can't record the table name and I am only seeing in the graph a single node called "DynamoDB" instead of the individual tables. This same behavior is happening with S3 for instance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants