diff --git a/pages/object-storage/troubleshooting/deleted-objects-still-billed.mdx b/pages/object-storage/troubleshooting/deleted-objects-still-billed.mdx new file mode 100644 index 0000000000..c3b684f870 --- /dev/null +++ b/pages/object-storage/troubleshooting/deleted-objects-still-billed.mdx @@ -0,0 +1,74 @@ +--- +title: I am getting billed for objects that I cannot see +description: I don't understand the amount billed compared to the objects that are present in my Scaleway Object Storage bucket +tags: +categories: + - storage + - object-storage +dates: + validation: 2025-07-16 + posted: 2025-07-03 +--- + +import Requirements from '@macros/iam/requirements.mdx' + + + +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization + +## Problem + +The amount billed does not correspond to the objects that are present in my Scaleway Object Storage bucket. + +## Possible causes + +- Your [bucket is versioned](/object-storage/how-to/use-bucket-versioning/), and multiple versions of your objects are stored in it, incurring extra cost. + +- Some [multipart uploads](/object-storage/api-cli/multipart-uploads/) are ongoing. The storage used during the upload is billed, but the object is not visible as long as the upload is not complete. + +## Possible solutions + +### Bucket versioning + +1. Check the versioning status of your bucket via the [Scaleway console](https://console.scaleway.com/object-storage/buckets), or using the [GetBucketVersioning](/object-storage/api-cli/bucket-operations/#getbucketversioning) command: + ``` + aws s3api get-bucket-versioning --bucket BucketName + ``` + - If the versioning is `disabled`, the issue is not linked to versioning. + - If the versioning is `enabled` or `suspended`, you may have multiple versions of your objects. +2. Use the [ListObjectVersions](/object-storage/api-cli/bucket-operations/#listobjectversions) command to list the versions of the objects in your bucket: + ```sh + aws s3api list-object-versions --bucket BucketName + ``` + A list of all the objects versions and delete markers present in the bucket appears. +3. Delete the unwanted versions and delete markers using the [DeleteObject] command with a versionId specified: + ```sh + aws s3api delete-object --bucket BucketName --key ObjectName --version-id ObjectVersion + ``` +Refer to the [official Amazon S3 documentation](https://docs.aws.amazon.com/AmazonS3/latest/userguide/versioning-workflows.html) for more information on how versioning works. + +### Multipart uploads + +1. Check if some multipart uploads are ongoing using the [ListMultipartUpload](/object-storage/api-cli/multipart-uploads/#listing-multipart-uploads) command: + ```sh + list-multipart-uploads --bucket BucketName + ``` + A list of ongoing multipart uploads displays. + +2. Abort the unwanted multipart uploads via the [Scaleway console](/object-storage/how-to/abort-incomplete-mpu/), or [using the CLI](/object-storage/api-cli/multipart-uploads/). + +3. Optionally, you can [set up lifecycle rules](/object-storage/how-to/manage-lifecycle-rules/) to automatically abort incomplete multipart uploads after a given duration. + +## Going further + + +- If you did not manage to identify the error and solve it by yourself, [open a support ticket](/account/how-to/open-a-support-ticket/), and provide as many details as possible, along with the necessary information below: + - Object Storage Endpoint (e.g. `s3.fr-par.scw.cloud`) + - Bucket name + - Object name (if the request concerns an object) + - Request type (PUT, GET, etc.) + - HTTP status code + - Date and time (timestamp) + - User-agent (SDK, client, console, etc.) + - Transaction ID (if possible) + - Log / trace of the error (if possible) diff --git a/pages/object-storage/troubleshooting/index.mdx b/pages/object-storage/troubleshooting/index.mdx index 46a47c2f0f..3dde4bb71e 100644 --- a/pages/object-storage/troubleshooting/index.mdx +++ b/pages/object-storage/troubleshooting/index.mdx @@ -59,10 +59,19 @@ productIcon: ObjectStorageProductIcon ## Object Storage troubleshooting pages - - [My API key does not work with Object Storage](/object-storage/troubleshooting/api-key-does-not-work) - - [I cannot access my data](/object-storage/troubleshooting/cannot-access-data) - - [I cannot delete my bucket](/object-storage/troubleshooting/cannot-delete-bucket) - - [I cannot restore my objects from Glacier](/object-storage/troubleshooting/cannot-restore-glacier) - - [I lost access to a bucket after applying a bucket policy](/object-storage/troubleshooting/lost-bucket-access-bucket-policy) - - [I am experiencing performance issues](/object-storage/troubleshooting/low-performance) +- [My API key does not work with Object Storage](/object-storage/troubleshooting/api-key-does-not-work/) +- [I cannot access my data](/object-storage/troubleshooting/cannot-access-data/) +- [I cannot delete my bucket](/object-storage/troubleshooting/cannot-delete-bucket/) +- [I cannot restore my objects from Glacier](/object-storage/troubleshooting/cannot-restore-glacier/) +- [I lost access to a bucket after applying a bucket policy](/object-storage/troubleshooting/lost-bucket-access-bucket-policy/) +- [I am experiencing performance issues](/object-storage/troubleshooting/low-performance/) +- [Lifecycle rules issues](/object-storage/troubleshooting/lifecycle-rules-issues/) +- [Deleted objects are still billed](/object-storage/troubleshooting/deleted-objects-still-billed/) +- [Lifecycle rules issues](/object-storage/troubleshooting/lifecycle-rules-issues/) +- [Object deletion issues](/object-storage/troubleshooting/object-deletion-issues/) +- [I am getting billed for objects that I cannot see](/object-storage/troubleshooting/deleted-objects-still-billed/) +- [I get error messages when trying to access a bucket](/object-storage/troubleshooting/error-messages-access/) +- [I am experiencing DNS/Edge Services issues](/object-storage/troubleshooting/issues-dns-edge-services/) +- [I am getting presigned URL errors](/object-storage/troubleshooting/presigned-url-errors/) +- [I am experiencing request rate errors](/object-storage/troubleshooting/request-rate-error/) diff --git a/pages/object-storage/troubleshooting/lifecycle-rules-issues.mdx b/pages/object-storage/troubleshooting/lifecycle-rules-issues.mdx new file mode 100644 index 0000000000..48ceda59db --- /dev/null +++ b/pages/object-storage/troubleshooting/lifecycle-rules-issues.mdx @@ -0,0 +1,54 @@ +--- +title: I am experiencing issues with lifecycle rules +description: Resolve issues encountered while using lifecycle rules with Scaleway Object Storage +tags: issues error problem lifecycle rules expire transfer class +categories: + - storage + - object-storage +dates: + validation: 2025-07-16 + posted: 2025-07-03 +--- + +import Requirements from '@macros/iam/requirements.mdx' + + + +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization + +## Problem + +I am experiencing issues with the lifecycle rules of my Scaleway Object Storage bucket. + +## Cause + +- Lifecycle rules are not properly set + +- Spaces are present in the prefixes or tags of your objects + +- You reached the limit of 500,000 lifecycle jobs per day + +## Possible solutions + +- Make sure that [lifecycle rules are properly set](/object-storage/how-to/manage-lifecycle-rules/) in the Scaleway console. + +- Make sure that the prefixes and tags of your objects do not contain any spaces. + +- If you reached the limit of 500,000 jobs per day, you can [transition](/object-storage/how-to/edit-storage-class/) or [delete](/object-storage/how-to/delete-an-object/) objects manually. + +- For expiration rules, you can use the [HeadObject](/object-storage/api-cli/object-operations/#headobject) command to check which rule is applied to a specific object. The `x-amz-expiration` header should return the expiration date and rule ID. + +## Going further + +- Refer to the [lifecycle rules documentation](/object-storage/how-to/manage-lifecycle-rules/) for more information. + +- If you did not manage to identify the error and solve it by yourself, [open a support ticket](/account/how-to/open-a-support-ticket/), and provide as many details as possible, along with the necessary information below: + - Object Storage Endpoint (e.g. `s3.fr-par.scw.cloud`) + - Bucket name + - Object name (if the request concerns an object) + - Request type (PUT, GET, etc.) + - HTTP status code + - Date and time (timestamp) + - User-agent (SDK, client, console, etc.) + - Transaction ID (if possible) + - Log / trace of the error (if possible) diff --git a/pages/object-storage/troubleshooting/object-deletion-issues.mdx b/pages/object-storage/troubleshooting/object-deletion-issues.mdx new file mode 100644 index 0000000000..53a8728e9b --- /dev/null +++ b/pages/object-storage/troubleshooting/object-deletion-issues.mdx @@ -0,0 +1,53 @@ +--- +title: I am experiencing issues while deleting objects +description: Find solutions to problems encountered while deleting objects with Scaleway Object Storage +tags: +categories: + - storage + - object-storage +dates: + validation: 2025-07-16 + posted: 2025-07-03 +--- + +import Requirements from '@macros/iam/requirements.mdx' + + + +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization + +## Problem + +I am experiencing issues while deleting objects + +## Cause + +- The object you are trying to delete is locked +- The bucket is versioned, and deleting an object adds a **delete marker** rather than deleting the object + +## Possible solutions + +### Object lock + +Check if the object is locked using the [HeadObject](/object-storage/api-cli/object-operations/#headobject) command. If it is locked with the **Governance** retention mode, you can bypass it with the [DeleteObject](/object-storage/api-cli/object-operations/#deleteobject) command using the `x-amz-bypass-governance-retention` header. You must also specify the VersionId of the object, as buckets with object lock enabled are automatically versioned. + +### Bucket versioning + +A [DeleteObject](/object-storage/api-cli/object-operations/#deleteobject) operation on a versioned bucket with no `VersionId` specified will create a delete marker, and the targeted objects will keep existing. To permanently delete it, list all the versions with [ListObjectVersions](/object-storage/api-cli/bucket-operations/#listobjectversions) (you can specify the name of your object as a prefix), then use the [DeleteObject](/object-storage/api-cli/object-operations/#deleteobject) operation on each version. + +## Going further + +- Refer to the [object lock documentation](/object-storage/api-cli/object-lock/) for more information. + +- Refer to the [bucket versioning documentation](/object-storage/how-to/use-bucket-versioning/) for more information. + +- If you did not manage to identify the error and solve it by yourself, [open a support ticket](/account/how-to/open-a-support-ticket/), and provide as many details as possible, along with the necessary information below: + - Object Storage Endpoint (e.g. `s3.fr-par.scw.cloud`) + - Bucket name + - Object name (if the request concerns an object) + - Request type (PUT, GET, etc.) + - HTTP status code + - Date and time (timestamp) + - User-agent (SDK, client, console, etc.) + - Transaction ID (if possible) + - Log / trace of the error (if possible) diff --git a/pages/object-storage/troubleshooting/presigned-url-errors.mdx b/pages/object-storage/troubleshooting/presigned-url-errors.mdx new file mode 100644 index 0000000000..7ff992c0a7 --- /dev/null +++ b/pages/object-storage/troubleshooting/presigned-url-errors.mdx @@ -0,0 +1,47 @@ +--- +title: I am getting presigned URL errors +description: I am receiving errors when using a presigned URL to access an object using Scaleway Object Storage. +tags: +categories: + - storage + - object-storage +dates: + validation: 2025-07-16 + posted: 2025-07-03 +--- +import Requirements from '@macros/iam/requirements.mdx' + + + +- A Scaleway account logged into the [console](https://console.scaleway.com) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization + +## Problem + +I am receiving errors when using a presigned URL to access an object. + +## Cause + +- A clock skew of more than 15 minutes between the host and client will trigger a `InvalidSignatureException` or a `RequestTimeTooSkewed` error + +- The public link of your [private object](/object-storage/concepts/) has expired + +## Possible solutions + +- Make sure that there is less than 15 minutes of clock skew between the host and client machines. + +- Make sure that the object's public link has not expired. + +## Going further + +- Refer to the [documentation on sharing objects](/object-storage/how-to/access-objects-via-https/) for more information on public links. +- If you did not manage to identify the error and solve it by yourself, [open a support ticket](/account/how-to/open-a-support-ticket/), and provide as many details as possible, along with the necessary information below: + - Object Storage Endpoint (e.g. `s3.fr-par.scw.cloud`) + - Bucket name + - Object name (if the request concerns an object) + - Request type (PUT, GET, etc.) + - HTTP status code + - Date and time (timestamp) + - User-agent (SDK, client, console, etc.) + - Transaction ID (if possible) + - Log / trace of the error (if possible) diff --git a/pages/object-storage/troubleshooting/request-rate-error.mdx b/pages/object-storage/troubleshooting/request-rate-error.mdx index 1a7438641c..1df0977728 100644 --- a/pages/object-storage/troubleshooting/request-rate-error.mdx +++ b/pages/object-storage/troubleshooting/request-rate-error.mdx @@ -9,11 +9,12 @@ categories: - storage - object-storage --- -import Requirements from '@macros/iam/requirements.mdx' +import Requirements from '@macros/iam/requirements.mdx' +- A Scaleway account logged into the [console](https://console.scaleway.com) - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization ## Problem