GH-4468: Transfer Acceleration option can now be passed to Storage.put()

[cespin]

Description of changes

Currently, it is not possible to make the Amplify client use the transfer acceleration option of S3.

With this modification the web application would pass an extra parameter to the put and that would attempt to do the upload using transfer acceleration

Issue #, if available

#4468

Description of how you validated changes

Ran the unit tests, checked with the documentation of the AWS S3 client that the parameter is valid.

Checklist

• PR description included
• yarn test passes
• Tests are changed or added
• Relevant documentation is changed or added (and PR referenced)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[codecov-commenter]

Codecov Report

Merging #8750 (617dc0c) into main (fc7f8ab) will increase coverage by 0.01%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main    #8750      +/-   ##
==========================================
+ Coverage   77.79%   77.80%   +0.01%     
==========================================
  Files         240      240              
  Lines       17192    17192              
  Branches     3680     3680              
==========================================
+ Hits        13375    13377       +2     
+ Misses       3692     3690       -2     
  Partials      125      125              

Impacted Files	Coverage Δ
...torage/src/providers/AWSS3ProviderManagedUpload.ts	90.44% <ø> (ø)
...ages/amazon-cognito-identity-js/src/CognitoUser.js	79.37% <100.00%> (ø)
packages/auth/src/Auth.ts	87.21% <100.00%> (ø)
packages/core/src/Platform/version.ts	100.00% <100.00%> (ø)
...kages/amazon-cognito-identity-js/src/BigInteger.js	89.71% <0.00%> (+0.40%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8c9bedd...617dc0c. Read the comment docs.

[jamesaucode]

LGTM :)

[iartemiev]

@jamesaucode when merging PRs, please make sure to squash and merge to a Conventional Commit-style message. For example: feat(@aws-amplify/storage): add transfer acceleration option to Storage.put. This enables our pipelines to correctly version packages and generate changelogs.

[cespin]

Hi @iartemiev / @jamesaucode ,

Thanks for merging this. Much appreciated.

I just upgraded the aws-amplify library in my project to version 4.2.4 which is supposed to include these changes according to the release notes but I don't see them in there when I navigate into the code.

I've downloaded the library several times, seems that the package doesn't match the release notes.

can you help me check if this is the case ?

Thanks,

[cespin]

I can confirm what I said above.

I downloaded the the package from the release page, here

The source code I downloaded doesn't include these changes but the release notes say it does.

[iartemiev]

@cespin, this change has not yet been released. It will be in the next release of aws-amplify. Where are you seeing that this is included in 4.2.4?

[iartemiev]

The change is currently available through our pre-release NPM tag If you want to use it before it goes out in the next release. You can npm install aws-amplify@4.2.5-unstable.1

[cespin]

Thanks for the information @iartemiev

I saw it in this URL after clicking on 2 commits

[iartemiev]

Those are not the commits that are included in the release. That's showing commits that have been merged to the main branch after the release went out.

[cespin]

Thanks for the clarification @iartemiev

[github-actions]

This pull request has been automatically locked since there hasn't been any recent activity after it was closed. Please open a new issue for related bugs.

Looking for a help forum? We recommend joining the Amplify Community Discord server *-help channels or Discussions for those types of questions.