You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, @wiewiur667 👋 and thank you for opening this issue. I've marked it as a feature request at this time because we do not currently support passing ChecksumAlgorithm while calling the Storage.put() API. I'll review this with the team internally and provide updates on any progress as it's made.
@cwomack Any news from the team on this? I'm currently using Storage.put in our React Native app for image upload, and sometimes corrupted images make it through. The ability to pass a pre-calculated checksum is something we'd love to try.
cwomack
changed the title
Generate CheckSum while uploading object using Storage category
Allow options for generating CheckSum while uploading object using Storage category (i.e. CRC-32, SHA-256, etc.)
Aug 7, 2024
@muvashi and @tlmader, we just released the Storage Browser connected component within the Amplify UI library that will support crc32 checksum. Also, the uploadData API in v6 of Amplify will support checksumAlgorithm: 'crc-32' as an option (not documented, but we'll get that updated).
Can you let us know if the two of these updates are sufficient for your use cases? Thanks.
Is this related to a new or existing framework?
Angular, React, React Native, Vue, Web Components, Next.js
Is this related to a new or existing API?
Storage
Is this related to another service?
No response
Describe the feature you'd like to request
When using S3 PubObjectCommand API, we can specify the CheckSumAlgorithm which generate the checksum in S3 that can be used later.
However, there is no option to generate the checksum via Amplify storage API call.
Describe the solution you'd like
Option to pass ChecksumAlgorithm while using Storage.put() API call.
Describe alternatives you've considered
.
Additional context
No response
Is this something that you'd be interested in working on?
The text was updated successfully, but these errors were encountered: