Using aws-sdk v3 instead of v2 as dependency.

[ajay47]

Currently this package uses aws-sdk v2 as dependency. Can you please look into the possibility of migrating over to v3. This will save a lot of space. The v3 is modular in nature and it will be beneficial for us to use @aws-sdk/client-cloudwatch-logs instead of v2 which imports all AWS service functions.
Please let me know if this is possible or maybe it can be scoped as part of Version 4 ? I am ready to help if you need any.
Thanks

[zendagin]

What a coincidence, I was going to raise this issue too. Yesterday, I just forked and modified for aws-sdk v3 for my own usage. You may take it as a reference. zendagin@a394491

It seems that support of v3 was considered in #144 (comment) but finally gave up. I think the point of easy migration is using v2 compatible style and use NodeHttpHandler to config proxy. (Well I spent some time to figure out the proxy config)

Edit: err.code is renamed to err.name in v3, so it seems that it is not fully compatible

[sagilevanon]

Much needed! All our code is based on v3 and adding the v2 is really bloating our bundle.

[lazywithclass]

Hello, sorry for the late reply, I have little to no time now to address issues, if you would like to submit PRs I am very open to review and merge.

EDIT: Is #172 addressing your needs?

[lazywithclass]

@dicky1126277766238 did you end up with some changes you'd feel comfortable to share as a PR here? I won't have time to do such a change.

[sagilevanon]

Hi @lazywithclass - will you be able to merge #172 any time soon?
Having the whole aws-sdk is really bloating our package.

[lazywithclass]

winston-cloudwatch@3.2.0 is out with this #172 merged, sorry for being so late I am full of work and uni studies.