AWS S3 Presigned URL Upload Tutorial in Python

can you give me an example to make this request from react axio please ?

I couldn't figure out how to do this in Swift, but this video gave me the idea to put the generator on Lambda! Awesome content always.

If you are getting this error: "Requests specifying Server Side Encryption with AWS KMS managed keys require AWS Signature Version 4", you have to configure the signature_version when you instance the client. For Python_:
client(service_name="s3", region_name="us-east-1", config=Config(signature_version="s3v4"))

I was curious who the guy in the photo was (Jeff Goldblum?) but googling mr Hands is not advised 😂

super dope😃 thank you bro

what would the code look like if you are provided a user name, access key ID, secret access key and bucket name instead of you creating it the signed URL?

I am getting a 405 for this. If someone can help me it would be much appreciated

what is aws accesskey id in presigned url payload ? and how do i generate presigned url in lambda python?

How would this work with file input or FileField?

Policy Condition failed: ["eq", "$key"] can anyone tell me how to resolve this error

in my case, it doesn't display the image, it just downloads the image

File uploaded with presigned post perfectly but the content type is always binary/octet-stream instead of my passed content type e.g application/pdf or image/png , how to send the proper content type, actually I want to view the file from S3 instead of download when click the S3 link after upload. Because of binary/octet-stream it's download instead of view on browser.

Love this video. Question though, why would this be done client side vs server side or in Lambda or another FaaS

can you please please make this with nodejs

like it

Would like it if you'd could continue this topic with presigned URL for multiparty upload

Interesting. What would be some good example use-cases for this?

I would have imagined exposing an upload endpoint to the user and handling the uploading ourselves would be the way to go. Would using a pre-signed url still make sense for this use-case, or better to just directly use boto3 s3 put call?