Skip to main content

Troubleshooting — S3 Buckets

AccessDenied when accessing the bucket​

Cause: the keys used are incorrect, the bucket name used is not the actual S3 name, or the user is read-only and is attempting a write.

Solution:

  1. Open the bucket page and note the Bucket name in the Access & Configuration card. Use this name, not the name entered in the wizard: 
    aws --endpoint-url https://<endpoint> s3 ls s3://<s3-bucket-name>/
  2. In the Users & Access card, check the user's permission (Read-only or Read / Write); change it if needed with Edit access.
  3. Check that the Access Key ID and the Secret Access Key are correctly configured in your tool. If the secret key is lost, create a new user.

ListBucket fails on the root​

Cause: a user's keys are limited to their bucket. It is not possible to list all the buckets of the endpoint.

Solution:

  1. Always target the bucket in your commands: 
    aws --endpoint-url https://<endpoint> s3 ls s3://<s3-bucket-name>/
    mc ls hikube/<s3-bucket-name>/
  2. To see all your buckets, use the Object Storage Buckets page of the console.

Credentials not found​

Cause: the secret key is only displayed when the user is created, or no user was created (for example if the bucket was not ready at the end of the wizard).

Solution:

  1. Open the bucket page and check the Users & Access card.
  2. Click Add User to create a user and get new keys.
  3. The endpoint and the S3 name remain available at any time in Access & Configuration.

"No S3 connection information available currently."​

Cause: the bucket is still being provisioned, or it does not have any user yet: the S3 name and the endpoint appear with its first user.

Solution: wait until the bucket status switches to Ready, create a user with Add User if needed, then reload the page. If the status remains Provisioning or switches to Error, contact support with the bucket name and its identifier.

Creation fails: "A bucket with this name already exists."​

Cause: a bucket in the project already has this name.

Solution: go back to the General step of the wizard and choose another Bucket name.

Objects disappeared after deleting a bucket​

Cause: deleting a bucket without locking also deletes all its objects, even if it is not empty, with no possibility of recovery. The confirmation window says so. A locked bucket (WORM) is the exception: its objects are kept after the deletion.

Solution: before deleting a bucket, copy the objects you want to keep, for example to your workstation:

aws --endpoint-url https://<endpoint> s3 sync s3://<s3-bucket-name>/ ./bucket-backup/

Bucket deletion fails​

Solution: retry the deletion from the console. If the error persists, contact support and specify the bucket name.

Slow upload or timeout​

Cause: network issue, large file uploaded without multipart upload.

Solution:

  1. Check your connectivity to the endpoint: 
    curl -s -o /dev/null -w "%{time_total}\n" https://<endpoint>
  2. For large files, use a client that handles multipart upload: aws s3 cp and mc cp do so automatically above a certain size.
  3. If needed, increase client-side parallelism (for example aws configure set default.s3.max_concurrent_requests 20).

AccessDenied with the name displayed when a user was created​

Cause: the S3 client uses the name chosen in the console (for example demo-assets) instead of the actual S3 name (bucket-…). Previous versions of the console could display that name in place of the S3 name when a bucket or a user was created. A user's keys only give access to the actual S3 bucket: any other name is refused with AccessDenied, never NoSuchBucket, even if a bucket with that name exists in the console.

Solution: note the Bucket name in the Access & Configuration card of the bucket page and use it instead in your clients' configuration. The user's keys remain valid.

warning

Do not confuse the bucket's name in the console with its S3 name. Only the latter works with S3 clients.