diff --git a/pages/iam/troubleshooting/cannot-use-resources.mdx b/pages/iam/troubleshooting/cannot-use-resources.mdx index 168cc9e8c8..cc424d2a65 100644 --- a/pages/iam/troubleshooting/cannot-use-resources.mdx +++ b/pages/iam/troubleshooting/cannot-use-resources.mdx @@ -37,7 +37,7 @@ You (or the IAM [user](/iam/concepts/glossary/#user) or [application](/iam/conce 4. If you are using a command-line tool to interact with Scaleway resources, make sure that there is no environment variable overriding your API key. Refer to the [documentation on environment variables priority](/scaleway-cli/reference-content/environment-variables/#environment-variables-priority) for more information. -If you encounter issues while using Object Storage, refer to the [dedicated troubleshooting page](/object-storage/troubleshooting/api-key-does-not-work/). +If you encounter issues while using Object Storage, refer to the [dedicated troubleshooting page](/object-storage/troubleshooting/access-and-authentication/#my-api-key-does-not-work). ## Going further diff --git a/pages/object-storage/how-to/create-bucket-policy.mdx b/pages/object-storage/how-to/create-bucket-policy.mdx index 66ec3c90be..cf325f3567 100644 --- a/pages/object-storage/how-to/create-bucket-policy.mdx +++ b/pages/object-storage/how-to/create-bucket-policy.mdx @@ -228,7 +228,7 @@ Alternatively, you can also delete a bucket policy by clicking + +- [Owner](/iam/concepts/glossary/#owner) status or [IAM permissions](/iam/concepts/glossary/#permission) allowing you to perform actions in the intended Organization + +## My API key does not work + +When using third-party API or CLI tools, such as the [AWS CLI](/object-storage/api-cli/object-storage-aws-cli/), [MinIO Client](/object-storage/api-cli/installing-minio-client/), or [Rclone](/object-storage/api-cli/installing-rclone/) to manage your Object Storage resources, you experience one of the following issues: + +- Listing your buckets with a third-party tool returns nothing, but you have at least one bucket in the [Scaleway console](https://console.scaleway.com/object-storage/buckets). +- The tool returns `An error occurred (Forbidden) when calling the ListObjectsV2 operation: Forbidden` or a similar message. +- The tool returns a `403` error. + +### Cause + +The API key you used to configure the third-party tool has a [preferred Project](/iam/concepts/glossary/#preferred-project) assigned. + +If you perform Object Storage operations in a Project that is **not** the preferred Project of the API key using a third-party tool, you cannot access your resources, and the tool returns an error message or an empty response. + +### Solution + +1. Make sure that you are using a valid [API key](https://console.scaleway.com/iam/api-keys). +2. Make sure that the bearer of the API key (IAM [user](/iam/concepts/glossary/#user) or [application](/iam/concepts/glossary/#application)) has the appropriate [IAM permissions](/iam/policies-permissions/view-permission-sets/) to perform the desired actions. +3. Make sure that the [preferred Project](/iam/concepts/glossary/#preferred-project) of the API key is the Project where you are performing actions. You can change the preferred Project of your API key: + - by [editing it from the Scaleway console](/iam/credentials/manage-api-keys/#how-to-edit-an-api-key) + - by [overriding it when making an API call](/iam/api-cli/using-api-key-object-storage/#overriding-the-preferred-project-when-making-a-call) +4. Make sure that no [bucket policy](/object-storage/concepts/#bucket-policy) prevents the action. If there is one, [update the bucket policy](/object-storage/how-to/create-bucket-policy/) to allow the desired actions to the bearer of the API key. + +See the documentation on [using IAM API keys with Object Storage](/iam/api-cli/using-api-key-object-storage/) for more information. + +## I get error messages when accessing a bucket + +One of the following messages displays when an application tries to access your bucket: + +- `Failed to preprocess target Error: S3 error: Access Denied` +- `Error: Shared memory connection was closed.` +- `Failed to upload disk 'shadowSpec>'` +- `Agent failed to process method {DataTransfer.SyncDisk}.` + +### Cause + +The application cannot access the Object Storage resource. + + + The `Shared memory connection was closed.` and `Agent failed to process method {DataTransfer.SyncDisk}.` messages can also indicate that your application reached the request rate limit. If the solution below does not solve the issue, refer to the [request rate errors troubleshooting](/object-storage/troubleshooting/performance-and-rate-limits/#i-get-request-rate-errors). + + +### Solution + +1. Check for issues with your API key by following the [API key troubleshooting procedure](#my-api-key-does-not-work). +2. Make sure that you have the `ObjectStorageFullAccess` [IAM permission set](/iam/concepts/glossary/#permission). +3. Make sure that no [bucket policy](/object-storage/api-cli/bucket-policy/) prevents the application from accessing your bucket. + +## I lost access to a bucket after applying a bucket policy + +After [creating and applying a bucket policy](/object-storage/api-cli/create-bucket-policy/) to a bucket, you can no longer access the resources within the bucket, and one of the following messages displays: + +- \[CLI\] - `An error occurred (AccessDenied) when calling the ListObjectsV2 operation: Access Denied` +- \[CLI\] - `403 AccessDenied` +- \[Console\] - `Failed to update bucket. Retry.` +- \[Console\] - `Failed to load data. Try refreshing the page.` + +### Cause + +[Bucket policies](/object-storage/api-cli/bucket-policy/) automatically deny actions to users who are not explicitly allowed by a [statement](/object-storage/api-cli/bucket-policy/#statement). If the bucket policy does not explicitly allow you, you lose access to the resources in the bucket. + + + +### Solution + +If you have permission to apply a bucket policy, you can edit or delete the bucket policy to regain access. + + + + +1. Click **Object Storage** on the left side menu of the console. The Object Storage dashboard displays. +2. Click the **Bucket policies** tab. +3. Click the name of the bucket policy applied to the bucket. +4. Edit the bucket policy to grant yourself access, or delete it and [create a new one](/object-storage/how-to/create-bucket-policy/). + + + +Do one of the following: + +- Delete the current bucket policy using the following command. The bucket becomes available to every user with the appropriate [IAM permissions](/iam/concepts/glossary/#permission). + ```bash + aws s3api delete-bucket-policy --bucket + ``` +- [Apply a new bucket policy](/object-storage/api-cli/create-bucket-policy/) to the bucket to allow yourself, or a principal, to perform the desired [storage operations](/object-storage/api-cli/using-api-call-list/). + + + + +See the [bucket policies overview](/object-storage/api-cli/bucket-policy/) for more information on the different elements of a bucket policy. + +## I get presigned URL errors + +You receive an error when using a presigned URL to access an object. + +### Cause + +- A clock skew of more than 15 minutes between the host and the client triggers an `InvalidSignatureException` or a `RequestTimeTooSkewed` error. +- The presigned URL of your [private object](/object-storage/concepts/) has expired. + +### Solution + +- Make sure that the clock skew between the host and client machines is less than 15 minutes. +- Make sure that the presigned URL has not expired. If it has, generate a new one. + +See the documentation on [sharing objects](/object-storage/how-to/access-objects-via-https/) for more information on presigned URLs. + +## I cannot access my objects + +You experience issues accessing your buckets and objects, and none of the symptoms mentioned previously match your situation. + +### Solution + +- Go to the [Status page](https://status.scaleway.com/) to see if there is an ongoing incident on the Scaleway infrastructure. +- Make sure that you are using a valid [API key](https://console.scaleway.com/iam/api-keys). +- Make sure that the bearer of the API key (IAM [user](/iam/concepts/glossary/#user) or [application](/iam/concepts/glossary/#application)) has the appropriate [IAM permission set](/iam/policies-permissions/view-permission-sets/) to perform the desired actions. +- Make sure that no [bucket policy](/object-storage/concepts/#bucket-policy) prevents you from accessing the bucket. If there is one, make sure that it [explicitly allows you](/object-storage/api-cli/bucket-policy/) to perform the desired action. +- Retrieve the logs of your buckets using any Amazon S3-compatible tool to identify the cause of the problem: + - [Rclone](https://rclone.org/docs/#logging) + - [S3cmd](https://s3tools.org/usage) + - [MinIO Client](https://min.io/docs/minio/linux/reference/minio-mc-admin/mc-admin-logs.html#mc-admin-logs) + - [AWS CLI](https://docs.aws.amazon.com/cli/latest/reference/logs/get-log-events.html) + +## Going further + +- Refer to the [Amazon S3 and IAM permissions equivalence](/object-storage/reference-content/s3-iam-permissions-equivalence/) to find the IAM permission set required for each operation. +- When you contact the Support team about Object Storage, include the endpoint (e.g., `s3.fr-par.scw.cloud`), the bucket name, and the object name if the request concerns an object. + + diff --git a/pages/object-storage/troubleshooting/api-key-does-not-work.mdx b/pages/object-storage/troubleshooting/api-key-does-not-work.mdx deleted file mode 100644 index 62841f8eee..0000000000 --- a/pages/object-storage/troubleshooting/api-key-does-not-work.mdx +++ /dev/null @@ -1,60 +0,0 @@ ---- -title: My API key does not work with Object Storage -description: Fix issues with non-functional API keys in Object Storage. -tags: api key bucket object storage aws cli -dates: - validation: 2025-08-11 - posted: 2023-12-15 ---- -import Requirements from '@macros/iam/requirements.mdx' - - - - -- [Owner](/iam/concepts/glossary/#owner) status or [IAM permissions](/iam/concepts/glossary/#permission) allowing you to perform actions in the intended Organization - -## Problem - -When using third-party API or CLI tools, such as the [AWS CLI](/object-storage/api-cli/object-storage-aws-cli/), [MinIO Client](/object-storage/api-cli/installing-minio-client/), or [Rclone](/object-storage/api-cli/installing-rclone/) to manage your Object Storage resources, you may experience one of the following issues connecting to the Scaleway API or listing your resources: - -- Listing your buckets with a third-party tool returns nothing, but you have at least one bucket created in the [Scaleway console](https://console.scaleway.com/object-storage/buckets). - -- The tool returns `An error occurred (Forbidden) when calling the ListObjectsV2 operation: Forbidden` or a similar message. - -- The tool returns a `403` error. - -## Cause - -The API key you used to configure the Amazon S3 third-party tool has a [preferred Project](/iam/concepts/glossary/#preferred-project) assigned. - -If you try to perform Object Storage operations in a Project that is **NOT** the [preferred Project](/iam/concepts/glossary/#preferred-project) using a third-party tool, you will not be able to access your resources, resulting in an error message or an empty response. - -## Solution - -1. Make sure that you are using a valid [API key](https://console.scaleway.com/iam/api-keys). - -2. Make sure that the bearer of the API key (IAM [user](/iam/concepts/glossary/#user) or [application](/iam/concepts/glossary/#application)) has the appropriate [IAM permissions](/iam/policies-permissions/view-permission-sets/) to perform the desired actions. - -3. Make sure that the API key's [preferred Project](/iam/concepts/glossary/#preferred-project) is the same as the one where you are performing actions. You can change the preferred project of your API key: - - by editing it from the [Scaleway console](/iam/credentials/manage-api-keys/#how-to-edit-an-api-key) - - by [overriding it while making an API call](/iam/api-cli/using-api-key-object-storage/#overriding-the-preferred-project-when-making-a-call) -4. Make sure that there is no [bucket policy](/object-storage/concepts/#bucket-policy) preventing the action. If there is one, [update the bucket policy](/object-storage/how-to/create-bucket-policy/) to allow the desired actions to the bearer of the API key. - -You should now be able to list your buckets using a supported Amazon S3-compatible third-party tool. - -## Going further - -- Refer to the documentation on [using IAM API keys with Object Storage](/iam/api-cli/using-api-key-object-storage/) for more information. - -- Refer to the documentation on [bucket policies](/object-storage/api-cli/bucket-policy/) for more information. - -- If you did not manage to identify the error and solve it by yourself, [open a support ticket](/account/support/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) \ No newline at end of file diff --git a/pages/object-storage/troubleshooting/cannot-access-data.mdx b/pages/object-storage/troubleshooting/cannot-access-data.mdx deleted file mode 100644 index ad0648779f..0000000000 --- a/pages/object-storage/troubleshooting/cannot-access-data.mdx +++ /dev/null @@ -1,49 +0,0 @@ ---- -title: I cannot access my objects -description: Troubleshoot issues related to accessing objects in Scaleway Object Storage. -tags: help troubleshooting object storage blocked data locked fail unable impossible -dates: - validation: 2025-07-03 - posted: 2024-06-04 ---- -import Requirements from '@macros/iam/requirements.mdx' - - - - -- [Owner](/iam/concepts/glossary/#owner) status or [IAM permissions](/iam/concepts/glossary/#permission) allowing you to perform actions in the intended Organization - -## Problem - -I am experiencing issues while trying to access my buckets and objects stored on Scaleway Object Storage. - -## Solution - -- Go to the [Status page](https://status.scaleway.com/) to see if there is an ongoing incident on the Scaleway infrastructure. - -- Make sure that you are using a valid [API key](https://console.scaleway.com/iam/api-keys). - -- Make sure that the bearer of the API key (IAM [user](/iam/concepts/glossary/#user) or [application](/iam/concepts/glossary/#application)) has the appropriate [IAM permission set](/iam/policies-permissions/view-permission-sets/) to perform the desired actions. - -- Retrieve the logs of your buckets using any Amazon S3-compatible tool to identify the cause of the problem: - - [Rclone](https://rclone.org/docs/#logging) - - [S3cmd](https://s3tools.org/usage) - - [MinIO Client](https://min.io/docs/minio/linux/reference/minio-mc-admin/mc-admin-logs.html#mc-admin-logs) - - [AWS CLI](https://docs.aws.amazon.com/cli/latest/reference/logs/get-log-events.html) - -- Make sure there is no [bucket policy](/object-storage/concepts/#bucket-policy) that prevents you from deleting the bucket. If there is one, make sure that it [explicitly allows you](/object-storage/api-cli/bucket-policy/) to perform the desired action. - -- Make sure that [Object lock](/object-storage/how-to/use-object-lock/) has not been enabled on the bucket you try to access. - -## Going further - -If you did not manage to identify the error and solve it by yourself, [open a support ticket](/account/support/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/cannot-delete-bucket.mdx b/pages/object-storage/troubleshooting/cannot-delete-bucket.mdx deleted file mode 100644 index bf8922749a..0000000000 --- a/pages/object-storage/troubleshooting/cannot-delete-bucket.mdx +++ /dev/null @@ -1,46 +0,0 @@ ---- -title: I cannot delete my bucket -description: Guide to solving bucket deletion problems in Object Storage. -tags: help troubleshooting object storage delete bucket fail unable impossible -dates: - validation: 2025-07-03 - posted: 2024-06-04 ---- -import Requirements from '@macros/iam/requirements.mdx' - - - - -- [Owner](/iam/concepts/glossary/#owner) status or [IAM permissions](/iam/concepts/glossary/#permission) allowing you to perform actions in the intended Organization - -## Problem - -I cannot delete my Scaleway Object Storage bucket. - -## Solution - -- Make sure there is no [bucket policy](/object-storage/concepts/#bucket-policy) that prevents you from deleting the bucket. - -- If there is a bucket policy, make sure that it [explicitly allows you](/object-storage/api-cli/bucket-policy/) to perform the desired action. - - -- The effective deletion of the bucket will start 24 hours after the deletion request. -- The bucket name will then be available for other customers to use. -- We recommend you erase all objects and versions in the bucket before requesting the deletion -- Files larger than 1 GB can take longer to be deleted. - - -## Going further - -- Refer to the documentation on [how to delete a bucket](/object-storage/how-to/delete-a-bucket/) for more information. - -- If you did not manage to identify the error and solve it by yourself, [open a support ticket](/account/support/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) \ No newline at end of file diff --git a/pages/object-storage/troubleshooting/cannot-restore-glacier.mdx b/pages/object-storage/troubleshooting/cannot-restore-glacier.mdx deleted file mode 100644 index cc512be97c..0000000000 --- a/pages/object-storage/troubleshooting/cannot-restore-glacier.mdx +++ /dev/null @@ -1,62 +0,0 @@ ---- -title: I cannot restore my objects from Glacier -description: Learn to troubleshoot issues when restoring Glacier objects. -tags: help troubleshooting object storage restore glacier fail unable impossible -dates: - validation: 2025-07-03 - posted: 2024-06-04 ---- -import Requirements from '@macros/iam/requirements.mdx' - - - - -- [Owner](/iam/concepts/glossary/#owner) status or [IAM permissions](/iam/concepts/glossary/#permission) allowing you to perform actions in the intended Organization - -## Problem - -I need to retrieve my data from Scaleway Glacier, but the restore operation does not seem to work. - -## Cause - -The time it takes to restore an object depends on the size of the object, and if [multipart](/object-storage/concepts/#multipart-uploads) is configured. If your object is larger than 1 MB, it can take anywhere from a few minutes to 24 hours for restore to start. - -## Solution - -Run the following command in a terminal to retrieve the metadata of the object you want to restore: - -```bash -aws s3api head-object --bucket --key -``` - -An output similar to the following displays: - -```bash -{ - "AcceptRanges": "bytes", - "Restore": "ongoing-request=\"true\"", - "LastModified": "2024-03-13T16:30:44+00:00", - "ContentLength": 5, - "ETag": "\"sd11r084349bc25d97e29393ced1d\"", - "ContentType": "application/octet-stream", - "Metadata": {}, - "StorageClass": "GLACIER" -} -``` - -The `"Restore": "ongoing-request=\"true\"",` line indicates that the restore operation has already started. - -## Going further - -- Refer to the documentation on [how to restore objects from Glacier](/object-storage/how-to/restore-an-object-from-glacier/) for more information. - -- If you did not manage to identify the error and solve it by yourself, [open a support ticket](/account/support/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) \ No newline at end of file diff --git a/pages/object-storage/troubleshooting/deleted-objects-still-billed.mdx b/pages/object-storage/troubleshooting/deleted-objects-still-billed.mdx deleted file mode 100644 index 9af57003dd..0000000000 --- a/pages/object-storage/troubleshooting/deleted-objects-still-billed.mdx +++ /dev/null @@ -1,71 +0,0 @@ ---- -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: -dates: - validation: 2025-07-16 - posted: 2025-07-03 ---- - -import Requirements from '@macros/iam/requirements.mdx' - - - -- [Owner](/iam/concepts/glossary/#owner) status or [IAM permissions](/iam/concepts/glossary/#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: - ```bash - 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: - ```bash - 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/#list-multipart-uploads) command: - ```bash - 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/support/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/deletion-and-billing.mdx b/pages/object-storage/troubleshooting/deletion-and-billing.mdx new file mode 100644 index 0000000000..74d7ce573f --- /dev/null +++ b/pages/object-storage/troubleshooting/deletion-and-billing.mdx @@ -0,0 +1,103 @@ +--- +title: I cannot delete my data or I am billed for objects I cannot see +description: Solve bucket and object deletion issues, and understand unexpected Scaleway Object Storage billing caused by versioning, delete markers, and incomplete multipart uploads. +tags: help troubleshooting object storage delete deletion bucket lock versioning marker multipart billing billed cost fail unable +dates: + validation: 2026-10-13 + posted: 2026-10-13 +--- +import Requirements from '@macros/iam/requirements.mdx' +import TroubleshootingTicket from '@macros/general/troubleshooting-ticket.mdx' + +Deletion and billing issues with Scaleway Object Storage usually come from the same sources: bucket policies, Object Lock, bucket versioning, or incomplete multipart uploads. Find the symptom that matches your situation in the following sections. + + + +- [Owner](/iam/concepts/glossary/#owner) status or [IAM permissions](/iam/concepts/glossary/#permission) allowing you to perform actions in the intended Organization + +## I cannot delete my bucket + +You cannot delete your Scaleway Object Storage bucket. + +### Cause + +A [bucket policy](/object-storage/concepts/#bucket-policy) prevents you from deleting the bucket. + +### Solution + +1. Make sure that no bucket policy prevents you from deleting the bucket. +2. If there is a bucket policy, make sure that it [explicitly allows you](/object-storage/api-cli/bucket-policy/) to perform the desired action. + + +- The effective deletion of the bucket starts 24 hours after the deletion request. +- The bucket name then becomes available for other customers to use. +- Scaleway recommends that you delete all objects and versions in the bucket before requesting the deletion. +- Files larger than 1 GB can take longer to delete. + + +## I cannot delete my objects + +You cannot delete objects, or deleted objects keep existing in the bucket. + +### Cause + +- The object you are trying to delete is protected by [Object Lock](/object-storage/how-to/use-object-lock/). +- The bucket is [versioned](/object-storage/how-to/use-bucket-versioning/), and deleting an object adds a **delete marker** rather than deleting the object. + +### Solution + +#### 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 creates a delete marker, and the targeted object keeps existing. To permanently delete it, list all its 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. + +## I am billed for objects that I cannot see + +The amount billed does not correspond to the objects present in your Scaleway Object Storage bucket. + +### Cause + +- Your [bucket is versioned](/object-storage/how-to/use-bucket-versioning/), and multiple versions of your objects are stored in it, incurring extra costs. +- Some [multipart uploads](/object-storage/api-cli/multipart-uploads/) are ongoing or incomplete. The storage used during the upload is billed, but the object is not visible until the upload is complete. + +### Solution + +#### 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: + ```bash + aws s3api get-bucket-versioning --bucket + ``` + - If versioning is `disabled`, the issue is not linked to versioning. + - If versioning is `enabled` or `suspended`, you may have multiple versions of your objects. +2. List the versions of the objects in your bucket using the [ListObjectVersions](/object-storage/api-cli/bucket-operations/#listobjectversions) command: + ```bash + aws s3api list-object-versions --bucket + ``` + A list of all object versions and delete markers present in the bucket is displayed. +3. Delete the unwanted versions and delete markers using the [DeleteObject](/object-storage/api-cli/object-operations/#deleteobject) command with a version ID specified: + ```bash + aws s3api delete-object --bucket --key --version-id + ``` + +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 for ongoing multipart uploads using the [ListMultipartUploads](/object-storage/api-cli/multipart-uploads/#listing-multipart-uploads) command: + ```bash + aws s3api list-multipart-uploads --bucket + ``` + A list of ongoing multipart uploads is displayed. +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/#aborting-a-multipart-upload). +3. Optionally, [set up lifecycle rules](/object-storage/how-to/manage-lifecycle-rules/) to automatically abort incomplete multipart uploads after a given duration. + +## Going further + +- See the [Object Storage concepts](/object-storage/concepts/#versioning) for more information on versioning. +- When you contact the Support team about Object Storage, include the endpoint (e.g., `s3.fr-par.scw.cloud`), the bucket name, and the object name if the request concerns an object. + + diff --git a/pages/object-storage/troubleshooting/error-messages-access.mdx b/pages/object-storage/troubleshooting/error-messages-access.mdx deleted file mode 100644 index 03e56e291c..0000000000 --- a/pages/object-storage/troubleshooting/error-messages-access.mdx +++ /dev/null @@ -1,51 +0,0 @@ ---- -title: I get error messages when trying to access a bucket -description: Solve errors encountered while trying to access your bucket with Scaleway Object Storage. -tags: help troubleshooting access bucket error message denied deny fail failed -dates: - validation: 2025-10-21 - posted: 2025-03-24 ---- -import Requirements from '@macros/iam/requirements.mdx' - - - - -- [Owner](/iam/concepts/glossary/#owner) status or [IAM permissions](/iam/concepts/glossary/#permission) allowing you to perform actions in the intended Organization - - -## Problem - -One of the following messages display when trying to access your bucket using Scaleway Object Storage: - -- `Failed to preprocess target Error: S3 error: Access Denied` -- `Error: Shared memory connection was closed.` -- `Failed to upload disk 'shadowSpec>'` -- `Agent failed to process method {DataTransfer.SyncDisk}.` - -#### Cause - -The application cannot access the Object Storage resource. - -#### Solution - -If you encounter one or several of the error messages above: - -- Check for issues with your API key by following [this procedure](/object-storage/troubleshooting/api-key-does-not-work/). - -- Make sure that you have the `ObjectStorageFullAccess` [IAM permission](/iam/concepts/glossary/#permission). - -- Make sure that there is no [bucket policy](/object-storage/api-cli/bucket-policy/) preventing the application to access your bucket. - -## Going further - -- If you did not manage to identify the error and solve it by yourself, [open a support ticket](/account/support/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) \ No newline at end of file diff --git a/pages/object-storage/troubleshooting/index.mdx b/pages/object-storage/troubleshooting/index.mdx index 9bb3aa694a..afe85fd076 100644 --- a/pages/object-storage/troubleshooting/index.mdx +++ b/pages/object-storage/troubleshooting/index.mdx @@ -58,19 +58,10 @@ 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 cannot access my buckets or objects](/object-storage/troubleshooting/access-and-authentication/) +- [I cannot delete my data or I am billed for objects I cannot see](/object-storage/troubleshooting/deletion-and-billing/) +- [I cannot restore objects from Glacier or my lifecycle rules do not work](/object-storage/troubleshooting/storage-classes-and-lifecycle/) - [I get 400 Bad Request errors when uploading objects](/object-storage/troubleshooting/400-error-aes256/) -- [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/) -- [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 performance issues or request rate errors](/object-storage/troubleshooting/performance-and-rate-limits/) - [I am experiencing DNS/Edge Services issues](/edge-services/troubleshooting/) -- [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 deleted file mode 100644 index ae1a9d5875..0000000000 --- a/pages/object-storage/troubleshooting/lifecycle-rules-issues.mdx +++ /dev/null @@ -1,51 +0,0 @@ ---- -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 -dates: - validation: 2025-07-16 - posted: 2025-07-03 ---- - -import Requirements from '@macros/iam/requirements.mdx' - - - -- [Owner](/iam/concepts/glossary/#owner) status or [IAM permissions](/iam/concepts/glossary/#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/support/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/lost-bucket-access-bucket-policy.mdx b/pages/object-storage/troubleshooting/lost-bucket-access-bucket-policy.mdx deleted file mode 100644 index 575a69a9f7..0000000000 --- a/pages/object-storage/troubleshooting/lost-bucket-access-bucket-policy.mdx +++ /dev/null @@ -1,82 +0,0 @@ ---- -title: I lost access to a bucket after applying a bucket policy -description: Regain access to buckets lost due to policy issues. -tags: help troubleshooting bucket access lose policy principal -dates: - validation: 2025-07-31 - posted: 2023-12-15 ---- -import Requirements from '@macros/iam/requirements.mdx' -import ImportantBucketPolicy from '@macros/storage/important-bucket-policy.mdx' - - - - -- [Owner](/iam/concepts/glossary/#owner) status or [IAM permissions](/iam/concepts/glossary/#permission) allowing you to perform actions in the intended Organization - -## Problem - -When [creating and applying a bucket policy](/object-storage/api-cli/create-bucket-policy/) to a bucket, you may lose access to the resources within the bucket if your bucket policy was not set properly. - -[Bucket policies](/object-storage/api-cli/bucket-policy/) automatically deny actions to users who are not explicitly allowed by a [statement](/object-storage/api-cli/bucket-policy/#statement). - - - -## Cause - -If you are not explicitly allowed access to the resources in your bucket, you may see one of the following messages: - -- \[CLI\] - `An error occurred (AccessDenied) when calling the ListObjectsV2 operation: Access Denied` - -- \[CLI\] - `403 AccessDenied` - -- \[Console\] - `Failed to update bucket. Retry.` - -- \[Console\] - `Failed to load data. Try refreshing the page.` - -## Solution - - - - -If you have permission to apply a bucket policy, you can also edit it or delete it using the [Scaleway console](https://console.scaleway.com). - -1. Click **Object Storage** on the left side menu of the console. The Object Storage dashboard displays. - -2. Click the **Bucket policies** tab. - -3. Click the name of the bucket policy applied to the lost bucket. - -4. Either edit it to grant yourself access, or delete it and [create a new one](/object-storage/how-to/create-bucket-policy/) - - - -If you have the permission to apply a bucket policy, you can also delete it. To regain access to the resources stored in your bucket, you can either: - -- delete the current bucket policy using the command below. The bucket will become available to every user with [IAM permissions](/iam/concepts/glossary/#permission). - ``` - aws s3api delete-bucket-policy --bucket - ``` -- [apply a new bucket policy](/object-storage/api-cli/create-bucket-policy/) in the bucket to allow yourself (or the desired principal) to perform the desired [storage operations](/object-storage/api-cli/using-api-call-list/). - - - - - - Refer to the [bucket policies overview](/object-storage/api-cli/bucket-policy/) for more information on the different elements of a bucket policy. - - -## Going further - -- Refer to the [bucket policies overview](/object-storage/api-cli/bucket-policy/) for more information on the different elements of a bucket policy. - -- If you did not manage to identify the error and solve it by yourself, [open a support ticket](/account/support/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/low-performance.mdx b/pages/object-storage/troubleshooting/low-performance.mdx deleted file mode 100644 index 5dfe549de4..0000000000 --- a/pages/object-storage/troubleshooting/low-performance.mdx +++ /dev/null @@ -1,44 +0,0 @@ ---- -title: I am experiencing performance issues -description: Diagnose and improve Object Storage performance. -tags: help troubleshooting object storage poor performance issues slow -dates: - validation: 2025-07-01 - posted: 2024-06-04 ---- -import Requirements from '@macros/iam/requirements.mdx' - - - - -- [Owner](/iam/concepts/glossary/#owner) status or [IAM permissions](/iam/concepts/glossary/#permission) allowing you to perform actions in the intended Organization - -## Problem - -I am noticing decreased throughputs, timeouts, high latency, and overall instability on my Scaleway Object Storage deployment. - -## Solution - -- Go to the [Status page](https://status.scaleway.com/) to see if there is an ongoing incident on the Scaleway infrastructure. - -- Retrieve the logs of your buckets using any Amazon S3-compatible tool to identify the cause of the problem: - - [Rclone](https://rclone.org/docs/#logging) - - [S3cmd](https://s3tools.org/usage) - - [MinIO Client](https://min.io/docs/minio/linux/reference/minio-mc-admin/mc-admin-logs.html#mc-admin-logs) - - [AWS CLI](https://docs.aws.amazon.com/cli/latest/reference/logs/get-log-events.html) - -## Going further - -- Refer to the documentation on [how to optimize your Object Storage performance](/object-storage/reference-content/optimize-object-storage-performance/) for more information. - -- If you did not manage to identify the error and solve it by yourself, [open a support ticket](/account/support/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 deleted file mode 100644 index af932b5621..0000000000 --- a/pages/object-storage/troubleshooting/object-deletion-issues.mdx +++ /dev/null @@ -1,50 +0,0 @@ ---- -title: I am experiencing issues while deleting objects -description: Find solutions to problems encountered while deleting objects with Scaleway Object Storage -tags: -dates: - validation: 2025-07-16 - posted: 2025-07-03 ---- - -import Requirements from '@macros/iam/requirements.mdx' - - - -- [Owner](/iam/concepts/glossary/#owner) status or [IAM permissions](/iam/concepts/glossary/#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/how-to/use-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/support/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/performance-and-rate-limits.mdx b/pages/object-storage/troubleshooting/performance-and-rate-limits.mdx new file mode 100644 index 0000000000..8ca8a9bbea --- /dev/null +++ b/pages/object-storage/troubleshooting/performance-and-rate-limits.mdx @@ -0,0 +1,62 @@ +--- +title: I am experiencing performance issues or request rate errors +description: Diagnose low throughput, timeouts, and request rate errors with Scaleway Object Storage. +tags: help troubleshooting object storage poor low performance slow slowness latency timeout throughput rate limit throttle too many requests bottleneck +dates: + validation: 2026-10-13 + posted: 2026-10-13 +--- +import Requirements from '@macros/iam/requirements.mdx' +import TroubleshootingTicket from '@macros/general/troubleshooting-ticket.mdx' + +This page helps you diagnose performance issues and request rate errors with Scaleway Object Storage. For guidance on tuning your deployment, see the documentation on [optimizing your Object Storage performance](/object-storage/reference-content/optimize-object-storage-performance/). + + + +- [Owner](/iam/concepts/glossary/#owner) status or [IAM permissions](/iam/concepts/glossary/#permission) allowing you to perform actions in the intended Organization + +## I am experiencing performance issues + +You notice decreased throughput, timeouts, high latency, and overall instability on your Scaleway Object Storage deployment. + +### Solution + +- Go to the [Status page](https://status.scaleway.com/) to see if there is an ongoing incident on the Scaleway infrastructure. +- Retrieve the logs of your buckets using any Amazon S3-compatible tool to identify the cause of the problem: + - [Rclone](https://rclone.org/docs/#logging) + - [S3cmd](https://s3tools.org/usage) + - [MinIO Client](https://min.io/docs/minio/linux/reference/minio-mc-admin/mc-admin-logs.html#mc-admin-logs) + - [AWS CLI](https://docs.aws.amazon.com/cli/latest/reference/logs/get-log-events.html) +- Apply the [hardware and software recommendations](/object-storage/reference-content/optimize-object-storage-performance/) for Object Storage, such as using [multipart uploads](/object-storage/reference-content/optimize-object-storage-performance/#multipart-uploads) for large objects. + +## I get request rate errors + +An error message similar to one of the following is displayed: + +- `Error: S3 error: Too Many Requests` +- `Code: Too Many Requests` +- `Shared memory connection was closed.` +- `Agent failed to process method {DataTransfer.SyncDisk}.` + +### Cause + +Scaleway Object Storage applies a rate limit on `PUT` operations for safety reasons. + + + The `Shared memory connection was closed.` and `Agent failed to process method {DataTransfer.SyncDisk}.` messages can also indicate an access issue. If the solution below does not solve the issue, see the [documentation on access troubleshooting](/object-storage/troubleshooting/access-and-authentication/#i-get-error-messages-when-accessing-a-bucket). + + +### Solution + +Reduce the number of `PUT` operations sent by your deployment. + + + You may experience reduced throughput due to the limitation. + + +## Going further + +- See the documentation on [optimizing your Object Storage performance](/object-storage/reference-content/optimize-object-storage-performance/). +- When you contact the Support team about Object Storage, include the endpoint (e.g., `s3.fr-par.scw.cloud`), the bucket name, and the object name if the request concerns an object. + + diff --git a/pages/object-storage/troubleshooting/presigned-url-errors.mdx b/pages/object-storage/troubleshooting/presigned-url-errors.mdx deleted file mode 100644 index bb67841580..0000000000 --- a/pages/object-storage/troubleshooting/presigned-url-errors.mdx +++ /dev/null @@ -1,44 +0,0 @@ ---- -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: -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/glossary/#owner) status or [IAM permissions](/iam/concepts/glossary/#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/support/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 deleted file mode 100644 index 79933592b4..0000000000 --- a/pages/object-storage/troubleshooting/request-rate-error.mdx +++ /dev/null @@ -1,52 +0,0 @@ ---- -title: I am experiencing request rate errors -description: Solve issues linked to request rate limitations on Scaleway Object Storage. -tags: help troubleshooting rate limit throttle error bottleneck slowness slow low performance -dates: - validation: 2025-10-21 - posted: 2025-03-24 ---- - -import Requirements from '@macros/iam/requirements.mdx' - - - -- A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/iam/concepts/glossary/#owner) status or [IAM permissions](/iam/concepts/glossary/#permission) allowing you to perform actions in the intended Organization - -## Problem - -An error message similar to one of the following displays: - -- `Error: S3 error: Too Many Requests` -- `Code: Too Many Requests` -- `Shared memory connection was closed.` -- `Agent failed to process method {DataTransfer.SyncDisk}.` - -## Cause - -Scaleway Object Storage applies a rate limit on `PUT` operations for safety reasons. - -## Solution - -Reduce the number of `PUT` operations sent by your deployment. - - -You may experience reduced throughput due to the limitation. - - -### Going further - -Refer to the documentation on [optimizing your Object Storage deployment](/object-storage/reference-content/optimize-object-storage-performance/). - -If you did not manage to identify the error and solve it by yourself, [open a support ticket](/account/support/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) \ No newline at end of file diff --git a/pages/object-storage/troubleshooting/storage-classes-and-lifecycle.mdx b/pages/object-storage/troubleshooting/storage-classes-and-lifecycle.mdx new file mode 100644 index 0000000000..0cc8e4ab71 --- /dev/null +++ b/pages/object-storage/troubleshooting/storage-classes-and-lifecycle.mdx @@ -0,0 +1,69 @@ +--- +title: I cannot restore objects from Glacier or my lifecycle rules do not work +description: Solve Glacier restore issues and lifecycle rule problems with Scaleway Object Storage. +tags: help troubleshooting object storage restore glacier class lifecycle rules expire expiration transition fail unable +dates: + validation: 2026-10-13 + posted: 2026-10-13 +--- +import Requirements from '@macros/iam/requirements.mdx' +import TroubleshootingTicket from '@macros/general/troubleshooting-ticket.mdx' + +This page helps you solve issues related to storage classes and lifecycle rules in Scaleway Object Storage. Find the symptom that matches your situation in the following sections. + + + +- [Owner](/iam/concepts/glossary/#owner) status or [IAM permissions](/iam/concepts/glossary/#permission) allowing you to perform actions in the intended Organization + +## I cannot restore my objects from Glacier + +You need to retrieve your data from the Glacier storage class, but the [restore operation](/object-storage/how-to/restore-an-object-from-glacier/) does not seem to work. + +### Cause + +The time it takes to restore an object depends on the size of the object, and on whether it was uploaded using [multipart upload](/object-storage/concepts/#multipart-uploads). If your object is larger than 1 MB, the restore can take from a few minutes to 24 hours to start. + +### Solution + +1. Run the following command in a terminal to retrieve the metadata of the object you want to restore: + ```bash + aws s3api head-object --bucket --key + ``` + An output similar to the following is displayed: + ```json no-copy + { + "AcceptRanges": "bytes", + "Restore": "ongoing-request=\"true\"", + "LastModified": "2024-03-13T16:30:44+00:00", + "ContentLength": 5, + "ETag": "\"sd11r084349bc25d97e29393ced1d\"", + "ContentType": "application/octet-stream", + "Metadata": {}, + "StorageClass": "GLACIER" + } + ``` +2. Check the `Restore` line. `"Restore": "ongoing-request=\"true\""` indicates that the restore operation has already started. Wait for it to complete. + +## My lifecycle rules do not work as expected + +Your [lifecycle rules](/object-storage/how-to/manage-lifecycle-rules/) do not transition or expire objects as expected. + +### Cause + +- The lifecycle rules are not properly set. +- The prefixes or tags of your objects contain spaces. +- You reached the limit of 500,000 lifecycle jobs per day. + +### Solution + +- Make sure that your [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, [transition](/object-storage/how-to/edit-storage-class/) or [delete](/object-storage/how-to/delete-an-object/) objects manually. +- For expiration rules, use the [HeadObject](/object-storage/api-cli/object-operations/#headobject) command to check which rule applies to a specific object. The `x-amz-expiration` header returns the expiration date and rule ID. + +## Going further + +- See the [lifecycle rules API documentation](/object-storage/api-cli/lifecycle-rules-api/) for more information on lifecycle configuration elements. +- When you contact the Support team about Object Storage, include the endpoint (e.g., `s3.fr-par.scw.cloud`), the bucket name, and the object name if the request concerns an object. + + diff --git a/pages/troubleshooting/index.mdx b/pages/troubleshooting/index.mdx index dda0b3d4fd..6d741d2ecc 100644 --- a/pages/troubleshooting/index.mdx +++ b/pages/troubleshooting/index.mdx @@ -59,7 +59,7 @@ description: Find information, assistance, and solutions related to Scaleway pro - [How to rename an Organization](/account/faq/#can-i-change-the-name-of-my-organization) - [How to delete an account](/account/setup-lifecycle/close-account/) - [How to verify your identity](/account/setup-lifecycle/verify-identity/) - - [My API key does not work with Object Storage](/object-storage/troubleshooting/api-key-does-not-work/) + - [My API key does not work with Object Storage](/object-storage/troubleshooting/access-and-authentication/#my-api-key-does-not-work) - [I need help installing NVIDIA drivers on Ubuntu 22.04](/gpu/troubleshooting/install-nvidia-drivers-ubuntu/) - [I am not allowed to perform actions on resources](/iam/troubleshooting/cannot-use-resources/) diff --git a/tutorials/cicd-github-action-object-storage-sync/index.mdx b/tutorials/cicd-github-action-object-storage-sync/index.mdx index 26de717a23..ca96ad6e0e 100644 --- a/tutorials/cicd-github-action-object-storage-sync/index.mdx +++ b/tutorials/cicd-github-action-object-storage-sync/index.mdx @@ -121,7 +121,7 @@ If your project uses a different build process, replace the `Install dependencie ## Troubleshooting and additional resources -- If you encounter issues while using your API key with Scaleway Object Storage, refer to the [dedicated troubleshooting](/object-storage/troubleshooting/api-key-does-not-work/). +- If you encounter issues while using your API key with Scaleway Object Storage, refer to the [dedicated troubleshooting page](/object-storage/troubleshooting/access-and-authentication/#my-api-key-does-not-work). - Refer to the [official GitHub Actions documentation](https://docs.github.com/en/actions/writing-workflows/quickstart) for more information on how to create and run workflows.