@Gary Zhang +1 @Kevin Cai, deleting a S3 storage volume still appears to be a problem in

3.5.4

I experienced the same problem where even after deleting the only table and database that used my storage volume, I still could not delete it. There does not appear to be any alter statement (needed for key rotation) or force parameter implemented on the drop statement. Is there anything on the horizon that will resolve this issue? If not, is there a workaround other than adding a new volume with a different name? If the database is associated with the old storage volume name, can you use an alter statement to change the storage volume to the newly provisioned replacement? Thanks in advance, Chris

alter storage volume, allows you to update volume creds.

That’s great @Kevin Cai, could you provide an example of the syntax? I did try it but couldn’t get it right.

Thank you @Kevin Cai !