diff --git a/menu/navigation.json b/menu/navigation.json index 4d81810709..9e75e9d50d 100644 --- a/menu/navigation.json +++ b/menu/navigation.json @@ -4082,6 +4082,10 @@ "label": "Manage lifecycle rules", "slug": "manage-lifecycle-rules" }, + { + "label": "View and abort incomplete multipart uploads", + "slug": "abort-incomplete-mpu" + }, { "label": "Monitor your consumption", "slug": "monitor-consumption" diff --git a/storage/object/api-cli/multipart-uploads.mdx b/storage/object/api-cli/multipart-uploads.mdx index e54ac65d85..98c8039c85 100644 --- a/storage/object/api-cli/multipart-uploads.mdx +++ b/storage/object/api-cli/multipart-uploads.mdx @@ -274,6 +274,10 @@ If the multipart upload is not completed, the parts will not be assembled and no In case these parts are no longer needed, it is possible to clear them by aborting the multipart upload session. + +You can also abort incomplete multipart uploads manually using the [Scaleway console](https://console.scaleway.com/), or automatically using [lifecycle rules](/storage/object/how-to/manage-lifecycle-rules). + + To abort an active multipart upload session, send a `DELETE` request to the platform, as follows: ``` diff --git a/storage/object/how-to/abort-incomplete-mpu.mdx b/storage/object/how-to/abort-incomplete-mpu.mdx new file mode 100644 index 0000000000..9daa184f68 --- /dev/null +++ b/storage/object/how-to/abort-incomplete-mpu.mdx @@ -0,0 +1,60 @@ +--- +meta: + title: How to view and abort incomplete multipart uploads from the console + description: Steps to view and abort incomplete multipart uploads from the Scaleway console. +content: + h1: How to view and abort incomplete multipart uploads from the console + paragraph: Steps to view and abort incomplete multipart uploads from the Scaleway console. +tags: object storage object-storage mpu multipart upload abort +dates: + validation: 2024-09-13 + posted: 2024-09-13 +categories: + - storage + - object-storage +--- + +The [Scaleway console](https://console.scaleway.com/) lists your Object Storage incomplete multipart uploads to allow you to consult them and manually abort them to clear storage space and optimize your storage costs. + + +Incomplete multipart uploads are charged even though they are not finished as they use storage space. + + +You can automate the process of aborting incomplete multipart uploads using [lifecycle rules](/storage/object/how-to/manage-lifecycle-rules). + + + +- A Scaleway account logged into the [console](https://console.scaleway.com) +- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [Object Storage bucket](/storage/object/how-to/create-a-bucket/) +- At least one incomplete [multipart upload](/storage/object/api-cli/multipart-uploads/) + +## How to view the information of an incomplete multipart upload + +1. Click **Object Storage** in the **Storage** section of the side menu. The list of your buckets displays. +2. Click the name of your bucket. The list of your objects displays. +3. Click the **Incomplete MPU** tab. A list of your incomplete multipart uploads displays. +4. Click next to the object you want to consult. +5. Click **More info**. The information page of the incomplete multipart upload displays. + +From this page, you can consult the following elements of an incomplete multipart upload: +- Name +- Upload ID +- Creation date +- Storage class +- List of parts uploaded so far + +Refer to the [dedicated documentation](/storage/object/api-cli/multipart-uploads/) for more information on how to create and manage multipart uploads. + +## How to abort an incomplete multipart upload + +1. Click **Object Storage** in the **Storage** section of the side menu. The list of your buckets displays. +2. Click the name of your bucket. The list of your objects displays. +3. Click the **Incomplete MPU** tab. A list of your incomplete multipart uploads displays. +4. Click next to the object you want to abort. +5. Click **Abort**. A confirmation pop-up displays. +6. Type **ABORT** then click **Abort multipart upload** to confirm your action. + + +This action will permanently delete the upload, and all the parts uploaded so far. You can also abort an incomplete multipart upload from its [information page](#how-to-view-the-information-of-an-incomplete-multipart-upload). + diff --git a/storage/object/how-to/manage-lifecycle-rules.mdx b/storage/object/how-to/manage-lifecycle-rules.mdx index 1bb342398b..1599409a62 100644 --- a/storage/object/how-to/manage-lifecycle-rules.mdx +++ b/storage/object/how-to/manage-lifecycle-rules.mdx @@ -5,9 +5,9 @@ meta: content: h1: How to manage lifecycle rules from the console paragraph: Set and manage lifecycle rules for Object Storage. -tags: object storage object-storage lifecycle lifecycle-rule +tags: object storage object-storage lifecycle lifecycle-rule abort incompelte multipart upload expire version dates: - validation: 2024-06-14 + validation: 2024-09-13 posted: 2021-05-27 categories: - storage @@ -16,6 +16,8 @@ categories: With the Scaleway console, you can use lifecycle rules to [manually](/storage/object/how-to/edit-storage-class/) or automatically change the storage class of your objects. These rules also allow users to set expiration dates for objects and their versions. +Lifecycle rules also allow you to automatically abort incomplete [multipart uploads](/storage/object/api-cli/multipart-uploads/). + - A Scaleway account logged into the [console](https://console.scaleway.com) @@ -28,44 +30,29 @@ With the Scaleway console, you can use lifecycle rules to [manually](/storage/ob 3. Click **Lifecycle rules**. 4. Click **+ Create Lifecycle rule** to add a rule. 5. Enter a name for the rule. -6. Filter the objects you want the rule to be applied to by one or both of the following criteria: - - [**Prefix**](/storage/object/concepts/#prefix): based on the object name and path. The defined rule will be applied to all objects with the same name [prefix](/storage/object/concepts/#prefix). - - [**Tags**](/storage/object/concepts/#tags): comprised of a **key** and an associated **value**. These tags should be defined before rule creation, for either a bucket or an object. You can add one or more tags to your filter. - - - - - Lifecycle rules are limited to 500,000 jobs per day. Beyond this limit, you can [transition](/storage/object/how-to/edit-storage-class/) or [delete](/storage/object/how-to/delete-an-object/) your objects manually. - +6. Select the scope of the lifecycle rule: + - Apply the rule to all the objects contained in the bucket. + - Filter the objects you want the rule to be applied to by one or both of the following criteria: + - [**Prefix**](/storage/object/concepts/#prefix): based on the object name and path. The defined rule will be applied to all objects with the same name [prefix](/storage/object/concepts/#prefix). + - [**Tags**](/storage/object/concepts/#tags): comprised of a **key** and an associated **value**. These tags should be defined before rule creation, for either a bucket or an object. You can add one or more tags to your filter. +7. Configure the behavior of the lifecycle rule: + - Automatically transition the current version of your objects to another storage class after a specified number of days. + - Automatically delete the current version of your objects after a specified number of days. + - Automatically abort [incomplete multipart uploads](/storage/object/api-cli/multipart-uploads/#aborting-a-multipart-upload) after a specified number of days. -## How to configure transition rules +8. Click **Next Step** to proceed. -If you wish to change the [storage class](/storage/object/concepts/#storage-class) of two or more objects at a time, you can set up a transition rule that will automate the process. - -1. Click **Change object class** to transfer the current version of the objects to a different storage class. -2. Select the new storage class. -3. Enter the desired number of days before transition. -4. Click **Next step** to proceed. -5. Make sure all the information is correct, then click **Create Lifecycle rule** to confirm. +9. Review the summary of your lifecycle rule, then click **Create lifecycle rule** to confirm. - Lifecycle rules only allow the following transitions: - - Standard -> Onezone IA - - Standard -> Glacier - - Onezone IA -> Glacier + - Lifecycle rules are limited to 500,000 jobs per day. Beyond this limit, you can [transition](/storage/object/how-to/edit-storage-class/) or [delete](/storage/object/how-to/delete-an-object/) your objects manually. - Refer to the documentation on [how to manually change the storage class of your objects](/storage/object/how-to/edit-storage-class/) for more information. + - Lifecycle rules only allow the following transitions: + - Standard -> Onezone IA + - Standard -> Glacier + - Onezone IA -> Glacier -## How to configure expiration rules - -If you wish to delete an object after a set number of days, you can set up an expiration rule that will automate the process. - -1. Click **Delete after expiration** to define when the current version of your objects will be deleted. -2. Enter the desired number of days before deletion. -3. Click **Next step** to proceed. -4. Check that all settings are correct and click **Create Lifecycle rule** to confirm. - ## How to disable a lifecycle rule 1. Click **Object Storage** in the **Storage** section of the side menu. A list of your buckets displays. @@ -76,7 +63,7 @@ If you wish to delete an object after a set number of days, you can set up an ex 6. Click **Disable lifecycle rule** to confirm. -Once disabled, the lifecycle rule remains listed and can be enabled again. Click > **Activate** to do so. +Once disabled, the lifecycle rule remains listed and can be enabled again. Click , then select **Activate** to re-enable it. To permanently delete a rule, click , then click **Delete**. \ No newline at end of file