- Newest
- Most votes
- Most comments
Hi, I wouldn't be able to comment on your third-party tool without much information regarding it. However, I would recommend looking at using native S3 client-side encryption. You can encrypt and decrypt at client-side using Amazon S3 Encryption Client, and coding in your preferred language.
If above is not possible, I would recommend calculating checksum for your objects and provide that checksum algorithm and precalculated value before the upload. When S3 receives the object, it calculates the checksum by using the algorithm that you specified. If the two checksum values don't match, Amazon S3 generates an error. This way, you could possibly avoid file corruption issues ensuring integrity through checksum.
https://docs.aws.amazon.com/AmazonS3/latest/userguide/checking-object-integrity.html
You may also use the following method adding Content-MD5 value as request header when uploading to S3.
Relevant content
- asked 9 months ago
- asked 15 days ago
AWS OFFICIALUpdated 8 months ago- AWS OFFICIALUpdated 4 months ago
Hello, thank you for your reply. the files i have are binary files which are being edited and saved as .bin but the third-party tool is a mix of hardware and software that encrypts the file and then saves it with other extensions to make it useable by also the companies software. I am not that good at coding to use S3 client-side encryption. As for the second option you suggested, I have the SHA-1 but how can i have S3 calculate the checksum using it? also you mentionned that if the checksum keys don't match S3 will generate an error. i need to make sure the file is uploaded from the first time and not becomming corrupted as this is a SAAS project and sending corrupted files is bad.