Class: AWS.S3
- Inherits:
-
AWS.Service
- Object
- AWS.Service
- AWS.S3
- Identifier:
- s3
- API Version:
- 2006-03-01
- Defined in:
- (unknown)
Overview
Constructs a service interface object. Each API operation is exposed as a function on service.
Service Description
Sending a Request Using S3
var s3 = new AWS.S3();
s3.abortMultipartUpload(params, function (err, data) {
if (err) console.log(err, err.stack); // an error occurred
else console.log(data); // successful response
});
Locking the API Version
In order to ensure that the S3 object uses this specific API, you can
construct the object by passing the apiVersion
option to the constructor:
var s3 = new AWS.S3({apiVersion: '2006-03-01'});
You can also set the API version globally in AWS.config.apiVersions
using
the s3 service identifier:
AWS.config.apiVersions = {
s3: '2006-03-01',
// other service API versions
};
var s3 = new AWS.S3();
Defined Under Namespace
Classes: ManagedUpload
Waiter Resource States
This service supports a list of resource states that can be polled using the waitFor() method. The resource states are:
bucketExists, bucketNotExists, objectExists, objectNotExists
Constructor Summary collapse
-
new AWS.S3(options = {}) ⇒ Object
constructor
Constructs a service object.
Property Summary collapse
-
endpoint ⇒ AWS.Endpoint
readwrite
An Endpoint object representing the endpoint URL for service requests.
Properties inherited from AWS.Service
Method Summary collapse
-
abortMultipartUpload(params = {}, callback) ⇒ AWS.Request
This action aborts a multipart upload.
-
addLegalHold(params = {}, callback) ⇒ AWS.Request
Add a legal hold on an object.
-
completeMultipartUpload(params = {}, callback) ⇒ AWS.Request
Completes a multipart upload by assembling previously uploaded parts.
You first initiate the multipart upload and then upload all parts using the UploadPart operation.
-
copyObject(params = {}, callback) ⇒ AWS.Request
Creates a copy of an object that is already stored in Amazon S3.
Note: You can store individual objects of up to 5 TB in Amazon S3.- createBucket(params, callback) ⇒ AWS.Request
Creates a new S3 bucket.
- createMultipartUpload(params = {}, callback) ⇒ AWS.Request
This action initiates a multipart upload and returns an upload ID.
- createPresignedPost(params, callback) ⇒ map?
Get a pre-signed POST policy to support uploading to S3 directly from an HTML form.
- deleteBucket(params = {}, callback) ⇒ AWS.Request
Deletes the S3 bucket.
- deleteBucketCors(params = {}, callback) ⇒ AWS.Request
Deletes the
cors
configuration information set for the bucket.To use this operation, you must have permission to perform the
s3:PutBucketCORS
action.- deleteBucketLifecycle(params = {}, callback) ⇒ AWS.Request
Deletes the lifecycle configuration from the specified bucket.
- deleteBucketReplication(params = {}, callback) ⇒ AWS.Request
Deletes the replication configuration from the bucket.
To use this operation, you must have permissions to perform the
s3:PutReplicationConfiguration
action.- deleteBucketTagging(params = {}, callback) ⇒ AWS.Request
Deletes the tags from the bucket.
To use this operation, you must have permission to perform the
s3:PutBucketTagging
action.- deleteBucketWebsite(params = {}, callback) ⇒ AWS.Request
This action removes the website configuration for a bucket.
- deleteLegalHold(params = {}, callback) ⇒ AWS.Request
Remove Legal hold on an object.
- deleteObject(params = {}, callback) ⇒ AWS.Request
Removes the null version (if there is one) of an object and inserts a delete marker, which becomes the latest version of the object.
- deleteObjects(params = {}, callback) ⇒ AWS.Request
This action enables you to delete multiple objects from a bucket using a single HTTP request.
- deleteObjectTagging(params = {}, callback) ⇒ AWS.Request
Removes the entire tag set from the specified object.
- deletePublicAccessBlock(params = {}, callback) ⇒ AWS.Request
Removes the
PublicAccessBlock
configuration for an Amazon S3 bucket.- extendObjectRetention(params = {}, callback) ⇒ AWS.Request
This implementation of the POST operation uses the extendRetention sub-resource to extend the retention period of a protected object in a protected vault.
- getBucketAcl(params = {}, callback) ⇒ AWS.Request
This implementation of the
GET
action uses theacl
subresource to return the access control list (ACL) of a bucket.- getBucketCors(params = {}, callback) ⇒ AWS.Request
Returns the Cross-Origin Resource Sharing (CORS) configuration information set for the bucket.
To use this operation, you must have permission to perform the
s3:GetBucketCORS
action.- getBucketLifecycle(params = {}, callback) ⇒ AWS.Request
For an updated version of this API, see GetBucketLifecycleConfiguration.
- getBucketLifecycleConfiguration(params = {}, callback) ⇒ AWS.Request
Note: Bucket lifecycle configuration now supports specifying a lifecycle rule using an object key name prefix, one or more object tags, or a combination of both.- getBucketLocation(params = {}, callback) ⇒ AWS.Request
Returns the Region the bucket resides in.
- getBucketProtectionConfiguration(params = {}, callback) ⇒ AWS.Request
Returns the protection configuration of a bucket.
- getBucketReplication(params = {}, callback) ⇒ AWS.Request
Returns the replication configuration of a bucket.
Note: It can take a while to propagate the put or delete a replication configuration to all Amazon S3 systems.- getBucketTagging(params = {}, callback) ⇒ AWS.Request
Returns the tag set associated with the bucket.
To use this operation, you must have permission to perform the
s3:GetBucketTagging
action.- getBucketVersioning(params = {}, callback) ⇒ AWS.Request
Returns the versioning state of a bucket.
To retrieve the versioning state of a bucket, you must be the bucket owner.
This implementation also returns the MFA Delete status of the versioning state.
- getBucketWebsite(params = {}, callback) ⇒ AWS.Request
Returns the website configuration for a bucket.
- getObject(params = {}, callback) ⇒ AWS.Request
Retrieves objects from Amazon S3.
- getObjectAcl(params = {}, callback) ⇒ AWS.Request
Returns the access control list (ACL) of an object.
- getObjectLegalHold(params = {}, callback) ⇒ AWS.Request
Gets an object's current legal hold status.
- getObjectLockConfiguration(params = {}, callback) ⇒ AWS.Request
Gets the Object Lock configuration for a bucket.
- getObjectRetention(params = {}, callback) ⇒ AWS.Request
Retrieves an object's retention settings.
- getObjectTagging(params = {}, callback) ⇒ AWS.Request
Returns the tag-set of an object.
- getPublicAccessBlock(params = {}, callback) ⇒ AWS.Request
Retrieves the
PublicAccessBlock
configuration for an Amazon S3 bucket.- getSignedUrl(operation, params, callback) ⇒ String?
Get a pre-signed URL for a given operation name.
- getSignedUrlPromise() ⇒ Promise
Returns a 'thenable' promise that will be resolved with a pre-signed URL for a given operation name.
- headBucket(params = {}, callback) ⇒ AWS.Request
This action is useful to determine if a bucket exists and you have permission to access it.
- headObject(params = {}, callback) ⇒ AWS.Request
The HEAD action retrieves metadata from an object without returning the object itself.
- listBuckets(params = {}, callback) ⇒ AWS.Request
Returns a list of all buckets owned by the authenticated sender of the request.
- listBucketsExtended(params = {}, callback) ⇒ AWS.Request
Returns a list of all buckets owned by the authenticated sender of the request, along with the LocationConstraint describing the region that the bucket resides in and the bucket's storage tier.
- listLegalHolds(params = {}, callback) ⇒ AWS.Request
Returns a list of legal holds on an object.
- listMultipartUploads(params = {}, callback) ⇒ AWS.Request
This action lists in-progress multipart uploads.
- listObjects(params = {}, callback) ⇒ AWS.Request
Returns some or all (up to 1,000) of the objects in a bucket.
- listObjectsV2(params = {}, callback) ⇒ AWS.Request
Returns some or all (up to 1,000) of the objects in a bucket with each request.
- listObjectVersions(params = {}, callback) ⇒ AWS.Request
Returns metadata about all versions of the objects in a bucket.
- listParts(params = {}, callback) ⇒ AWS.Request
Lists the parts that have been uploaded for a specific multipart upload.
- putBucketAcl(params = {}, callback) ⇒ AWS.Request
Sets the permissions on an existing bucket using access control lists (ACL).
- putBucketCors(params = {}, callback) ⇒ AWS.Request
Sets the
cors
configuration for your bucket.- putBucketLifecycle(params = {}, callback) ⇒ AWS.Request
For an updated version of this API, see PutBucketLifecycleConfiguration.
- putBucketLifecycleConfiguration(params = {}, callback) ⇒ AWS.Request
Creates a new lifecycle configuration for the bucket or replaces an existing lifecycle configuration.
- putBucketProtectionConfiguration(params = {}, callback) ⇒ AWS.Request
Sets the protection configuration of an existing bucket.
- putBucketReplication(params = {}, callback) ⇒ AWS.Request
Creates a replication configuration or replaces an existing one.
- putBucketTagging(params = {}, callback) ⇒ AWS.Request
Sets the tags for a bucket.
Use tags to organize your Amazon Web Services bill to reflect your own cost structure.
- putBucketVersioning(params = {}, callback) ⇒ AWS.Request
Sets the versioning state of an existing bucket.
You can set the versioning state with one of the following values:
Enabled—Enables versioning for the objects in the bucket.
- putBucketWebsite(params = {}, callback) ⇒ AWS.Request
Sets the configuration of the website that is specified in the
website
subresource.- putObject(params = {}, callback) ⇒ AWS.Request
Adds an object to a bucket.
- putObjectAcl(params = {}, callback) ⇒ AWS.Request
Uses the
acl
subresource to set the access control list (ACL) permissions for a new or existing object in an S3 bucket.- putObjectLegalHold(params = {}, callback) ⇒ AWS.Request
Applies a legal hold configuration to the specified object.
- putObjectLockConfiguration(params = {}, callback) ⇒ AWS.Request
Places an Object Lock configuration on the specified bucket.
- putObjectRetention(params = {}, callback) ⇒ AWS.Request
Places an Object Retention configuration on an object.
- putObjectTagging(params = {}, callback) ⇒ AWS.Request
Sets the supplied tag-set to an object that already exists in a bucket.
A tag is a key-value pair.
- putPublicAccessBlock(params = {}, callback) ⇒ AWS.Request
Creates or modifies the
PublicAccessBlock
configuration for an Amazon S3 bucket.- restoreObject(params = {}, callback) ⇒ AWS.Request
Restores an archived copy of an object back into Amazon S3
This action is not supported by Amazon S3 on Outposts.
This action performs the following types of requests:
-
select
- Perform a select query on an archived object -
restore an archive
- Restore an archived object
For more information about the
S3
structure in the request body, see the following:-
Managing Access with ACLs in the Amazon S3 User Guide
-
Protecting Data Using Server-Side Encryption in the Amazon S3 User Guide
Define the SQL expression for the
SELECT
type of restoration for your query in the request body'sSelectParameters
structure.- upload(params = {}, [options], [callback]) ⇒ AWS.S3.ManagedUpload
Uploads an arbitrarily sized buffer, blob, or stream, using intelligent concurrent handling of parts if the payload is large enough.
- uploadPart(params = {}, callback) ⇒ AWS.Request
Uploads a part in a multipart upload.
Note: In this operation, you provide part data in your request.- uploadPartCopy(params = {}, callback) ⇒ AWS.Request
Uploads a part by copying data from an existing object as data source.
- waitFor(state, params = {}, callback) ⇒ AWS.Request
Waits for a given S3 resource.
Methods inherited from AWS.Service
makeRequest, makeUnauthenticatedRequest, defineService
Constructor Details
new AWS.S3(options = {}) ⇒ Object
Constructs a service object. This object has one method for each API operation.
Property Details
Method Details
abortMultipartUpload(params = {}, callback) ⇒ AWS.Request
This action aborts a multipart upload. After a multipart upload is aborted, no additional parts can be uploaded using that upload ID. The storage consumed by any previously uploaded parts will be freed. However, if any part uploads are currently in progress, those part uploads might or might not succeed. As a result, it might be necessary to abort a given multipart upload multiple times in order to completely free all storage consumed by all parts.
To verify that all parts have been removed, so you don't get charged for the part storage, you should call the ListParts action and ensure that the parts list is empty.
For information about permissions required to use the multipart upload, see Multipart Upload and Permissions.
The following operations are related to
AbortMultipartUpload
:addLegalHold(params = {}, callback) ⇒ AWS.Request
Add a legal hold on an object. The legal hold identifiers are stored in the object metadata along with the timestamp of when they are POSTed to the object. The presence of any legal hold identifiers prevents the modification or deletion of the object data, even if the retention period has expired. The presence of a retention period header is required, otherwise a 400 error is returned.
completeMultipartUpload(params = {}, callback) ⇒ AWS.Request
Completes a multipart upload by assembling previously uploaded parts.
You first initiate the multipart upload and then upload all parts using the UploadPart operation. After successfully uploading all relevant parts of an upload, you call this action to complete the upload. Upon receiving this request, Amazon S3 concatenates all the parts in ascending order by part number to create a new object. In the Complete Multipart Upload request, you must provide the parts list. You must ensure that the parts list is complete. This action concatenates the parts that you provide in the list. For each part in the list, you must provide the part number and the
ETag
value, returned after that part was uploaded.Processing of a Complete Multipart Upload request could take several minutes to complete. After Amazon S3 begins processing the request, it sends an HTTP response header that specifies a 200 OK response. While processing is in progress, Amazon S3 periodically sends white space characters to keep the connection from timing out. A request could fail after the initial 200 OK response has been sent. This means that a
200 OK
response can contain either a success or an error. If you call the S3 API directly, make sure to design your application to parse the contents of the response and handle it appropriately. If you use Amazon Web Services SDKs, SDKs handle this condition. The SDKs detect the embedded error and apply error handling per your configuration settings (including automatically retrying the request as appropriate). If the condition persists, the SDKs throws an exception (or, for the SDKs that don't use exceptions, they return the error).Note that if
CompleteMultipartUpload
fails, applications should be prepared to retry the failed requests. For more information, see Amazon S3 Error Best Practices.You cannot use
Content-Type: application/x-www-form-urlencoded
with Complete Multipart Upload requests. Also, if you do not provide aContent-Type
header,CompleteMultipartUpload
returns a 200 OK response.For more information about multipart uploads, see Uploading Objects Using Multipart Upload.
For information about permissions required to use the multipart upload API, see Multipart Upload and Permissions.
CompleteMultipartUpload
has the following special errors:-
Error code:
EntityTooSmall
-
Description: Your proposed upload is smaller than the minimum allowed object size. Each part must be at least 5 MB in size, except the last part.
-
400 Bad Request
-
-
Error code:
InvalidPart
-
Description: One or more of the specified parts could not be found. The part might not have been uploaded, or the specified entity tag might not have matched the part's entity tag.
-
400 Bad Request
-
-
Error code:
InvalidPartOrder
-
Description: The list of parts was not in ascending order. The parts list must be specified in order by part number.
-
400 Bad Request
-
-
Error code:
NoSuchUpload
-
Description: The specified multipart upload does not exist. The upload ID might be invalid, or the multipart upload might have been aborted or completed.
-
404 Not Found
-
The following operations are related to
CompleteMultipartUpload
:copyObject(params = {}, callback) ⇒ AWS.Request
Creates a copy of an object that is already stored in Amazon S3.
Note: You can store individual objects of up to 5 TB in Amazon S3. You create a copy of your object up to 5 GB in size in a single atomic action using this API. However, to copy an object greater than 5 GB, you must use the multipart upload Upload Part - Copy (UploadPartCopy) API. For more information, see Copy Object Using the REST Multipart Upload API.All copy requests must be authenticated. Additionally, you must have read access to the source object and write access to the destination bucket. For more information, see REST Authentication. Both the Region that you want to copy the object from and the Region that you want to copy the object to must be enabled for your account.
A copy request might return an error when Amazon S3 receives the copy request or while Amazon S3 is copying the files. If the error occurs before the copy action starts, you receive a standard Amazon S3 error. If the error occurs during the copy operation, the error response is embedded in the
200 OK
response. This means that a200 OK
response can contain either a success or an error. If you call the S3 API directly, make sure to design your application to parse the contents of the response and handle it appropriately. If you use Amazon Web Services SDKs, SDKs handle this condition. The SDKs detect the embedded error and apply error handling per your configuration settings (including automatically retrying the request as appropriate). If the condition persists, the SDKs throws an exception (or, for the SDKs that don't use exceptions, they return the error).If the copy is successful, you receive a response with information about the copied object.
Note: If the request is an HTTP 1.1 request, the response is chunk encoded. If it were not, it would not contain the content-length, and you would need to read the entire body.The copy request charge is based on the storage class and Region that you specify for the destination object. For pricing information, see Amazon S3 pricing.
Amazon S3 transfer acceleration does not support cross-Region copies. If you request a cross-Region copy using a transfer acceleration endpoint, you get a 400
Bad Request
error. For more information, see Transfer Acceleration.- Metadata
-
When copying an object, you can preserve all metadata (default) or specify new metadata. However, the ACL is not preserved and is set to private for the user making the request. To override the default ACL setting, specify a new ACL when generating a copy request. For more information, see Using ACLs.
To specify whether you want the object metadata copied from the source object or replaced with metadata provided in the request, you can optionally add the
x-amz-metadata-directive
header. When you grant permissions, you can use thes3:x-amz-metadata-directive
condition key to enforce certain metadata behavior when objects are uploaded. For more information, see Specifying Conditions in a Policy in the Amazon S3 User Guide. For a complete list of Amazon S3-specific condition keys, see Actions, Resources, and Condition Keys for Amazon S3.Note:x-amz-website-redirect-location
is unique to each object and must be specified in the request headers to copy the value. - x-amz-copy-source-if Headers
-
To only copy an object under certain conditions, such as whether the
Etag
matches or whether the object was modified before or after a specified date, use the following request parameters:-
x-amz-copy-source-if-match
-
x-amz-copy-source-if-none-match
-
x-amz-copy-source-if-unmodified-since
-
x-amz-copy-source-if-modified-since
If both the
x-amz-copy-source-if-match
andx-amz-copy-source-if-unmodified-since
headers are present in the request and evaluate as follows, Amazon S3 returns200 OK
and copies the data:-
x-amz-copy-source-if-match
condition evaluates to true -
x-amz-copy-source-if-unmodified-since
condition evaluates to false
If both the
x-amz-copy-source-if-none-match
andx-amz-copy-source-if-modified-since
headers are present in the request and evaluate as follows, Amazon S3 returns the412 Precondition Failed
response code:-
x-amz-copy-source-if-none-match
condition evaluates to false -
x-amz-copy-source-if-modified-since
condition evaluates to true
Note: All headers with thex-amz-
prefix, includingx-amz-copy-source
, must be signed. -
- Server-side encryption
-
Amazon S3 automatically encrypts all new objects that are copied to an S3 bucket. When copying an object, if you don't specify encryption information in your copy request, the encryption setting of the target object is set to the default encryption configuration of the destination bucket. By default, all buckets have a base level of encryption configuration that uses server-side encryption with Amazon S3 managed keys (SSE-S3). If the destination bucket has a default encryption configuration that uses server-side encryption with an Key Management Service (KMS) key (SSE-KMS), or a customer-provided encryption key (SSE-C), Amazon S3 uses the corresponding KMS key, or a customer-provided key to encrypt the target object copy.
When you perform a CopyObject operation, if you want to use a different type of encryption setting for the target object, you can use other appropriate encryption-related headers to encrypt the target object with a KMS key, an Amazon S3 managed key, or a customer-provided key. With server-side encryption, Amazon S3 encrypts your data as it writes it to disks in its data centers and decrypts the data when you access it. If the encryption setting in your request is different from the default encryption configuration of the destination bucket, the encryption setting in your request takes precedence. If the source object for the copy is stored in Amazon S3 using SSE-C, you must provide the necessary encryption information in your request so that Amazon S3 can decrypt the object for copying. For more information about server-side encryption, see Using Server-Side Encryption.
If a target object uses SSE-KMS, you can enable an S3 Bucket Key for the object. For more information, see Amazon S3 Bucket Keys in the Amazon S3 User Guide.
- Access Control List (ACL)-Specific Request Headers
-
When copying an object, you can optionally use headers to grant ACL-based permissions. By default, all objects are private. Only the owner has full access control. When adding a new object, you can grant permissions to individual Amazon Web Services accounts or to predefined groups defined by Amazon S3. These permissions are then added to the ACL on the object. For more information, see Access Control List (ACL) Overview and Managing ACLs Using the REST API.
If the bucket that you're copying objects to uses the bucket owner enforced setting for S3 Object Ownership, ACLs are disabled and no longer affect permissions. Buckets that use this setting only accept PUT requests that don't specify an ACL or PUT requests that specify bucket owner full control ACLs, such as the
bucket-owner-full-control
canned ACL or an equivalent form of this ACL expressed in the XML format.For more information, see Controlling ownership of objects and disabling ACLs in the Amazon S3 User Guide.
Note: If your bucket uses the bucket owner enforced setting for Object Ownership, all objects written to the bucket by any account will be owned by the bucket owner. - Checksums
-
When copying an object, if it has a checksum, that checksum will be copied to the new object by default. When you copy the object over, you may optionally specify a different checksum algorithm to use with the
x-amz-checksum-algorithm
header. - Storage Class Options
-
You can use the
CopyObject
action to change the storage class of an object that is already stored in Amazon S3 using theStorageClass
parameter. For more information, see Storage Classes in the Amazon S3 User Guide.If the source object's storage class is GLACIER, you must restore a copy of this object before you can use it as a source object for the copy operation. For more information, see RestoreObject. For more information, see Copying Objects.
- Versioning
-
By default,
x-amz-copy-source
identifies the current version of an object to copy. If the current version is a delete marker, Amazon S3 behaves as if the object was deleted. To copy a different version, use theversionId
subresource.If you enable versioning on the target bucket, Amazon S3 generates a unique version ID for the object being copied. This version ID is different from the version ID of the source object. Amazon S3 returns the version ID of the copied object in the
x-amz-version-id
response header in the response.If you do not enable versioning or suspend it on the target bucket, the version ID that Amazon S3 generates is always null.
The following operations are related to
CopyObject
:createBucket(params, callback) ⇒ AWS.Request
Creates a new S3 bucket. To create a bucket, you must register with Amazon S3 and have a valid Amazon Web Services Access Key ID to authenticate requests. Anonymous requests are never allowed to create buckets. By creating the bucket, you become the bucket owner.
Not every string is an acceptable bucket name. For information about bucket naming restrictions, see Bucket naming rules.
If you want to create an Amazon S3 on Outposts bucket, see Create Bucket.
By default, the bucket is created in the US East (N. Virginia) Region. You can optionally specify a Region in the request body. You might choose a Region to optimize latency, minimize costs, or address regulatory requirements. For example, if you reside in Europe, you will probably find it advantageous to create buckets in the Europe (Ireland) Region. For more information, see Accessing a bucket.
Note: If you send your create bucket request to thes3.amazonaws.com
endpoint, the request goes to the us-east-1 Region. Accordingly, the signature calculations in Signature Version 4 must use us-east-1 as the Region, even if the location constraint in the request specifies another Region where the bucket is to be created. If you create a bucket in a Region other than US East (N. Virginia), your application must be able to handle 307 redirect. For more information, see Virtual hosting of buckets.- Access control lists (ACLs)
-
When creating a bucket using this operation, you can optionally configure the bucket ACL to specify the accounts or groups that should be granted specific permissions on the bucket.
If your CreateBucket request sets bucket owner enforced for S3 Object Ownership and specifies a bucket ACL that provides access to an external Amazon Web Services account, your request fails with a
400
error and returns theInvalidBucketAclWithObjectOwnership
error code. For more information, see Controlling object ownership in the Amazon S3 User Guide.There are two ways to grant the appropriate permissions using the request headers.
-
Specify a canned ACL using the
x-amz-acl
request header. Amazon S3 supports a set of predefined ACLs, known as canned ACLs. Each canned ACL has a predefined set of grantees and permissions. For more information, see Canned ACL. -
Specify access permissions explicitly using the
x-amz-grant-read
,x-amz-grant-write
,x-amz-grant-read-acp
,x-amz-grant-write-acp
, andx-amz-grant-full-control
headers. These headers map to the set of permissions Amazon S3 supports in an ACL. For more information, see Access control list (ACL) overview.You specify each grantee as a type=value pair, where the type is one of the following:
-
id
– if the value specified is the canonical user ID of an Amazon Web Services account -
uri
– if you are granting permissions to a predefined group -
emailAddress
– if the value specified is the email address of an Amazon Web Services accountNote: Using email addresses to specify a grantee is only supported in the following Amazon Web Services Regions:- US East (N. Virginia)
- US West (N. California)
- US West (Oregon)
- Asia Pacific (Singapore)
- Asia Pacific (Sydney)
- Asia Pacific (Tokyo)
- Europe (Ireland)
- South America (São Paulo)
For example, the following
x-amz-grant-read
header grants the Amazon Web Services accounts identified by account IDs permissions to read object data and its metadata:x-amz-grant-read: id="11112222333", id="444455556666"
-
Note: You can use either a canned ACL or specify access permissions explicitly. You cannot do both. -
- Permissions
-
In addition to
s3:CreateBucket
, the following permissions are required when your CreateBucket includes specific headers:-
ACLs - If your
CreateBucket
request specifies ACL permissions and the ACL is public-read, public-read-write, authenticated-read, or if you specify access permissions explicitly through any other ACL, boths3:CreateBucket
ands3:PutBucketAcl
permissions are needed. If the ACL theCreateBucket
request is private or doesn't specify any ACLs, onlys3:CreateBucket
permission is needed. -
Object Lock - If
ObjectLockEnabledForBucket
is set to true in yourCreateBucket
request,s3:PutBucketObjectLockConfiguration
ands3:PutBucketVersioning
permissions are required. -
S3 Object Ownership - If your CreateBucket request includes the
x-amz-object-ownership
header,s3:PutBucketOwnershipControls
permission is required.
-
The following operations are related to
CreateBucket
:Note: This operation cannot be used in a browser. S3 does not support CORS on this operation.
createMultipartUpload(params = {}, callback) ⇒ AWS.Request
This action initiates a multipart upload and returns an upload ID. This upload ID is used to associate all of the parts in the specific multipart upload. You specify this upload ID in each of your subsequent upload part requests (see UploadPart). You also include this upload ID in the final request to either complete or abort the multipart upload request.
For more information about multipart uploads, see Multipart Upload Overview.
If you have configured a lifecycle rule to abort incomplete multipart uploads, the upload must complete within the number of days specified in the bucket lifecycle configuration. Otherwise, the incomplete multipart upload becomes eligible for an abort action and Amazon S3 aborts the multipart upload. For more information, see Aborting Incomplete Multipart Uploads Using a Bucket Lifecycle Configuration.
For information about the permissions required to use the multipart upload API, see Multipart Upload and Permissions.
For request signing, multipart upload is just a series of regular requests. You initiate a multipart upload, send one or more requests to upload parts, and then complete the multipart upload process. You sign each request individually. There is nothing special about signing multipart upload requests. For more information about signing, see Authenticating Requests (Amazon Web Services Signature Version 4).
Note: After you initiate a multipart upload and upload one or more parts, to stop being charged for storing the uploaded parts, you must either complete or abort the multipart upload. Amazon S3 frees up the space used to store the parts and stop charging you for storing them only after you either complete or abort a multipart upload.Server-side encryption is for data encryption at rest. Amazon S3 encrypts your data as it writes it to disks in its data centers and decrypts it when you access it. Amazon S3 automatically encrypts all new objects that are uploaded to an S3 bucket. When doing a multipart upload, if you don't specify encryption information in your request, the encryption setting of the uploaded parts is set to the default encryption configuration of the destination bucket. By default, all buckets have a base level of encryption configuration that uses server-side encryption with Amazon S3 managed keys (SSE-S3). If the destination bucket has a default encryption configuration that uses server-side encryption with an Key Management Service (KMS) key (SSE-KMS), or a customer-provided encryption key (SSE-C), Amazon S3 uses the corresponding KMS key, or a customer-provided key to encrypt the uploaded parts. When you perform a CreateMultipartUpload operation, if you want to use a different type of encryption setting for the uploaded parts, you can request that Amazon S3 encrypts the object with a KMS key, an Amazon S3 managed key, or a customer-provided key. If the encryption setting in your request is different from the default encryption configuration of the destination bucket, the encryption setting in your request takes precedence. If you choose to provide your own encryption key, the request headers you provide in UploadPart and UploadPartCopy requests must match the headers you used in the request to initiate the upload by using
CreateMultipartUpload
. You can request that Amazon S3 save the uploaded parts encrypted with server-side encryption with an Amazon S3 managed key (SSE-S3), an Key Management Service (KMS) key (SSE-KMS), or a customer-provided encryption key (SSE-C).To perform a multipart upload with encryption by using an Amazon Web Services KMS key, the requester must have permission to the
kms:Decrypt
andkms:GenerateDataKey*
actions on the key. These permissions are required because Amazon S3 must decrypt and read data from the encrypted file parts before it completes the multipart upload. For more information, see Multipart upload API and permissions and Protecting data using server-side encryption with Amazon Web Services KMS in the Amazon S3 User Guide.If your Identity and Access Management (IAM) user or role is in the same Amazon Web Services account as the KMS key, then you must have these permissions on the key policy. If your IAM user or role belongs to a different account than the key, then you must have the permissions on both the key policy and your IAM user or role.
For more information, see Protecting Data Using Server-Side Encryption.
- Access Permissions
-
When copying an object, you can optionally specify the accounts or groups that should be granted specific permissions on the new object. There are two ways to grant the permissions using the request headers:
-
Specify a canned ACL with the
x-amz-acl
request header. For more information, see Canned ACL. -
Specify access permissions explicitly with the
x-amz-grant-read
,x-amz-grant-read-acp
,x-amz-grant-write-acp
, andx-amz-grant-full-control
headers. These parameters map to the set of permissions that Amazon S3 supports in an ACL. For more information, see Access Control List (ACL) Overview.
You can use either a canned ACL or specify access permissions explicitly. You cannot do both.
-
- Server-Side- Encryption-Specific Request Headers
-
Amazon S3 encrypts data by using server-side encryption with an Amazon S3 managed key (SSE-S3) by default. Server-side encryption is for data encryption at rest. Amazon S3 encrypts your data as it writes it to disks in its data centers and decrypts it when you access it. You can request that Amazon S3 encrypts data at rest by using server-side encryption with other key options. The option you use depends on whether you want to use KMS keys (SSE-KMS) or provide your own encryption keys (SSE-C).
-
Use KMS keys (SSE-KMS) that include the Amazon Web Services managed key (
aws/s3
) and KMS customer managed keys stored in Key Management Service (KMS) – If you want Amazon Web Services to manage the keys used to encrypt data, specify the following headers in the request.-
x-amz-server-side-encryption
-
x-amz-server-side-encryption-aws-kms-key-id
-
x-amz-server-side-encryption-context
Note: If you specifyx-amz-server-side-encryption:aws:kms
, but don't providex-amz-server-side-encryption-aws-kms-key-id
, Amazon S3 uses the Amazon Web Services managed key (aws/s3
key) in KMS to protect the data.All
GET
andPUT
requests for an object protected by KMS fail if you don't make them by using Secure Sockets Layer (SSL), Transport Layer Security (TLS), or Signature Version 4.For more information about server-side encryption with KMS keys (SSE-KMS), see Protecting Data Using Server-Side Encryption with KMS keys.
-
-
Use customer-provided encryption keys (SSE-C) – If you want to manage your own encryption keys, provide all the following headers in the request.
-
x-amz-server-side-encryption-customer-algorithm
-
x-amz-server-side-encryption-customer-key
-
x-amz-server-side-encryption-customer-key-MD5
For more information about server-side encryption with customer-provided encryption keys (SSE-C), see Protecting data using server-side encryption with customer-provided encryption keys (SSE-C).
-
-
- Access-Control-List (ACL)-Specific Request Headers
-
You also can use the following access control–related headers with this operation. By default, all objects are private. Only the owner has full access control. When adding a new object, you can grant permissions to individual Amazon Web Services accounts or to predefined groups defined by Amazon S3. These permissions are then added to the access control list (ACL) on the object. For more information, see Using ACLs. With this operation, you can grant access permissions using one of the following two methods:
-
Specify a canned ACL (
x-amz-acl
) — Amazon S3 supports a set of predefined ACLs, known as canned ACLs. Each canned ACL has a predefined set of grantees and permissions. For more information, see Canned ACL. -
Specify access permissions explicitly — To explicitly grant access permissions to specific Amazon Web Services accounts or groups, use the following headers. Each header maps to specific permissions that Amazon S3 supports in an ACL. For more information, see Access Control List (ACL) Overview. In the header, you specify a list of grantees who get the specific permission. To grant permissions explicitly, use:
-
x-amz-grant-read
-
x-amz-grant-write
-
x-amz-grant-read-acp
-
x-amz-grant-write-acp
-
x-amz-grant-full-control
You specify each grantee as a type=value pair, where the type is one of the following:
-
id
– if the value specified is the canonical user ID of an Amazon Web Services account -
uri
– if you are granting permissions to a predefined group -
emailAddress
– if the value specified is the email address of an Amazon Web Services accountNote: Using email addresses to specify a grantee is only supported in the following Amazon Web Services Regions:- US East (N. Virginia)
- US West (N. California)
- US West (Oregon)
- Asia Pacific (Singapore)
- Asia Pacific (Sydney)
- Asia Pacific (Tokyo)
- Europe (Ireland)
- South America (São Paulo)
For example, the following
x-amz-grant-read
header grants the Amazon Web Services accounts identified by account IDs permissions to read object data and its metadata:x-amz-grant-read: id="11112222333", id="444455556666"
-
-
The following operations are related to
CreateMultipartUpload
:createPresignedPost(params, callback) ⇒ map?
Note:All fields passed in when creating presigned post data will be signed as exact match conditions. Any fields that will be interpolated by S3 must be added to the fields hash after signing, and an appropriate condition for such fields must be explicitly added to the Conditions array passed to this function before signing.
Note:You must ensure that you have static or previously resolved credentials if you call this method synchronously (with no callback), otherwise it may not properly sign the request. If you cannot guarantee this (you are using an asynchronous credential provider, i.e., EC2 IAM roles), you should always call this method with an asynchronous callback.
Get a pre-signed POST policy to support uploading to S3 directly from an HTML form.
deleteBucket(params = {}, callback) ⇒ AWS.Request
Deletes the S3 bucket. All objects (including all object versions and delete markers) in the bucket must be deleted before the bucket itself can be deleted.
The following operations are related to
DeleteBucket
:Note: This operation cannot be used in a browser. S3 does not support CORS on this operation.
deleteBucketCors(params = {}, callback) ⇒ AWS.Request
Deletes the
cors
configuration information set for the bucket.To use this operation, you must have permission to perform the
s3:PutBucketCORS
action. The bucket owner has this permission by default and can grant this permission to others.For information about
cors
, see Enabling Cross-Origin Resource Sharing in the Amazon S3 User Guide.The following operations are related to
DeleteBucketCors
:deleteBucketLifecycle(params = {}, callback) ⇒ AWS.Request
Deletes the lifecycle configuration from the specified bucket. Amazon S3 removes all the lifecycle configuration rules in the lifecycle subresource associated with the bucket. Your objects never expire, and Amazon S3 no longer automatically deletes any objects on the basis of rules contained in the deleted lifecycle configuration.
To use this operation, you must have permission to perform the
s3:PutLifecycleConfiguration
action. By default, the bucket owner has this permission and the bucket owner can grant this permission to others.There is usually some time lag before lifecycle configuration deletion is fully propagated to all the Amazon S3 systems.
For more information about the object expiration, see Elements to Describe Lifecycle Actions.
Related actions include:
deleteBucketReplication(params = {}, callback) ⇒ AWS.Request
Deletes the replication configuration from the bucket.
To use this operation, you must have permissions to perform the
s3:PutReplicationConfiguration
action. The bucket owner has these permissions by default and can grant it to others. For more information about permissions, see Permissions Related to Bucket Subresource Operations and Managing Access Permissions to Your Amazon S3 Resources.Note: It can take a while for the deletion of a replication configuration to fully propagate.For information about replication configuration, see Replication in the Amazon S3 User Guide.
The following operations are related to
DeleteBucketReplication
:deleteBucketTagging(params = {}, callback) ⇒ AWS.Request
Deletes the tags from the bucket.
To use this operation, you must have permission to perform the
s3:PutBucketTagging
action. By default, the bucket owner has this permission and can grant this permission to others.The following operations are related to
DeleteBucketTagging
:deleteBucketWebsite(params = {}, callback) ⇒ AWS.Request
This action removes the website configuration for a bucket. Amazon S3 returns a
200 OK
response upon successfully deleting a website configuration on the specified bucket. You will get a200 OK
response if the website configuration you are trying to delete does not exist on the bucket. Amazon S3 returns a404
response if the bucket specified in the request does not exist.This DELETE action requires the
S3:DeleteBucketWebsite
permission. By default, only the bucket owner can delete the website configuration attached to a bucket. However, bucket owners can grant other users permission to delete the website configuration by writing a bucket policy granting them theS3:DeleteBucketWebsite
permission.For more information about hosting websites, see Hosting Websites on Amazon S3.
The following operations are related to
DeleteBucketWebsite
:deleteLegalHold(params = {}, callback) ⇒ AWS.Request
Remove Legal hold on an object. The legal hold identifiers are stored in the object metadata along with the timestamp of when they are POSTed to the object. The presence of any legal hold identifiers prevents the modification or deletion of the object data, even if the retention period has expired. The presence of a retention period header is required, otherwise a 400 error is returned.
deleteObject(params = {}, callback) ⇒ AWS.Request
Removes the null version (if there is one) of an object and inserts a delete marker, which becomes the latest version of the object. If there isn't a null version, Amazon S3 does not remove any objects but will still respond that the command was successful.
To remove a specific version, you must use the version Id subresource. Using this subresource permanently deletes the version. If the object deleted is a delete marker, Amazon S3 sets the response header,
x-amz-delete-marker
, to true.If the object you want to delete is in a bucket where the bucket versioning configuration is MFA Delete enabled, you must include the
x-amz-mfa
request header in the DELETEversionId
request. Requests that includex-amz-mfa
must use HTTPS.For more information about MFA Delete, see Using MFA Delete. To see sample requests that use versioning, see Sample Request.
You can delete objects by explicitly calling DELETE Object or configure its lifecycle (PutBucketLifecycle) to enable Amazon S3 to remove them for you. If you want to block users or accounts from removing or deleting objects from your bucket, you must deny them the
s3:DeleteObject
,s3:DeleteObjectVersion
, ands3:PutLifeCycleConfiguration
actions.The following action is related to
DeleteObject
:deleteObjects(params = {}, callback) ⇒ AWS.Request
This action enables you to delete multiple objects from a bucket using a single HTTP request. If you know the object keys that you want to delete, then this action provides a suitable alternative to sending individual delete requests, reducing per-request overhead.
The request contains a list of up to 1000 keys that you want to delete. In the XML, you provide the object key names, and optionally, version IDs if you want to delete a specific version of the object from a versioning-enabled bucket. For each key, Amazon S3 performs a delete action and returns the result of that delete, success, or failure, in the response. Note that if the object specified in the request is not found, Amazon S3 returns the result as deleted.
The action supports two modes for the response: verbose and quiet. By default, the action uses verbose mode in which the response includes the result of deletion of each key in your request. In quiet mode the response includes only keys where the delete action encountered an error. For a successful deletion, the action does not return any information about the delete in the response body.
When performing this action on an MFA Delete enabled bucket, that attempts to delete any versioned objects, you must include an MFA token. If you do not provide one, the entire request will fail, even if there are non-versioned objects you are trying to delete. If you provide an invalid token, whether there are versioned keys in the request or not, the entire Multi-Object Delete request will fail. For information about MFA Delete, see MFA Delete.
Finally, the Content-MD5 header is required for all Multi-Object Delete requests. Amazon S3 uses the header value to ensure that your request body has not been altered in transit.
The following operations are related to
DeleteObjects
:deleteObjectTagging(params = {}, callback) ⇒ AWS.Request
Removes the entire tag set from the specified object. For more information about managing object tags, see Object Tagging.
To use this operation, you must have permission to perform the
s3:DeleteObjectTagging
action.To delete tags of a specific object version, add the
versionId
query parameter in the request. You will need permission for thes3:DeleteObjectVersionTagging
action.The following operations are related to
DeleteObjectTagging
:deletePublicAccessBlock(params = {}, callback) ⇒ AWS.Request
Removes the
PublicAccessBlock
configuration for an Amazon S3 bucket. To use this operation, you must have thes3:PutBucketPublicAccessBlock
permission. For more information about permissions, see Permissions Related to Bucket Subresource Operations and Managing Access Permissions to Your Amazon S3 Resources.The following operations are related to
DeletePublicAccessBlock
:extendObjectRetention(params = {}, callback) ⇒ AWS.Request
This implementation of the POST operation uses the extendRetention sub-resource to extend the retention period of a protected object in a protected vault.
getBucketAcl(params = {}, callback) ⇒ AWS.Request
This implementation of the
GET
action uses theacl
subresource to return the access control list (ACL) of a bucket. To useGET
to return the ACL of the bucket, you must haveREAD_ACP
access to the bucket. IfREAD_ACP
permission is granted to the anonymous user, you can return the ACL of the bucket without using an authorization header.To use this API operation against an access point, provide the alias of the access point in place of the bucket name.
To use this API operation against an Object Lambda access point, provide the alias of the Object Lambda access point in place of the bucket name. If the Object Lambda access point alias in a request is not valid, the error code
InvalidAccessPointAliasError
is returned. For more information aboutInvalidAccessPointAliasError
, see List of Error Codes.Note: If your bucket uses the bucket owner enforced setting for S3 Object Ownership, requests to read ACLs are still supported and return thebucket-owner-full-control
ACL with the owner being the account that created the bucket. For more information, see Controlling object ownership and disabling ACLs in the Amazon S3 User Guide.The following operations are related to
GetBucketAcl
:getBucketCors(params = {}, callback) ⇒ AWS.Request
Returns the Cross-Origin Resource Sharing (CORS) configuration information set for the bucket.
To use this operation, you must have permission to perform the
s3:GetBucketCORS
action. By default, the bucket owner has this permission and can grant it to others.To use this API operation against an access point, provide the alias of the access point in place of the bucket name.
To use this API operation against an Object Lambda access point, provide the alias of the Object Lambda access point in place of the bucket name. If the Object Lambda access point alias in a request is not valid, the error code
InvalidAccessPointAliasError
is returned. For more information aboutInvalidAccessPointAliasError
, see List of Error Codes.For more information about CORS, see Enabling Cross-Origin Resource Sharing.
The following operations are related to
GetBucketCors
:getBucketLifecycle(params = {}, callback) ⇒ AWS.Request
For an updated version of this API, see GetBucketLifecycleConfiguration. If you configured a bucket lifecycle using the
filter
element, you should see the updated version of this topic. This topic is provided for backward compatibility.Returns the lifecycle configuration information set on the bucket. For information about lifecycle configuration, see Object Lifecycle Management.
To use this operation, you must have permission to perform the
s3:GetLifecycleConfiguration
action. The bucket owner has this permission by default. The bucket owner can grant this permission to others. For more information about permissions, see Permissions Related to Bucket Subresource Operations and Managing Access Permissions to Your Amazon S3 Resources.GetBucketLifecycle
has the following special error:-
Error code:
NoSuchLifecycleConfiguration
-
Description: The lifecycle configuration does not exist.
-
HTTP Status Code: 404 Not Found
-
SOAP Fault Code Prefix: Client
-
The following operations are related to
GetBucketLifecycle
:getBucketLifecycleConfiguration(params = {}, callback) ⇒ AWS.Request
Note: Bucket lifecycle configuration now supports specifying a lifecycle rule using an object key name prefix, one or more object tags, or a combination of both. Accordingly, this section describes the latest API. The response describes the new filter element that you can use to specify a filter to select a subset of objects to which the rule applies. If you are using a previous version of the lifecycle configuration, it still works. For the earlier action, see GetBucketLifecycle.Returns the lifecycle configuration information set on the bucket. For information about lifecycle configuration, see Object Lifecycle Management.
To use this operation, you must have permission to perform the
s3:GetLifecycleConfiguration
action. The bucket owner has this permission, by default. The bucket owner can grant this permission to others. For more information about permissions, see Permissions Related to Bucket Subresource Operations and Managing Access Permissions to Your Amazon S3 Resources.GetBucketLifecycleConfiguration
has the following special error:-
Error code:
NoSuchLifecycleConfiguration
-
Description: The lifecycle configuration does not exist.
-
HTTP Status Code: 404 Not Found
-
SOAP Fault Code Prefix: Client
-
The following operations are related to
GetBucketLifecycleConfiguration
:getBucketLocation(params = {}, callback) ⇒ AWS.Request
Returns the Region the bucket resides in. You set the bucket's Region using the
LocationConstraint
request parameter in aCreateBucket
request. For more information, see CreateBucket.To use this API operation against an access point, provide the alias of the access point in place of the bucket name.
To use this API operation against an Object Lambda access point, provide the alias of the Object Lambda access point in place of the bucket name. If the Object Lambda access point alias in a request is not valid, the error code
InvalidAccessPointAliasError
is returned. For more information aboutInvalidAccessPointAliasError
, see List of Error Codes.Note: We recommend that you use HeadBucket to return the Region that a bucket resides in. For backward compatibility, Amazon S3 continues to support GetBucketLocation.The following operations are related to
GetBucketLocation
:getBucketProtectionConfiguration(params = {}, callback) ⇒ AWS.Request
Returns the protection configuration of a bucket.
getBucketReplication(params = {}, callback) ⇒ AWS.Request
Returns the replication configuration of a bucket.
Note: It can take a while to propagate the put or delete a replication configuration to all Amazon S3 systems. Therefore, a get request soon after put or delete can return a wrong result.For information about replication configuration, see Replication in the Amazon S3 User Guide.
This action requires permissions for the
s3:GetReplicationConfiguration
action. For more information about permissions, see Using Bucket Policies and User Policies.If you include the
Filter
element in a replication configuration, you must also include theDeleteMarkerReplication
andPriority
elements. The response also returns those elements.For information about
GetBucketReplication
errors, see List of replication-related error codesThe following operations are related to
GetBucketReplication
:getBucketTagging(params = {}, callback) ⇒ AWS.Request
Returns the tag set associated with the bucket.
To use this operation, you must have permission to perform the
s3:GetBucketTagging
action. By default, the bucket owner has this permission and can grant this permission to others.GetBucketTagging
has the following special error:-
Error code:
NoSuchTagSet
-
Description: There is no tag set associated with the bucket.
-
The following operations are related to
GetBucketTagging
:getBucketVersioning(params = {}, callback) ⇒ AWS.Request
Returns the versioning state of a bucket.
To retrieve the versioning state of a bucket, you must be the bucket owner.
This implementation also returns the MFA Delete status of the versioning state. If the MFA Delete status is
enabled
, the bucket owner must use an authentication device to change the versioning state of the bucket.The following operations are related to
GetBucketVersioning
:getBucketWebsite(params = {}, callback) ⇒ AWS.Request
Returns the website configuration for a bucket. To host website on Amazon S3, you can configure a bucket as website by adding a website configuration. For more information about hosting websites, see Hosting Websites on Amazon S3.
This GET action requires the
S3:GetBucketWebsite
permission. By default, only the bucket owner can read the bucket website configuration. However, bucket owners can allow other users to read the website configuration by writing a bucket policy granting them theS3:GetBucketWebsite
permission.The following operations are related to
GetBucketWebsite
:getObject(params = {}, callback) ⇒ AWS.Request
Retrieves objects from Amazon S3. To use
GET
, you must haveREAD
access to the object. If you grantREAD
access to the anonymous user, you can return the object without using an authorization header.An Amazon S3 bucket has no directory hierarchy such as you would find in a typical computer file system. You can, however, create a logical hierarchy by using object key names that imply a folder structure. For example, instead of naming an object
sample.jpg
, you can name itphotos/2006/February/sample.jpg
.To get an object from such a logical hierarchy, specify the full key name for the object in the
GET
operation. For a virtual hosted-style request example, if you have the objectphotos/2006/February/sample.jpg
, specify the resource as/photos/2006/February/sample.jpg
. For a path-style request example, if you have the objectphotos/2006/February/sample.jpg
in the bucket namedexamplebucket
, specify the resource as/examplebucket/photos/2006/February/sample.jpg
. For more information about request types, see HTTP Host Header Bucket Specification.For more information about returning the ACL of an object, see GetObjectAcl.
If the object you are retrieving is stored in the S3 Glacier or S3 Glacier Deep Archive storage class, or S3 Intelligent-Tiering Archive or S3 Intelligent-Tiering Deep Archive tiers, before you can retrieve the object you must first restore a copy using RestoreObject. Otherwise, this action returns an
InvalidObjectState
error. For information about restoring archived objects, see Restoring Archived Objects.Encryption request headers, like
x-amz-server-side-encryption
, should not be sent for GET requests if your object uses server-side encryption with KMS keys (SSE-KMS) or server-side encryption with Amazon S3–managed encryption keys (SSE-S3). If your object does use these types of keys, you’ll get an HTTP 400 BadRequest error.If you encrypt an object by using server-side encryption with customer-provided encryption keys (SSE-C) when you store the object in Amazon S3, then when you GET the object, you must use the following headers:
-
x-amz-server-side-encryption-customer-algorithm
-
x-amz-server-side-encryption-customer-key
-
x-amz-server-side-encryption-customer-key-MD5
For more information about SSE-C, see Server-Side Encryption (Using Customer-Provided Encryption Keys).
Assuming you have the relevant permission to read object tags, the response also returns the
x-amz-tagging-count
header that provides the count of number of tags associated with the object. You can use GetObjectTagging to retrieve the tag set associated with an object.- Permissions
-
You need the relevant read object (or version) permission for this operation. For more information, see Specifying Permissions in a Policy. If the object you request does not exist, the error Amazon S3 returns depends on whether you also have the
s3:ListBucket
permission.-
If you have the
s3:ListBucket
permission on the bucket, Amazon S3 will return an HTTP status code 404 ("no such key") error. -
If you don’t have the
s3:ListBucket
permission, Amazon S3 will return an HTTP status code 403 ("access denied") error.
-
- Versioning
-
By default, the GET action returns the current version of an object. To return a different version, use the
versionId
subresource.Note:- If you supply a
versionId
, you need thes3:GetObjectVersion
permission to access a specific version of an object. If you request a specific version, you do not need to have thes3:GetObject
permission. If you request the current version without a specific version ID, onlys3:GetObject
permission is required.s3:GetObjectVersion
permission won't be required. - If the current version of the object is a delete marker, Amazon S3 behaves as if the object was deleted and includes
x-amz-delete-marker: true
in the response.
For more information about versioning, see PutBucketVersioning.
- If you supply a
- Overriding Response Header Values
-
There are times when you want to override certain response header values in a GET response. For example, you might override the
Content-Disposition
response header value in your GET request.You can override values for a set of response headers using the following query parameters. These response header values are sent only on a successful request, that is, when status code 200 OK is returned. The set of headers you can override using these parameters is a subset of the headers that Amazon S3 accepts when you create an object. The response headers that you can override for the GET response are
Content-Type
,Content-Language
,Expires
,Cache-Control
,Content-Disposition
, andContent-Encoding
. To override these header values in the GET response, you use the following request parameters.Note: You must sign the request, either using an Authorization header or a presigned URL, when using these parameters. They cannot be used with an unsigned (anonymous) request.-
response-content-type
-
response-content-language
-
response-expires
-
response-cache-control
-
response-content-disposition
-
response-content-encoding
-
- Overriding Response Header Values
-
If both of the
If-Match
andIf-Unmodified-Since
headers are present in the request as follows:If-Match
condition evaluates totrue
, and;If-Unmodified-Since
condition evaluates tofalse
; then, S3 returns 200 OK and the data requested.If both of the
If-None-Match
andIf-Modified-Since
headers are present in the request as follows:If-None-Match
condition evaluates tofalse
, and;If-Modified-Since
condition evaluates totrue
; then, S3 returns 304 Not Modified response code.For more information about conditional requests, see RFC 7232.
The following operations are related to
GetObject
:getObjectAcl(params = {}, callback) ⇒ AWS.Request
Returns the access control list (ACL) of an object. To use this operation, you must have
s3:GetObjectAcl
permissions orREAD_ACP
access to the object. For more information, see Mapping of ACL permissions and access policy permissions in the Amazon S3 User GuideThis action is not supported by Amazon S3 on Outposts.
By default, GET returns ACL information about the current version of an object. To return ACL information about a different version, use the versionId subresource.
Note: If your bucket uses the bucket owner enforced setting for S3 Object Ownership, requests to read ACLs are still supported and return thebucket-owner-full-control
ACL with the owner being the account that created the bucket. For more information, see Controlling object ownership and disabling ACLs in the Amazon S3 User Guide.The following operations are related to
GetObjectAcl
:getObjectLegalHold(params = {}, callback) ⇒ AWS.Request
Gets an object's current legal hold status. For more information, see Locking Objects.
This action is not supported by Amazon S3 on Outposts.
The following action is related to
GetObjectLegalHold
:getObjectLockConfiguration(params = {}, callback) ⇒ AWS.Request
Gets the Object Lock configuration for a bucket. The rule specified in the Object Lock configuration will be applied by default to every new object placed in the specified bucket. For more information, see Locking Objects.
The following action is related to
GetObjectLockConfiguration
:getObjectRetention(params = {}, callback) ⇒ AWS.Request
Retrieves an object's retention settings. For more information, see Locking Objects.
This action is not supported by Amazon S3 on Outposts.
The following action is related to
GetObjectRetention
:getObjectTagging(params = {}, callback) ⇒ AWS.Request
Returns the tag-set of an object. You send the GET request against the tagging subresource associated with the object.
To use this operation, you must have permission to perform the
s3:GetObjectTagging
action. By default, the GET action returns information about current version of an object. For a versioned bucket, you can have multiple versions of an object in your bucket. To retrieve tags of any other version, use the versionId query parameter. You also need permission for thes3:GetObjectVersionTagging
action.By default, the bucket owner has this permission and can grant this permission to others.
For information about the Amazon S3 object tagging feature, see Object Tagging.
The following actions are related to
GetObjectTagging
:getPublicAccessBlock(params = {}, callback) ⇒ AWS.Request
Retrieves the
PublicAccessBlock
configuration for an Amazon S3 bucket. To use this operation, you must have thes3:GetBucketPublicAccessBlock
permission. For more information about Amazon S3 permissions, see Specifying Permissions in a Policy.When Amazon S3 evaluates the
PublicAccessBlock
configuration for a bucket or an object, it checks thePublicAccessBlock
configuration for both the bucket (or the bucket that contains the object) and the bucket owner's account. If thePublicAccessBlock
settings are different between the bucket and the account, Amazon S3 uses the most restrictive combination of the bucket-level and account-level settings.For more information about when Amazon S3 considers a bucket or an object public, see The Meaning of "Public".
The following operations are related to
GetPublicAccessBlock
:getSignedUrl(operation, params, callback) ⇒ String?
Note:You must ensure that you have static or previously resolved credentials if you call this method synchronously (with no callback), otherwise it may not properly sign the request. If you cannot guarantee this (you are using an asynchronous credential provider, i.e., EC2 IAM roles), you should always call this method with an asynchronous callback.
Note:Not all operation parameters are supported when using pre-signed URLs. Certain parameters, such as
SSECustomerKey
,ACL
,Expires
,ContentLength
, orTagging
must be provided as headers when sending a request. If you are using pre-signed URLs to upload from a browser and need to use these fields, see createPresignedPost().Note:The default signer allows altering the request by adding corresponding headers to set some parameters (e.g. Range) and these added parameters won't be signed. You must use signatureVersion v4 to to include these parameters in the signed portion of the URL and enforce exact matching between headers and signed params in the URL.
Note:This operation cannot be used with a promise. See note above regarding asynchronous credentials and use with a callback.
Get a pre-signed URL for a given operation name.
getSignedUrlPromise() ⇒ Promise
Note:Not all operation parameters are supported when using pre-signed URLs. Certain parameters, such as
SSECustomerKey
,ACL
,Expires
,ContentLength
, orTagging
must be provided as headers when sending a request. If you are using pre-signed URLs to upload from a browser and need to use these fields, see createPresignedPost().Returns a 'thenable' promise that will be resolved with a pre-signed URL for a given operation name.
Two callbacks can be provided to the
then
method on the returned promise. The first callback will be called if the promise is fulfilled, and the second callback will be called if the promise is rejected.headBucket(params = {}, callback) ⇒ AWS.Request
This action is useful to determine if a bucket exists and you have permission to access it. The action returns a
200 OK
if the bucket exists and you have permission to access it.If the bucket does not exist or you do not have permission to access it, the
HEAD
request returns a generic400 Bad Request
,403 Forbidden
or404 Not Found
code. A message body is not included, so you cannot determine the exception beyond these error codes.To use this operation, you must have permissions to perform the
s3:ListBucket
action. The bucket owner has this permission by default and can grant this permission to others. For more information about permissions, see Permissions Related to Bucket Subresource Operations and Managing Access Permissions to Your Amazon S3 Resources.To use this API operation against an access point, you must provide the alias of the access point in place of the bucket name or specify the access point ARN. When using the access point ARN, you must direct requests to the access point hostname. The access point hostname takes the form AccessPointName-AccountId.s3-accesspoint.Region.amazonaws.com. When using the Amazon Web Services SDKs, you provide the ARN in place of the bucket name. For more information, see Using access points.
To use this API operation against an Object Lambda access point, provide the alias of the Object Lambda access point in place of the bucket name. If the Object Lambda access point alias in a request is not valid, the error code
InvalidAccessPointAliasError
is returned. For more information aboutInvalidAccessPointAliasError
, see List of Error Codes.headObject(params = {}, callback) ⇒ AWS.Request
The HEAD action retrieves metadata from an object without returning the object itself. This action is useful if you're only interested in an object's metadata. To use HEAD, you must have READ access to the object.
A
HEAD
request has the same options as aGET
action on an object. The response is identical to theGET
response except that there is no response body. Because of this, if theHEAD
request generates an error, it returns a generic400 Bad Request
,403 Forbidden
or404 Not Found
code. It is not possible to retrieve the exact exception beyond these error codes.If you encrypt an object by using server-side encryption with customer-provided encryption keys (SSE-C) when you store the object in Amazon S3, then when you retrieve the metadata from the object, you must use the following headers:
-
x-amz-server-side-encryption-customer-algorithm
-
x-amz-server-side-encryption-customer-key
-
x-amz-server-side-encryption-customer-key-MD5
For more information about SSE-C, see Server-Side Encryption (Using Customer-Provided Encryption Keys).
Note:- Encryption request headers, like
x-amz-server-side-encryption
, should not be sent for GET requests if your object uses server-side encryption with KMS keys (SSE-KMS) or server-side encryption with Amazon S3–managed encryption keys (SSE-S3). If your object does use these types of keys, you’ll get an HTTP 400 BadRequest error. - The last modified property in this case is the creation date of the object.
Request headers are limited to 8 KB in size. For more information, see Common Request Headers.
Consider the following when using request headers:
-
Consideration 1 – If both of the
If-Match
andIf-Unmodified-Since
headers are present in the request as follows:-
If-Match
condition evaluates totrue
, and; -
If-Unmodified-Since
condition evaluates tofalse
;
Then Amazon S3 returns
200 OK
and the data requested. -
-
Consideration 2 – If both of the
If-None-Match
andIf-Modified-Since
headers are present in the request as follows:-
If-None-Match
condition evaluates tofalse
, and; -
If-Modified-Since
condition evaluates totrue
;
Then Amazon S3 returns the
304 Not Modified
response code. -
For more information about conditional requests, see RFC 7232.
- Permissions
-
You need the relevant read object (or version) permission for this operation. For more information, see Actions, resources, and condition keys for Amazon S3. If the object you request does not exist, the error Amazon S3 returns depends on whether you also have the s3:ListBucket permission.
-
If you have the
s3:ListBucket
permission on the bucket, Amazon S3 returns an HTTP status code 404 ("no such key") error. -
If you don’t have the
s3:ListBucket
permission, Amazon S3 returns an HTTP status code 403 ("access denied") error.
-
The following actions are related to
HeadObject
:listBuckets(params = {}, callback) ⇒ AWS.Request
Returns a list of all buckets owned by the authenticated sender of the request. To use this operation, you must have the
s3:ListAllMyBuckets
permission.For information about Amazon S3 buckets, see Creating, configuring, and working with Amazon S3 buckets.
Note: This operation cannot be used in a browser. S3 does not support CORS on this operation.
listBucketsExtended(params = {}, callback) ⇒ AWS.Request
Returns a list of all buckets owned by the authenticated sender of the request, along with the LocationConstraint describing the region that the bucket resides in and the bucket's storage tier.
listMultipartUploads(params = {}, callback) ⇒ AWS.Request
This action lists in-progress multipart uploads. An in-progress multipart upload is a multipart upload that has been initiated using the Initiate Multipart Upload request, but has not yet been completed or aborted.
This action returns at most 1,000 multipart uploads in the response. 1,000 multipart uploads is the maximum number of uploads a response can include, which is also the default value. You can further limit the number of uploads in a response by specifying the
max-uploads
parameter in the response. If additional multipart uploads satisfy the list criteria, the response will contain anIsTruncated
element with the value true. To list the additional multipart uploads, use thekey-marker
andupload-id-marker
request parameters.In the response, the uploads are sorted by key. If your application has initiated more than one multipart upload using the same object key, then uploads in the response are first sorted by key. Additionally, uploads are sorted in ascending order within each key by the upload initiation time.
For more information on multipart uploads, see Uploading Objects Using Multipart Upload.
For information on permissions required to use the multipart upload API, see Multipart Upload and Permissions.
The following operations are related to
ListMultipartUploads
:listObjects(params = {}, callback) ⇒ AWS.Request
Returns some or all (up to 1,000) of the objects in a bucket. You can use the request parameters as selection criteria to return a subset of the objects in a bucket. A 200 OK response can contain valid or invalid XML. Be sure to design your application to parse the contents of the response and handle it appropriately.
This action has been revised. We recommend that you use the newer version, ListObjectsV2, when developing applications. For backward compatibility, Amazon S3 continues to support
ListObjects
.The following operations are related to
ListObjects
:listObjectsV2(params = {}, callback) ⇒ AWS.Request
Returns some or all (up to 1,000) of the objects in a bucket with each request. You can use the request parameters as selection criteria to return a subset of the objects in a bucket. A
200 OK
response can contain valid or invalid XML. Make sure to design your application to parse the contents of the response and handle it appropriately. Objects are returned sorted in an ascending order of the respective key names in the list. For more information about listing objects, see Listing object keys programmaticallyTo use this operation, you must have READ access to the bucket.
To use this action in an Identity and Access Management (IAM) policy, you must have permissions to perform the
s3:ListBucket
action. The bucket owner has this permission by default and can grant this permission to others. For more information about permissions, see Permissions Related to Bucket Subresource Operations and Managing Access Permissions to Your Amazon S3 Resources.This section describes the latest revision of this action. We recommend that you use this revised API for application development. For backward compatibility, Amazon S3 continues to support the prior version of this API, ListObjects.
To get a list of your buckets, see ListBuckets.
The following operations are related to
ListObjectsV2
:listObjectVersions(params = {}, callback) ⇒ AWS.Request
Returns metadata about all versions of the objects in a bucket. You can also use request parameters as selection criteria to return metadata about a subset of all the object versions.
To use this operation, you must have permissions to perform the
s3:ListBucketVersions
action. Be aware of the name difference.Note: A 200 OK response can contain valid or invalid XML. Make sure to design your application to parse the contents of the response and handle it appropriately.To use this operation, you must have READ access to the bucket.
This action is not supported by Amazon S3 on Outposts.
The following operations are related to
ListObjectVersions
:listParts(params = {}, callback) ⇒ AWS.Request
Lists the parts that have been uploaded for a specific multipart upload. This operation must include the upload ID, which you obtain by sending the initiate multipart upload request (see CreateMultipartUpload). This request returns a maximum of 1,000 uploaded parts. The default number of parts returned is 1,000 parts. You can restrict the number of parts returned by specifying the
max-parts
request parameter. If your multipart upload consists of more than 1,000 parts, the response returns anIsTruncated
field with the value of true, and aNextPartNumberMarker
element. In subsequentListParts
requests you can include the part-number-marker query string parameter and set its value to theNextPartNumberMarker
field value from the previous response.If the upload was created using a checksum algorithm, you will need to have permission to the
kms:Decrypt
action for the request to succeed.For more information on multipart uploads, see Uploading Objects Using Multipart Upload.
For information on permissions required to use the multipart upload API, see Multipart Upload and Permissions.
The following operations are related to
ListParts
:putBucketAcl(params = {}, callback) ⇒ AWS.Request
Sets the permissions on an existing bucket using access control lists (ACL). For more information, see Using ACLs. To set the ACL of a bucket, you must have
WRITE_ACP
permission.You can use one of the following two ways to set a bucket's permissions:
-
Specify the ACL in the request body
-
Specify permissions using request headers
Note: You cannot specify access permission using both the body and the request headers.Depending on your application needs, you may choose to set the ACL on a bucket using either the request body or the headers. For example, if you have an existing application that updates a bucket ACL using the request body, then you can continue to use that approach.
If your bucket uses the bucket owner enforced setting for S3 Object Ownership, ACLs are disabled and no longer affect permissions. You must use policies to grant access to your bucket and the objects in it. Requests to set ACLs or update ACLs fail and return the
AccessControlListNotSupported
error code. Requests to read ACLs are still supported. For more information, see Controlling object ownership in the Amazon S3 User Guide.- Permissions
-
You can set access permissions using one of the following methods:
-
Specify a canned ACL with the
x-amz-acl
request header. Amazon S3 supports a set of predefined ACLs, known as canned ACLs. Each canned ACL has a predefined set of grantees and permissions. Specify the canned ACL name as the value ofx-amz-acl
. If you use this header, you cannot use other access control-specific headers in your request. For more information, see Canned ACL. -
Specify access permissions explicitly with the
x-amz-grant-read
,x-amz-grant-read-acp
,x-amz-grant-write-acp
, andx-amz-grant-full-control
headers. When using these headers, you specify explicit access permissions and grantees (Amazon Web Services accounts or Amazon S3 groups) who will receive the permission. If you use these ACL-specific headers, you cannot use thex-amz-acl
header to set a canned ACL. These parameters map to the set of permissions that Amazon S3 supports in an ACL. For more information, see Access Control List (ACL) Overview.You specify each grantee as a type=value pair, where the type is one of the following:
-
id
– if the value specified is the canonical user ID of an Amazon Web Services account -
uri
– if you are granting permissions to a predefined group -
emailAddress
– if the value specified is the email address of an Amazon Web Services accountNote: Using email addresses to specify a grantee is only supported in the following Amazon Web Services Regions:- US East (N. Virginia)
- US West (N. California)
- US West (Oregon)
- Asia Pacific (Singapore)
- Asia Pacific (Sydney)
- Asia Pacific (Tokyo)
- Europe (Ireland)
- South America (São Paulo)
For example, the following
x-amz-grant-write
header grants create, overwrite, and delete objects permission to LogDelivery group predefined by Amazon S3 and two Amazon Web Services accounts identified by their email addresses.x-amz-grant-write: uri="http://acs.amazonaws.com/groups/s3/LogDelivery", id="111122223333", id="555566667777"
-
You can use either a canned ACL or specify access permissions explicitly. You cannot do both.
-
- Grantee Values
-
You can specify the person (grantee) to whom you're assigning access rights (using request elements) in the following ways:
-
By the person's ID:
<Grantee xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="CanonicalUser"><ID><>ID<></ID><DisplayName><>GranteesEmail<></DisplayName> </Grantee>
DisplayName is optional and ignored in the request
-
By URI:
<Grantee xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="Group"><URI><>http://acs.amazonaws.com/groups/global/AuthenticatedUsers<></URI></Grantee>
-
By Email address:
<Grantee xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="AmazonCustomerByEmail"><EmailAddress><>Grantees@email.com<></EmailAddress>&</Grantee>
The grantee is resolved to the CanonicalUser and, in a response to a GET Object acl request, appears as the CanonicalUser.
Note: Using email addresses to specify a grantee is only supported in the following Amazon Web Services Regions:- US East (N. Virginia)
- US West (N. California)
- US West (Oregon)
- Asia Pacific (Singapore)
- Asia Pacific (Sydney)
- Asia Pacific (Tokyo)
- Europe (Ireland)
- South America (São Paulo)
-
The following operations are related to
PutBucketAcl
:putBucketCors(params = {}, callback) ⇒ AWS.Request
Sets the
cors
configuration for your bucket. If the configuration exists, Amazon S3 replaces it.To use this operation, you must be allowed to perform the
s3:PutBucketCORS
action. By default, the bucket owner has this permission and can grant it to others.You set this configuration on a bucket so that the bucket can service cross-origin requests. For example, you might want to enable a request whose origin is
http://www.example.com
to access your Amazon S3 bucket atmy.example.bucket.com
by using the browser'sXMLHttpRequest
capability.To enable cross-origin resource sharing (CORS) on a bucket, you add the
cors
subresource to the bucket. Thecors
subresource is an XML document in which you configure rules that identify origins and the HTTP methods that can be executed on your bucket. The document is limited to 64 KB in size.When Amazon S3 receives a cross-origin request (or a pre-flight OPTIONS request) against a bucket, it evaluates the
cors
configuration on the bucket and uses the firstCORSRule
rule that matches the incoming browser request to enable a cross-origin request. For a rule to match, the following conditions must be met:-
The request's
Origin
header must matchAllowedOrigin
elements. -
The request method (for example, GET, PUT, HEAD, and so on) or the
Access-Control-Request-Method
header in case of a pre-flightOPTIONS
request must be one of theAllowedMethod
elements. -
Every header specified in the
Access-Control-Request-Headers
request header of a pre-flight request must match anAllowedHeader
element.
For more information about CORS, go to Enabling Cross-Origin Resource Sharing in the Amazon S3 User Guide.
The following operations are related to
PutBucketCors
:putBucketLifecycle(params = {}, callback) ⇒ AWS.Request
For an updated version of this API, see PutBucketLifecycleConfiguration. This version has been deprecated. Existing lifecycle configurations will work. For new lifecycle configurations, use the updated API.
Creates a new lifecycle configuration for the bucket or replaces an existing lifecycle configuration. For information about lifecycle configuration, see Object Lifecycle Management in the Amazon S3 User Guide.
By default, all Amazon S3 resources, including buckets, objects, and related subresources (for example, lifecycle configuration and website configuration) are private. Only the resource owner, the Amazon Web Services account that created the resource, can access it. The resource owner can optionally grant access permissions to others by writing an access policy. For this operation, users must get the
s3:PutLifecycleConfiguration
permission.You can also explicitly deny permissions. Explicit denial also supersedes any other permissions. If you want to prevent users or accounts from removing or deleting objects from your bucket, you must deny them permissions for the following actions:
-
s3:DeleteObject
-
s3:DeleteObjectVersion
-
s3:PutLifecycleConfiguration
For more information about permissions, see Managing Access Permissions to your Amazon S3 Resources in the Amazon S3 User Guide.
For more examples of transitioning objects to storage classes such as STANDARD_IA or ONEZONE_IA, see Examples of Lifecycle Configuration.
The following operations are related to
PutBucketLifecycle
:-
GetBucketLifecycle(Deprecated)
-
By default, a resource owner—in this case, a bucket owner, which is the Amazon Web Services account that created the bucket—can perform any of the operations. A resource owner can also grant others permission to perform the operation. For more information, see the following topics in the Amazon S3 User Guide:
putBucketLifecycleConfiguration(params = {}, callback) ⇒ AWS.Request
Creates a new lifecycle configuration for the bucket or replaces an existing lifecycle configuration. Keep in mind that this will overwrite an existing lifecycle configuration, so if you want to retain any configuration details, they must be included in the new lifecycle configuration. For information about lifecycle configuration, see Managing your storage lifecycle.
Note: Bucket lifecycle configuration now supports specifying a lifecycle rule using an object key name prefix, one or more object tags, or a combination of both. Accordingly, this section describes the latest API. The previous version of the API supported filtering based only on an object key name prefix, which is supported for backward compatibility. For the related API description, see PutBucketLifecycle.- Rules
-
You specify the lifecycle configuration in your request body. The lifecycle configuration is specified as XML consisting of one or more rules. An Amazon S3 Lifecycle configuration can have up to 1,000 rules. This limit is not adjustable. Each rule consists of the following:
-
Filter identifying a subset of objects to which the rule applies. The filter can be based on a key name prefix, object tags, or a combination of both.
-
Status whether the rule is in effect.
-
One or more lifecycle transition and expiration actions that you want Amazon S3 to perform on the objects identified by the filter. If the state of your bucket is versioning-enabled or versioning-suspended, you can have many versions of the same object (one current version and zero or more noncurrent versions). Amazon S3 provides predefined actions that you can specify for current and noncurrent object versions.
For more information, see Object Lifecycle Management and Lifecycle Configuration Elements.
-
- Permissions
-
By default, all Amazon S3 resources are private, including buckets, objects, and related subresources (for example, lifecycle configuration and website configuration). Only the resource owner (that is, the Amazon Web Services account that created it) can access the resource. The resource owner can optionally grant access permissions to others by writing an access policy. For this operation, a user must get the
s3:PutLifecycleConfiguration
permission.You can also explicitly deny permissions. Explicit deny also supersedes any other permissions. If you want to block users or accounts from removing or deleting objects from your bucket, you must deny them permissions for the following actions:
-
s3:DeleteObject
-
s3:DeleteObjectVersion
-
s3:PutLifecycleConfiguration
For more information about permissions, see Managing Access Permissions to Your Amazon S3 Resources.
-
The following operations are related to
PutBucketLifecycleConfiguration
:putBucketProtectionConfiguration(params = {}, callback) ⇒ AWS.Request
Sets the protection configuration of an existing bucket.
putBucketReplication(params = {}, callback) ⇒ AWS.Request
Creates a replication configuration or replaces an existing one. For more information, see Replication in the Amazon S3 User Guide.
Specify the replication configuration in the request body. In the replication configuration, you provide the name of the destination bucket or buckets where you want Amazon S3 to replicate objects, the IAM role that Amazon S3 can assume to replicate objects on your behalf, and other relevant information.
A replication configuration must include at least one rule, and can contain a maximum of 1,000. Each rule identifies a subset of objects to replicate by filtering the objects in the source bucket. To choose additional subsets of objects to replicate, add a rule for each subset.
To specify a subset of the objects in the source bucket to apply a replication rule to, add the Filter element as a child of the Rule element. You can filter objects based on an object key prefix, one or more object tags, or both. When you add the Filter element in the configuration, you must also add the following elements:
DeleteMarkerReplication
,Status
, andPriority
.Note: If you are using an earlier version of the replication configuration, Amazon S3 handles replication of delete markers differently. For more information, see Backward Compatibility.For information about enabling versioning on a bucket, see Using Versioning.
- Handling Replication of Encrypted Objects
-
By default, Amazon S3 doesn't replicate objects that are stored at rest using server-side encryption with KMS keys. To replicate Amazon Web Services KMS-encrypted objects, add the following:
SourceSelectionCriteria
,SseKmsEncryptedObjects
,Status
,EncryptionConfiguration
, andReplicaKmsKeyID
. For information about replication configuration, see Replicating Objects Created with SSE Using KMS keys.For information on
PutBucketReplication
errors, see List of replication-related error codes - Permissions
-
To create a
PutBucketReplication
request, you must haves3:PutReplicationConfiguration
permissions for the bucket.By default, a resource owner, in this case the Amazon Web Services account that created the bucket, can perform this operation. The resource owner can also grant others permissions to perform the operation. For more information about permissions, see Specifying Permissions in a Policy and Managing Access Permissions to Your Amazon S3 Resources.
Note: To perform this operation, the user or role performing the action must have the iam:PassRole permission.
The following operations are related to
PutBucketReplication
:putBucketTagging(params = {}, callback) ⇒ AWS.Request
Sets the tags for a bucket.
Use tags to organize your Amazon Web Services bill to reflect your own cost structure. To do this, sign up to get your Amazon Web Services account bill with tag key values included. Then, to see the cost of combined resources, organize your billing information according to resources with the same tag key values. For example, you can tag several resources with a specific application name, and then organize your billing information to see the total cost of that application across several services. For more information, see Cost Allocation and Tagging and Using Cost Allocation in Amazon S3 Bucket Tags.
Note: When this operation sets the tags for a bucket, it will overwrite any current tags the bucket already has. You cannot use this operation to add tags to an existing list of tags.To use this operation, you must have permissions to perform the
s3:PutBucketTagging
action. The bucket owner has this permission by default and can grant this permission to others. For more information about permissions, see Permissions Related to Bucket Subresource Operations and Managing Access Permissions to Your Amazon S3 Resources.PutBucketTagging
has the following special errors:-
Error code:
InvalidTagError
-
Description: The tag provided was not a valid tag. This error can occur if the tag did not pass input validation. For information about tag restrictions, see User-Defined Tag Restrictions and Amazon Web Services-Generated Cost Allocation Tag Restrictions.
-
-
Error code:
MalformedXMLError
-
Description: The XML provided does not match the schema.
-
-
Error code:
OperationAbortedError
-
Description: A conflicting conditional action is currently in progress against this resource. Please try again.
-
-
Error code:
InternalError
-
Description: The service was unable to apply the provided tag to the bucket.
-
The following operations are related to
PutBucketTagging
:putBucketVersioning(params = {}, callback) ⇒ AWS.Request
Sets the versioning state of an existing bucket.
You can set the versioning state with one of the following values:
Enabled—Enables versioning for the objects in the bucket. All objects added to the bucket receive a unique version ID.
Suspended—Disables versioning for the objects in the bucket. All objects added to the bucket receive the version ID null.
If the versioning state has never been set on a bucket, it has no versioning state; a GetBucketVersioning request does not return a versioning state value.
In order to enable MFA Delete, you must be the bucket owner. If you are the bucket owner and want to enable MFA Delete in the bucket versioning configuration, you must include the
x-amz-mfa request
header and theStatus
and theMfaDelete
request elements in a request to set the versioning state of the bucket.If you have an object expiration lifecycle configuration in your non-versioned bucket and you want to maintain the same permanent delete behavior when you enable versioning, you must add a noncurrent expiration policy. The noncurrent expiration lifecycle configuration will manage the deletes of the noncurrent object versions in the version-enabled bucket. (A version-enabled bucket maintains one current and zero or more noncurrent object versions.) For more information, see Lifecycle and Versioning.
The following operations are related to
PutBucketVersioning
:putBucketWebsite(params = {}, callback) ⇒ AWS.Request
Sets the configuration of the website that is specified in the
website
subresource. To configure a bucket as a website, you can add this subresource on the bucket with website configuration information such as the file name of the index document and any redirect rules. For more information, see Hosting Websites on Amazon S3.This PUT action requires the
S3:PutBucketWebsite
permission. By default, only the bucket owner can configure the website attached to a bucket; however, bucket owners can allow other users to set the website configuration by writing a bucket policy that grants them theS3:PutBucketWebsite
permission.To redirect all website requests sent to the bucket's website endpoint, you add a website configuration with the following elements. Because all requests are sent to another website, you don't need to provide index document name for the bucket.
-
WebsiteConfiguration
-
RedirectAllRequestsTo
-
HostName
-
Protocol
If you want granular control over redirects, you can use the following elements to add routing rules that describe conditions for redirecting requests and information about the redirect destination. In this case, the website configuration must provide an index document for the bucket, because some requests might not be redirected.
-
WebsiteConfiguration
-
IndexDocument
-
Suffix
-
ErrorDocument
-
Key
-
RoutingRules
-
RoutingRule
-
Condition
-
HttpErrorCodeReturnedEquals
-
KeyPrefixEquals
-
Redirect
-
Protocol
-
HostName
-
ReplaceKeyPrefixWith
-
ReplaceKeyWith
-
HttpRedirectCode
Amazon S3 has a limitation of 50 routing rules per website configuration. If you require more than 50 routing rules, you can use object redirect. For more information, see Configuring an Object Redirect in the Amazon S3 User Guide.
putObject(params = {}, callback) ⇒ AWS.Request
Adds an object to a bucket. You must have WRITE permissions on a bucket to add an object to it.
Note: Amazon S3 never adds partial objects; if you receive a success response, Amazon S3 added the entire object to the bucket. You cannot usePutObject
to only update a single piece of metadata for an existing object. You must put the entire object with updated metadata if you want to update some values.Amazon S3 is a distributed system. If it receives multiple write requests for the same object simultaneously, it overwrites all but the last object written. To prevent objects from being deleted or overwritten, you can use Amazon S3 Object Lock.
To ensure that data is not corrupted traversing the network, use the
Content-MD5
header. When you use this header, Amazon S3 checks the object against the provided MD5 value and, if they do not match, returns an error. Additionally, you can calculate the MD5 while putting an object to Amazon S3 and compare the returned ETag to the calculated MD5 value.Note:- To successfully complete the
PutObject
request, you must have thes3:PutObject
in your IAM permissions. - To successfully change the objects acl of your
PutObject
request, you must have thes3:PutObjectAcl
in your IAM permissions. - To successfully set the tag-set with your
PutObject
request, you must have thes3:PutObjectTagging
in your IAM permissions. - The
Content-MD5
header is required for any request to upload an object with a retention period configured using Amazon S3 Object Lock. For more information about Amazon S3 Object Lock, see Amazon S3 Object Lock Overview in the Amazon S3 User Guide.
You have three mutually exclusive options to protect data using server-side encryption in Amazon S3, depending on how you choose to manage the encryption keys. Specifically, the encryption key options are Amazon S3 managed keys (SSE-S3), Amazon Web Services KMS keys (SSE-KMS), and customer-provided keys (SSE-C). Amazon S3 encrypts data with server-side encryption by using Amazon S3 managed keys (SSE-S3) by default. You can optionally tell Amazon S3 to encrypt data at by rest using server-side encryption with other key options. For more information, see Using Server-Side Encryption.
When adding a new object, you can use headers to grant ACL-based permissions to individual Amazon Web Services accounts or to predefined groups defined by Amazon S3. These permissions are then added to the ACL on the object. By default, all objects are private. Only the owner has full access control. For more information, see Access Control List (ACL) Overview and Managing ACLs Using the REST API.
If the bucket that you're uploading objects to uses the bucket owner enforced setting for S3 Object Ownership, ACLs are disabled and no longer affect permissions. Buckets that use this setting only accept PUT requests that don't specify an ACL or PUT requests that specify bucket owner full control ACLs, such as the
bucket-owner-full-control
canned ACL or an equivalent form of this ACL expressed in the XML format. PUT requests that contain other ACLs (for example, custom grants to certain Amazon Web Services accounts) fail and return a400
error with the error codeAccessControlListNotSupported
. For more information, see Controlling ownership of objects and disabling ACLs in the Amazon S3 User Guide.Note: If your bucket uses the bucket owner enforced setting for Object Ownership, all objects written to the bucket by any account will be owned by the bucket owner.By default, Amazon S3 uses the STANDARD Storage Class to store newly created objects. The STANDARD storage class provides high durability and high availability. Depending on performance needs, you can specify a different Storage Class. Amazon S3 on Outposts only uses the OUTPOSTS Storage Class. For more information, see Storage Classes in the Amazon S3 User Guide.
If you enable versioning for a bucket, Amazon S3 automatically generates a unique version ID for the object being stored. Amazon S3 returns this ID in the response. When you enable versioning for a bucket, if Amazon S3 receives multiple write requests for the same object simultaneously, it stores all of the objects. For more information about versioning, see Adding Objects to Versioning-Enabled Buckets. For information about returning the versioning state of a bucket, see GetBucketVersioning.
For more information about related Amazon S3 APIs, see the following:
putObjectAcl(params = {}, callback) ⇒ AWS.Request
Uses the
acl
subresource to set the access control list (ACL) permissions for a new or existing object in an S3 bucket. You must haveWRITE_ACP
permission to set the ACL of an object. For more information, see What permissions can I grant? in the Amazon S3 User Guide.This action is not supported by Amazon S3 on Outposts.
Depending on your application needs, you can choose to set the ACL on an object using either the request body or the headers. For example, if you have an existing application that updates a bucket ACL using the request body, you can continue to use that approach. For more information, see Access Control List (ACL) Overview in the Amazon S3 User Guide.
If your bucket uses the bucket owner enforced setting for S3 Object Ownership, ACLs are disabled and no longer affect permissions. You must use policies to grant access to your bucket and the objects in it. Requests to set ACLs or update ACLs fail and return the
AccessControlListNotSupported
error code. Requests to read ACLs are still supported. For more information, see Controlling object ownership in the Amazon S3 User Guide.- Permissions
-
You can set access permissions using one of the following methods:
-
Specify a canned ACL with the
x-amz-acl
request header. Amazon S3 supports a set of predefined ACLs, known as canned ACLs. Each canned ACL has a predefined set of grantees and permissions. Specify the canned ACL name as the value ofx-amz-ac
l. If you use this header, you cannot use other access control-specific headers in your request. For more information, see Canned ACL. -
Specify access permissions explicitly with the
x-amz-grant-read
,x-amz-grant-read-acp
,x-amz-grant-write-acp
, andx-amz-grant-full-control
headers. When using these headers, you specify explicit access permissions and grantees (Amazon Web Services accounts or Amazon S3 groups) who will receive the permission. If you use these ACL-specific headers, you cannot usex-amz-acl
header to set a canned ACL. These parameters map to the set of permissions that Amazon S3 supports in an ACL. For more information, see Access Control List (ACL) Overview.You specify each grantee as a type=value pair, where the type is one of the following:
-
id
– if the value specified is the canonical user ID of an Amazon Web Services account -
uri
– if you are granting permissions to a predefined group -
emailAddress
– if the value specified is the email address of an Amazon Web Services accountNote: Using email addresses to specify a grantee is only supported in the following Amazon Web Services Regions:- US East (N. Virginia)
- US West (N. California)
- US West (Oregon)
- Asia Pacific (Singapore)
- Asia Pacific (Sydney)
- Asia Pacific (Tokyo)
- Europe (Ireland)
- South America (São Paulo)
For example, the following
x-amz-grant-read
header grants list objects permission to the two Amazon Web Services accounts identified by their email addresses.x-amz-grant-read: emailAddress="xyz@amazon.com", emailAddress="abc@amazon.com"
-
You can use either a canned ACL or specify access permissions explicitly. You cannot do both.
-
- Grantee Values
-
You can specify the person (grantee) to whom you're assigning access rights (using request elements) in the following ways:
-
By the person's ID:
<Grantee xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="CanonicalUser"><ID><>ID<></ID><DisplayName><>GranteesEmail<></DisplayName> </Grantee>
DisplayName is optional and ignored in the request.
-
By URI:
<Grantee xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="Group"><URI><>http://acs.amazonaws.com/groups/global/AuthenticatedUsers<></URI></Grantee>
-
By Email address:
<Grantee xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="AmazonCustomerByEmail"><EmailAddress><>Grantees@email.com<></EmailAddress>lt;/Grantee>
The grantee is resolved to the CanonicalUser and, in a response to a GET Object acl request, appears as the CanonicalUser.
Note: Using email addresses to specify a grantee is only supported in the following Amazon Web Services Regions:- US East (N. Virginia)
- US West (N. California)
- US West (Oregon)
- Asia Pacific (Singapore)
- Asia Pacific (Sydney)
- Asia Pacific (Tokyo)
- Europe (Ireland)
- South America (São Paulo)
-
- Versioning
-
The ACL of an object is set at the object version level. By default, PUT sets the ACL of the current version of an object. To set the ACL of a different version, use the
versionId
subresource.
The following operations are related to
PutObjectAcl
:putObjectLegalHold(params = {}, callback) ⇒ AWS.Request
Applies a legal hold configuration to the specified object. For more information, see Locking Objects.
This action is not supported by Amazon S3 on Outposts.
putObjectLockConfiguration(params = {}, callback) ⇒ AWS.Request
Places an Object Lock configuration on the specified bucket. The rule specified in the Object Lock configuration will be applied by default to every new object placed in the specified bucket. For more information, see Locking Objects.
Note:- The
DefaultRetention
settings require both a mode and a period. - The
DefaultRetention
period can be eitherDays
orYears
but you must select one. You cannot specifyDays
andYears
at the same time. - You can only enable Object Lock for new buckets. If you want to turn on Object Lock for an existing bucket, contact Amazon Web Services Support.
putObjectRetention(params = {}, callback) ⇒ AWS.Request
Places an Object Retention configuration on an object. For more information, see Locking Objects. Users or accounts require the
s3:PutObjectRetention
permission in order to place an Object Retention configuration on objects. Bypassing a Governance Retention configuration requires thes3:BypassGovernanceRetention
permission.This action is not supported by Amazon S3 on Outposts.
putObjectTagging(params = {}, callback) ⇒ AWS.Request
Sets the supplied tag-set to an object that already exists in a bucket.
A tag is a key-value pair. You can associate tags with an object by sending a PUT request against the tagging subresource that is associated with the object. You can retrieve tags by sending a GET request. For more information, see GetObjectTagging.
For tagging-related restrictions related to characters and encodings, see Tag Restrictions. Note that Amazon S3 limits the maximum number of tags to 10 tags per object.
To use this operation, you must have permission to perform the
s3:PutObjectTagging
action. By default, the bucket owner has this permission and can grant this permission to others.To put tags of any other version, use the
versionId
query parameter. You also need permission for thes3:PutObjectVersionTagging
action.For information about the Amazon S3 object tagging feature, see Object Tagging.
PutObjectTagging
has the following special errors:-
-
Code: InvalidTagError
-
Cause: The tag provided was not a valid tag. This error can occur if the tag did not pass input validation. For more information, see Object Tagging.
-
-
-
Code: MalformedXMLError
-
Cause: The XML provided does not match the schema.
-
-
-
Code: OperationAbortedError
-
Cause: A conflicting conditional action is currently in progress against this resource. Please try again.
-
-
-
Code: InternalError
-
Cause: The service was unable to apply the provided tag to the object.
-
The following operations are related to
PutObjectTagging
:putPublicAccessBlock(params = {}, callback) ⇒ AWS.Request
Creates or modifies the
PublicAccessBlock
configuration for an Amazon S3 bucket. To use this operation, you must have thes3:PutBucketPublicAccessBlock
permission. For more information about Amazon S3 permissions, see Specifying Permissions in a Policy.When Amazon S3 evaluates the
PublicAccessBlock
configuration for a bucket or an object, it checks thePublicAccessBlock
configuration for both the bucket (or the bucket that contains the object) and the bucket owner's account. If thePublicAccessBlock
configurations are different between the bucket and the account, Amazon S3 uses the most restrictive combination of the bucket-level and account-level settings.For more information about when Amazon S3 considers a bucket or an object public, see The Meaning of "Public".
The following operations are related to
PutPublicAccessBlock
:restoreObject(params = {}, callback) ⇒ AWS.Request
Restores an archived copy of an object back into Amazon S3
This action is not supported by Amazon S3 on Outposts.
This action performs the following types of requests:
-
select
- Perform a select query on an archived object -
restore an archive
- Restore an archived object
For more information about the
S3
structure in the request body, see the following:-
Managing Access with ACLs in the Amazon S3 User Guide
-
Protecting Data Using Server-Side Encryption in the Amazon S3 User Guide
Define the SQL expression for the
SELECT
type of restoration for your query in the request body'sSelectParameters
structure. You can use expressions like the following examples.-
The following expression returns all records from the specified object.
SELECT * FROM Object
-
Assuming that you are not using any headers for data stored in the object, you can specify columns with positional headers.
SELECT s._1, s._2 FROM Object s WHERE s._3 > 100
-
If you have headers and you set the
fileHeaderInfo
in theCSV
structure in the request body toUSE
, you can specify headers in the query. (If you set thefileHeaderInfo
field toIGNORE
, the first row is skipped for the query.) You cannot mix ordinal positions with header column names.SELECT s.Id, s.FirstName, s.SSN FROM S3Object s
When making a select request, you can also do the following:
-
To expedite your queries, specify the
Expedited
tier. For more information about tiers, see "Restoring Archives," later in this topic. -
Specify details about the data serialization format of both the input object that is being queried and the serialization of the CSV-encoded query results.
The following are additional important facts about the select feature:
-
The output results are new Amazon S3 objects. Unlike archive retrievals, they are stored until explicitly deleted-manually or through a lifecycle configuration.
-
You can issue more than one select request on the same Amazon S3 object. Amazon S3 doesn't duplicate requests, so avoid issuing duplicate requests.
-
Amazon S3 accepts a select request even if the object has already been restored. A select request doesn’t return error response
409
.
- Permissions
-
To use this operation, you must have permissions to perform the
s3:RestoreObject
action. The bucket owner has this permission by default and can grant this permission to others. For more information about permissions, see Permissions Related to Bucket Subresource Operations and Managing Access Permissions to Your Amazon S3 Resources in the Amazon S3 User Guide. - Restoring objects
-
Objects that you archive to the S3 Glacier Flexible Retrieval or S3 Glacier Deep Archive storage class, and S3 Intelligent-Tiering Archive or S3 Intelligent-Tiering Deep Archive tiers, are not accessible in real time. For objects in the S3 Glacier Flexible Retrieval or S3 Glacier Deep Archive storage classes, you must first initiate a restore request, and then wait until a temporary copy of the object is available. If you want a permanent copy of the object, create a copy of it in the Amazon S3 Standard storage class in your S3 bucket. To access an archived object, you must restore the object for the duration (number of days) that you specify. For objects in the Archive Access or Deep Archive Access tiers of S3 Intelligent-Tiering, you must first initiate a restore request, and then wait until the object is moved into the Frequent Access tier.
To restore a specific object version, you can provide a version ID. If you don't provide a version ID, Amazon S3 restores the current version.
When restoring an archived object, you can specify one of the following data access tier options in the
Tier
element of the request body:-
Expedited
- Expedited retrievals allow you to quickly access your data stored in the S3 Glacier Flexible Retrieval storage class or S3 Intelligent-Tiering Archive tier when occasional urgent requests for restoring archives are required. For all but the largest archived objects (250 MB+), data accessed using Expedited retrievals is typically made available within 1–5 minutes. Provisioned capacity ensures that retrieval capacity for Expedited retrievals is available when you need it. Expedited retrievals and provisioned capacity are not available for objects stored in the S3 Glacier Deep Archive storage class or S3 Intelligent-Tiering Deep Archive tier. -
Standard
- Standard retrievals allow you to access any of your archived objects within several hours. This is the default option for retrieval requests that do not specify the retrieval option. Standard retrievals typically finish within 3–5 hours for objects stored in the S3 Glacier Flexible Retrieval storage class or S3 Intelligent-Tiering Archive tier. They typically finish within 12 hours for objects stored in the S3 Glacier Deep Archive storage class or S3 Intelligent-Tiering Deep Archive tier. Standard retrievals are free for objects stored in S3 Intelligent-Tiering. -
Bulk
- Bulk retrievals free for objects stored in the S3 Glacier Flexible Retrieval and S3 Intelligent-Tiering storage classes, enabling you to retrieve large amounts, even petabytes, of data at no cost. Bulk retrievals typically finish within 5–12 hours for objects stored in the S3 Glacier Flexible Retrieval storage class or S3 Intelligent-Tiering Archive tier. Bulk retrievals are also the lowest-cost retrieval option when restoring objects from S3 Glacier Deep Archive. They typically finish within 48 hours for objects stored in the S3 Glacier Deep Archive storage class or S3 Intelligent-Tiering Deep Archive tier.
For more information about archive retrieval options and provisioned capacity for
Expedited
data access, see Restoring Archived Objects in the Amazon S3 User Guide.You can use Amazon S3 restore speed upgrade to change the restore speed to a faster speed while it is in progress. For more information, see Upgrading the speed of an in-progress restore in the Amazon S3 User Guide.
To get the status of object restoration, you can send a
HEAD
request. Operations return thex-amz-restore
header, which provides information about the restoration status, in the response. You can use Amazon S3 event notifications to notify you when a restore is initiated or completed. For more information, see Configuring Amazon S3 Event Notifications in the Amazon S3 User Guide.After restoring an archived object, you can update the restoration period by reissuing the request with a new period. Amazon S3 updates the restoration period relative to the current time and charges only for the request-there are no data transfer charges. You cannot update the restoration period when Amazon S3 is actively processing your current restore request for the object.
If your bucket has a lifecycle configuration with a rule that includes an expiration action, the object expiration overrides the life span that you specify in a restore request. For example, if you restore an object copy for 10 days, but the object is scheduled to expire in 3 days, Amazon S3 deletes the object in 3 days. For more information about lifecycle configuration, see PutBucketLifecycleConfiguration and Object Lifecycle Management in Amazon S3 User Guide.
-
- Responses
-
A successful action returns either the
200 OK
or202 Accepted
status code.-
If the object is not previously restored, then Amazon S3 returns
202 Accepted
in the response. -
If the object is previously restored, Amazon S3 returns
200 OK
in the response.
-
Special errors:
-
Code: RestoreAlreadyInProgress
-
Cause: Object restore is already in progress. (This error does not apply to SELECT type requests.)
-
HTTP Status Code: 409 Conflict
-
SOAP Fault Code Prefix: Client
-
-
-
Code: GlacierExpeditedRetrievalNotAvailable
-
Cause: expedited retrievals are currently not available. Try again later. (Returned if there is insufficient capacity to process the Expedited request. This error applies only to Expedited retrievals and not to S3 Standard or Bulk retrievals.)
-
HTTP Status Code: 503
-
SOAP Fault Code Prefix: N/A
-
-
The following operations are related to
RestoreObject
:upload(params = {}, [options], [callback]) ⇒ AWS.S3.ManagedUpload
uploadPart(params = {}, callback) ⇒ AWS.Request
Uploads a part in a multipart upload.
Note: In this operation, you provide part data in your request. However, you have an option to specify your existing Amazon S3 object as a data source for the part you are uploading. To upload a part from an existing object, you use the UploadPartCopy operation.You must initiate a multipart upload (see CreateMultipartUpload) before you can upload any part. In response to your initiate request, Amazon S3 returns an upload ID, a unique identifier, that you must include in your upload part request.
Part numbers can be any number from 1 to 10,000, inclusive. A part number uniquely identifies a part and also defines its position within the object being created. If you upload a new part using the same part number that was used with a previous part, the previously uploaded part is overwritten.
For information about maximum and minimum part sizes and other multipart upload specifications, see Multipart upload limits in the Amazon S3 User Guide.
To ensure that data is not corrupted when traversing the network, specify the
Content-MD5
header in the upload part request. Amazon S3 checks the part data against the provided MD5 value. If they do not match, Amazon S3 returns an error.If the upload request is signed with Signature Version 4, then Amazon Web Services S3 uses the
x-amz-content-sha256
header as a checksum instead ofContent-MD5
. For more information see Authenticating Requests: Using the Authorization Header (Amazon Web Services Signature Version 4).Note: After you initiate multipart upload and upload one or more parts, you must either complete or abort multipart upload in order to stop getting charged for storage of the uploaded parts. Only after you either complete or abort multipart upload, Amazon S3 frees up the parts storage and stops charging you for the parts storage.
For more information on multipart uploads, go to Multipart Upload Overview in the Amazon S3 User Guide .
For information on the permissions required to use the multipart upload API, go to Multipart Upload and Permissions in the Amazon S3 User Guide.
Server-side encryption is for data encryption at rest. Amazon S3 encrypts your data as it writes it to disks in its data centers and decrypts it when you access it. You have three mutually exclusive options to protect data using server-side encryption in Amazon S3, depending on how you choose to manage the encryption keys. Specifically, the encryption key options are Amazon S3 managed keys (SSE-S3), Amazon Web Services KMS keys (SSE-KMS), and Customer-Provided Keys (SSE-C). Amazon S3 encrypts data with server-side encryption using Amazon S3 managed keys (SSE-S3) by default. You can optionally tell Amazon S3 to encrypt data at rest using server-side encryption with other key options. The option you use depends on whether you want to use KMS keys (SSE-KMS) or provide your own encryption key (SSE-C). If you choose to provide your own encryption key, the request headers you provide in the request must match the headers you used in the request to initiate the upload by using CreateMultipartUpload. For more information, go to Using Server-Side Encryption in the Amazon S3 User Guide.
Server-side encryption is supported by the S3 Multipart Upload actions. Unless you are using a customer-provided encryption key (SSE-C), you don't need to specify the encryption parameters in each UploadPart request. Instead, you only need to specify the server-side encryption parameters in the initial Initiate Multipart request. For more information, see CreateMultipartUpload.
If you requested server-side encryption using a customer-provided encryption key (SSE-C) in your initiate multipart upload request, you must provide identical encryption information in each part upload using the following headers.
-
x-amz-server-side-encryption-customer-algorithm
-
x-amz-server-side-encryption-customer-key
-
x-amz-server-side-encryption-customer-key-MD5
UploadPart
has the following special errors:-
-
Code: NoSuchUpload
-
Cause: The specified multipart upload does not exist. The upload ID might be invalid, or the multipart upload might have been aborted or completed.
-
HTTP Status Code: 404 Not Found
-
SOAP Fault Code Prefix: Client
-
The following operations are related to
UploadPart
:uploadPartCopy(params = {}, callback) ⇒ AWS.Request
Uploads a part by copying data from an existing object as data source. You specify the data source by adding the request header
x-amz-copy-source
in your request and a byte range by adding the request headerx-amz-copy-source-range
in your request.For information about maximum and minimum part sizes and other multipart upload specifications, see Multipart upload limits in the Amazon S3 User Guide.
Note: Instead of using an existing object as part data, you might use the UploadPart action and provide data in your request.You must initiate a multipart upload before you can upload any part. In response to your initiate request. Amazon S3 returns a unique identifier, the upload ID, that you must include in your upload part request.
For more information about using the
UploadPartCopy
operation, see the following:-
For conceptual information about multipart uploads, see Uploading Objects Using Multipart Upload in the Amazon S3 User Guide.
-
For information about permissions required to use the multipart upload API, see Multipart Upload and Permissions in the Amazon S3 User Guide.
-
For information about copying objects using a single atomic action vs. a multipart upload, see Operations on Objects in the Amazon S3 User Guide.
-
For information about using server-side encryption with customer-provided encryption keys with the
UploadPartCopy
operation, see CopyObject and UploadPart.
Note the following additional considerations about the request headers
x-amz-copy-source-if-match
,x-amz-copy-source-if-none-match
,x-amz-copy-source-if-unmodified-since
, andx-amz-copy-source-if-modified-since
:-
Consideration 1 - If both of the
x-amz-copy-source-if-match
andx-amz-copy-source-if-unmodified-since
headers are present in the request as follows:x-amz-copy-source-if-match
condition evaluates totrue
, and;x-amz-copy-source-if-unmodified-since
condition evaluates tofalse
;Amazon S3 returns
200 OK
and copies the data. -
Consideration 2 - If both of the
x-amz-copy-source-if-none-match
andx-amz-copy-source-if-modified-since
headers are present in the request as follows:x-amz-copy-source-if-none-match
condition evaluates tofalse
, and;x-amz-copy-source-if-modified-since
condition evaluates totrue
;Amazon S3 returns
412 Precondition Failed
response code.
- Versioning
-
If your bucket has versioning enabled, you could have multiple versions of the same object. By default,
x-amz-copy-source
identifies the current version of the object to copy. If the current version is a delete marker and you don't specify a versionId in thex-amz-copy-source
, Amazon S3 returns a 404 error, because the object does not exist. If you specify versionId in thex-amz-copy-source
and the versionId is a delete marker, Amazon S3 returns an HTTP 400 error, because you are not allowed to specify a delete marker as a version for thex-amz-copy-source
.You can optionally specify a specific version of the source object to copy by adding the
versionId
subresource as shown in the following example:x-amz-copy-source: /bucket/object?versionId=version id
- Special errors
-
-
-
Code: NoSuchUpload
-
Cause: The specified multipart upload does not exist. The upload ID might be invalid, or the multipart upload might have been aborted or completed.
-
HTTP Status Code: 404 Not Found
-
-
-
Code: InvalidRequest
-
Cause: The specified copy source is not supported as a byte-range copy source.
-
HTTP Status Code: 400 Bad Request
-
-
The following operations are related to
UploadPartCopy
:waitFor(state, params = {}, callback) ⇒ AWS.Request
Waits for a given S3 resource. The final callback or 'complete' event will be fired only when the resource is either in its final state or the waiter has timed out and stopped polling for the final state.
Waiter Resource Details
s3.waitFor('bucketExists', params = {}, [callback]) ⇒ AWS.Request
Waits for the
bucketExists
state by periodically calling the underlying S3.headBucket() operation every 5 seconds (at most 20 times).s3.waitFor('bucketNotExists', params = {}, [callback]) ⇒ AWS.Request
Waits for the
bucketNotExists
state by periodically calling the underlying S3.headBucket() operation every 5 seconds (at most 20 times).s3.waitFor('objectExists', params = {}, [callback]) ⇒ AWS.Request
Waits for the
objectExists
state by periodically calling the underlying S3.headObject() operation every 5 seconds (at most 20 times).s3.waitFor('objectNotExists', params = {}, [callback]) ⇒ AWS.Request
Waits for the
objectNotExists
state by periodically calling the underlying S3.headObject() operation every 5 seconds (at most 20 times). - createBucket(params, callback) ⇒ AWS.Request