-
-
Notifications
You must be signed in to change notification settings - Fork 446
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
S3 bucket should have etag header exposed #485
Comments
Oh that's interesting. What file size did you try? I'd like to test it to verify the fix. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Just found that any half decent sized file for upload will fail, because amplify storage falls over if the s3 bucket does not have the etag exposed.
Simple fix to the CORS setup... in yml:
The text was updated successfully, but these errors were encountered: