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
AWS uses checksum for uploading files, but another checksum can be added and stored as metadata to be absolutely sure that the data that was supposed to be stored is stored. It's best practice for migrations of data and while you're not doing that here it might be good to have some extra protection.
Enhancement
Checksums can be specified on s3.PutObjectInput
Solution proposal
Either use SHA256 as checksum or CRC32C. Since blobs are keyed by it can be used, but it's a bit less performant than CRC32C.
Use case and current behavior
AWS uses checksum for uploading files, but another checksum can be added and stored as metadata to be absolutely sure that the data that was supposed to be stored is stored. It's best practice for migrations of data and while you're not doing that here it might be good to have some extra protection.
Enhancement
Checksums can be specified on
s3.PutObjectInput
Solution proposal
Either use SHA256 as checksum or CRC32C. Since blobs are keyed by it can be used, but it's a bit less performant than CRC32C.
Additional Information
https://docs.aws.amazon.com/AmazonS3/latest/userguide/checking-object-integrity.html
https://aws.amazon.com/getting-started/hands-on/amazon-s3-with-additional-checksums/?ref=docs_gateway/amazons3/checking-object-integrity.html
The text was updated successfully, but these errors were encountered: