aws-sdk-js-v3 VS aws-sdk-js

From this GitHub issue and this one from 2021 it seems like AWS just doesn't care about this - so, asking here if anyone knows of a workaround (other than "just keep using v2"... that's not a long-term solution), or if any AWS devs can shed some light on the situation.

First class typescript support, but everything is possibly undefined?

I published "ts-dynamodb-attributes-transformer" that transforms the TypsScript object to Amazon DynamoDB attributes (precisely, this attributes type is Record that is defined at aws-sdk-js-v3).

Once we have verified the presence of the AWS_WEB_IDENTITY_TOKEN_FILE and AWS_ROLE_ARN environment variables, our pod is ready to connect to and read from S3. The following Typescript snippet illustrates a simple example which fetches the names of all the S3 buckets in our account. It uses the AWS SDK for JavaScript V3

If you'd like the Amazon JavaScript SDK to support Deno then make your support known on this thread:

https://github.com/aws/aws-sdk-js-v3/issues/1289

I really suggest checking out the repo and especially the Upgrading section for more details.

No CloudFront URL signing - how can v3 SDK be labeled as general release if it doesn't have feature parity with the v2 SDK?

⚠️Here's the issue: https://github.com/aws/aws-sdk-js/issues/4519

The updates could be parsed from the github repo's CHANGELOG files (ex: javascript, java, python). I'm picturing an RSS feed generated for a specific language and module (ex: python s3, javascript s3, java sqs)

Another option is to look at the changelog for the AWS SDK. Because the AWS SDK has to have support for pretty much every service ever it gets a new version and a changelog whenever new things are added. I like to refer to this changelog from time to time: https://github.com/aws/aws-sdk-js/blob/master/CHANGELOG.md

From this thread I double-checked that all query strings and the origin, Access-Control-Request-Method and Access-Control-Request-Headers are sent to the origin (I ran into some signature mismatch issues before that were solved with this origin request policy).

Now that you have installed MinIO server, let's use it on your project. I will be using the official S3 JavaScript SDK as example. But should be applicable for all other S3 SDKs.

The client is only available for Java and Python. https://github.com/aws/aws-sdk-js/issues/1164

The best way I've found to locate the X-Amz-Target value is from this AWS support ticket where it is recommend to look at the SDK docs for the service and locate the targetPrefix field in the metadata.

I wonder if there's a way to only bring in the S3 SDK from aws-sdk to help trim the file size. I believe there might be a way to import only certain files, maybe something like this?

Due to performance reasons, one of the goals was to switch to rollup for bundling all our applications, however, we use webpack due to rollup’s known issues with aws-sdk.