Uploading Objects Using Presigned URLs

Topics

• Upload an Object Using a Presigned URL (AWS SDK for Java)
• Upload an Object to an S3 Bucket Using a Presigned URL (AWS SDK for .NET)
• Upload an Object Using a Presigned URL (AWS SDK for Ruby)

A presigned URL gives you access to the object identified in the URL, provided that the creator of the presigned URL has permissions to access that object. That is, if you receive a presigned URL to upload an object, you can upload the object only if the creator of the presigned URL has the necessary permissions to upload that object.

All objects and buckets by default are private. The presigned URLs are useful if you want your user/customer to be able to upload a specific object to your bucket, but you don't require them to have AWS security credentials or permissions. When you create a presigned URL, you must provide your security credentials and then specify a bucket name, an object key, an HTTP method (PUT for uploading objects), and an expiration date and time. The presigned URLs are valid only for the specified duration.

You can generate a presigned URL programmatically using the AWS SDK for Java or the AWS SDK for .NET. If you are using Microsoft Visual Studio, you can also use AWS Explorer to generate a presigned object URL without writing any code. Anyone who receives a valid presigned URL can then programmatically upload an object.

For more information, go to Using Amazon S3 from AWS Explorer.

For instructions about how to install AWS Explorer, see Using the AWS SDKs, CLI, and Explorers.

Note
Anyone with valid security credentials can create a presigned URL. However, in order for you to successfully upload an object, the presigned URL must be created by someone who has permission to perform the operation that the presigned URL is based upon.