Amplify Storage uploads objects to S3 at a reduced size

[buildforprod]

Before opening, please confirm:

• I have checked to see if my question is addressed in the FAQ.
• I have searched for duplicate or closed issues.
• I have read the guide for submitting questions.
• I have removed any sensitive information from my code snippets and submission.

App Id

d21kc3ho29wsqv

AWS Region

us-east-1

Amplify Hosting feature

Not Applicable

Question

I'm observing that objects uploaded to S3 using Amplify Storage are stored at a reduced size! The code for uploading the objects is working fine when tested outside of Amplify.

The code used in React:

const [files, setFiles] = useState([]);
const handleDrop = async (e) => {
        e.preventDefault();
        const newFiles = [...files];
        for (let i = 0; i < e.dataTransfer.files.length; i++) {
            const file = e.dataTransfer.files[i];
            newFiles.push({ key: file.name, file });
        }
        setFiles(newFiles);
    };

const handleUpload = async () => {
        for (const file of files) {
            const result = await Storage.put(`${city}/${resource}/${file.key}`, file, {
                contentType: file.file.type, });
        }
    };

[Jay2113]

Hi @buildforprod 👋 , thanks for reaching out. Since the issue seems related to the Amplify Storage category/library, I am going to transfer this over to the amplify-js repository for better assistance.

[nadetastic]

HI @buildforprod I'm currently investigating this and will follow up soon. In the meantime let me know if there have been any updates or additional context to provide.

[nadetastic]

Hi @buildforprod following up here - this isn't something that the library is doing after doing some investigation. As seen on this thread, this can be the result of s3 not working like a traditional filesystem and rather uses a key and prefix patterns for storage and all permission related information and metadata is controlled at the bucket level along with AWS IAM which is Identity and Access Management system. Hence, we observe this difference in object size.

[cwomack]

@buildforprod, wanted to check in and see if you're still experiencing this issue. Let us know if you got a chance to review the comment above and have any additional questions. Thanks!

[cwomack]

Closing this issue as we have not heard back from you. If you are still experiencing this, please feel free to reply back and provide any information previously requested and we'd be happy to re-open the issue.

Thank you!