Unanswered Questions tagged with AWS Amplify

Content language: English

Sort by most recent

Browse through the questions and answers listed below or filter and sort to narrow down your results.

Multipart upload with aws S3 + checksums

I am trying to implement browser multipart upload to a S3 bucket. I should be able to pause and play the upload and also I'll like to automatically generate the checksums as I'm uploading. I have tried several approaches and I've been hitting a wall. Some of the approaches I've tried. * Using the amplify S3 upload, this works well, but has the caveat that I can't generate the checksums automatically, to generate the checksums, I run a lambda function after file upload, the caveat is for large files, the lambda function times out. Also, I'll like to avoid going this route as I believe It's quite computationally expensive. * Using https://blog.logrocket.com/multipart-uploads-s3-node-js-react/. This is also similar to the above, the caveat is when I add the checksum algorithm to the upload part query, I get a **checksum type mismatch occurred, expected checksum type sha256, actual checksum type: null site:stackoverflow.com s3**. After a lot of googling, I'm not sure I can compute the checksums using presigned url. * and the current approach is to do away with the presigned url and send the chunked data to the lambda functions which then sends to the bucket. Since I'm managing everything with amplify, I run into some problems with API gateway(multipart/form-data). I have set the gateway to accept binary data and followed other fixes I found online but I’m stuck on **execution failed due to configuration error unable to transform request**. How do I fix the above error and what will be the ideal approach to implement the functionalities(multipart file upload to support resumable uploads and checksum computation)
0
answers
0
votes
21
views
asked 18 days ago

Can not call HTTP API with Custom domain which provided by Google Domain

I'm going to connect HTTP API to my domain and use it. My domain is ***.art and I'm using it from Google. First, I connected CNAME to connect to AWS Amplify. Below is a captured copy of the Admin tab for the Amplify domain and the DNS settings status for the Google domain. ![Enter image description here](/media/postImages/original/IMB_v0nABCQlCCYiDg12-d2w) ![Enter image description here](/media/postImages/original/IMFAxZpx67SJuQywDFZY_7kQ) Subsequently, we created an HTTP API and verified calls through that URL.![Enter image description here](/media/postImages/original/IMvwgkwY8cT26mAvQkxWUziQ) The path and CORS settings of the API are shown in the screenshot below. ![Enter image description here](/media/postImages/original/IMgV_fMCrZTCmDIGUNWS_OYg)![Enter image description here](/media/postImages/original/IMiNitf33iQamWTYY5xe6QPQ) And the settings for the custom domain are as follows. ![Enter image description here](/media/postImages/original/IMbAtfy-xzStmVm9fP81rLBg) ![Enter image description here](/media/postImages/original/IMDBwuYv4gSV2Ro_3u-Yhz3A) Finally, the certificate and the DNS setting of the Google domain to which it was applied are as follows. ![Enter image description here](/media/postImages/original/IM6kXCEe7ZRiKUxDoIX4hkyA) ![Enter image description here](/media/postImages/original/IMSm3e45NJTMCJZW9Khrwvyw) I would appreciate it if you could tell me which part went wrong. The following is an error response when Chrome accessed the HTTP API address through my custom domain. ![Enter image description here](/media/postImages/original/IMWg1T0EeAQq-SgV5FTYm_dA) ![Enter image description here](/media/postImages/original/IM-KMgzjgITX-I3u_N-Lr5JQ)
0
answers
0
votes
23
views
asked a month ago