Thanks to Tigris for the prompt reply

, ,
1

I met a issue, have been fighting around with it for a few hours, finally I sent a query mail to tigris’ customer service email. I got very helpful replies!

Lessons learned: don’t hesitate to ask questions; just be succinct, polite, and provide enough contextual information.

Browse the storyline below (with timestamps) :wink:

Unable to delete bucket (me)

On Sun, 13 Oct 2024 at 16:42

AWS_ACCESS_KEY_ID: tid_zkrUeBLpqV_TOdaZzjYefcGEZJrZJqQHvmidyMx_VJtknmcWhC
AWS_ENDPOINT_URL_S3: https://fly.storage.tigris.dev 
AWS_REGION: auto
AWS_SECRET_ACCESS_KEY: tsec_TjMm0vp3_8XDIEBmDCUx4Yn3h-3O63HxAAh-IQCi864h4k5p4S4DxgrBQBh5kCJrBBRMXv
BUCKET_NAME: public-iiij

Either with “aws s3api delete-bucket” or “fly storage destroy”, I’m unable to delete the previously mentioned bucket. Why do I want to delete this bucket? Because it’s not usable for unknown reasons. When I upload a file to it, I get this error:

An error occurred (InvalidAccessKeyId) when calling the PutObject operation: The access key ID you provided does not exist in our records.

Could you please take a look?

Thanks a lot!

Buwei Liao

(tigris)

On Mon, 14 Oct 2024 at 00:27

Hello Buwei,

It appears that the key you mentioned is deleted and that is why you are not able to perform operations using it.

Thanks, Jigar

(me)

On Mon, 14 Oct 2024 at 06:48

Thanks Jigar for the quick reply.
I also created an access key able to manage all buckets, with this access key configured I still cannot delete the mentioned public-iiij bucket. I really can’t figure it out. Could you shed some light on this issue?

Best regards,

Buwei Liao

(me)

On Mon, 14 Oct 2024 at 07:41

Sorry, I just did it. I have successfully deleted the bucket with the aws s3api delete-bucket command. It’s just the fly storage destroy command that doesn’t work.

May I just add one more question? Is the fly storage commands a wrapper around the aws s3 or aws s3api for convenience?

Thanks a lot!

(tigris)

On Mon, 14 Oct 2024 at 08:12

Hi Buwei,

Yes fly storage provides simpler access to common storage operations which includes creation of bucket, deletion of bucket and so on. Let me clarify what has happend

  • you attempted to create bucket named public on 2024-10-12 01:51:28.927 (UTC) via Fly cli.
  • because this bucket already existed, Tigris added suffix to your requested name and created bucket named public-iiij
  • Fly cached the bucket name as public and then anywhere you tried to perform operation on your bucket, it pointed those operations on bucket named public
  • While this bucket (public) is not owned by you, Tigris rejected requests and that is why you were unable to delete this bucket via Fly cli.

We have fixed the issue, in case if the bucket already exists, it will simply return error in the first place. Going forward operating via Fly CLI should not create such out of sync issues for you.

Thanks, Jigar

3 Likes
2

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.