deleteObject
Removes an object from a bucket. The behavior depends on the bucket's versioning state:
If versioning is enabled, the operation 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.
If versioning is suspended or not enabled, the operation permanently deletes the object.
Directory buckets - S3 Versioning isn't enabled and supported for directory buckets. For this API operation, only the
null
value of the version ID is supported by directory buckets. You can only specifynull
to theversionId
query parameter in the request.Directory buckets - For directory buckets, you must make requests for this API operation to the Zonal endpoint. These endpoints support virtual-hosted-style requests in the format
https://<i>bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com/<i>key-name</i>
. Path-style requests are not supported. For more information, see Regional and Zonal endpoints in the Amazon S3 User Guide. To remove a specific version, you must use theversionId
query parameter. Using this query parameter permanently deletes the version. If the object deleted is a delete marker, Amazon S3 sets the response headerx-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 DELETE versionId
request. Requests that include x-amz-mfa
must use HTTPS. For more information about MFA Delete, see Using MFA Delete in the Amazon S3 User Guide. To see sample requests that use versioning, see Sample Request.
Directory buckets - MFA delete is not supported by directory buckets.
You can delete objects by explicitly calling DELETE Object or calling (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
, and s3:PutLifeCycleConfiguration
actions.
Directory buckets - S3 Lifecycle is not supported by directory buckets.
Permissions
General purpose bucket permissions - The following permissions are required in your policies when your
DeleteObjects
request includes specific headers.s3:DeleteObject
- To delete an object from a bucket, you must always have thes3:DeleteObject
permission.s3:DeleteObjectVersion
- To delete a specific version of an object from a versiong-enabled bucket, you must have thes3:DeleteObjectVersion
permission.Directory bucket permissions - To grant access to this API operation on a directory bucket, we recommend that you use the
CreateSession
API operation for session-based authorization. Specifically, you grant thes3express:CreateSession
permission to the directory bucket in a bucket policy or an IAM identity-based policy. Then, you make theCreateSession
API call on the bucket to obtain a session token. With the session token in your request header, you can make API requests to this operation. After the session token expires, you make anotherCreateSession
API call to generate a new session token for use. Amazon Web Services CLI or SDKs create session and refresh the session token automatically to avoid service interruptions when a session expires. For more information about authorization, seeCreateSession
.
HTTP Host header syntax
**Directory buckets ** - The HTTP Host header syntax is <i>Bucket_name</i>.s3express-<i>az_id</i>.<i>region</i>.amazonaws.com
.
The following action is related to DeleteObject
:
Samples
fun main() {
//sampleStart
// The following example deletes an object from a non versioned bucket.
s3Client.deleteObject {
bucket = "ExampleBucket"
key = "HappyFace.jpg"
}
//sampleEnd
}
fun main() {
//sampleStart
// The following example deletes an object from an S3 bucket.
val resp = s3Client.deleteObject {
bucket = "examplebucket"
key = "objectkey.jpg"
}
//sampleEnd
}