News for hackers. Stuff that matters.
Re:Ptar: Replacing .tgz for petabyte-scale S3 archives by icedchai on Tuesday July 08, 2025 @10:27PM (#44505817)
What if someone deletes a bucket? Then all your versioning is gone...
Re:Ptar: Replacing .tgz for petabyte-scale S3 archives by charcircuit on Tuesday July 08, 2025 @10:41PM (#44505907)
It doesn't let you.
Re:Ptar: Replacing .tgz for petabyte-scale S3 archives by icedchai on Tuesday July 08, 2025 @10:53PM (#44505957)
It can be done if you delete the versions. You’ll need to use the aws cli.
Re:Ptar: Replacing .tgz for petabyte-scale S3 archives by fpoling on Wednesday July 09, 2025 @12:57AM (#44506459)
It cannot be done if S3 objects use the object lock in compliance mode. Such objects cannot be altered in any way and the bucket cannot be deleted until the lock expires .
Re:Ptar: Replacing .tgz for petabyte-scale S3 archives by icedchai on Wednesday July 09, 2025 @04:50AM (#44507693)
Good to know! I’ve never used that feature.
Re:Ptar: Replacing .tgz for petabyte-scale S3 archives by fpoling on Wednesday July 09, 2025 @06:44AM (#44508362)
Note that with such lock mistakes can be costly. If you put into S3 several terabytes by mistake and set the compliance lock duration for 2 years, you will have to pay for that storage for 2 years.
Re:Ptar: Replacing .tgz for petabyte-scale S3 archives by icedchai on Wednesday July 09, 2025 @03:20PM (#44513842)
So not even Amazon can fix this? What if my company goes bankrupt with several TB locked up?
Re:Ptar: Replacing .tgz for petabyte-scale S3 archives by fpoling on Wednesday July 09, 2025 @04:52PM (#44514634)
If you close the account with Amazon, then yes, the data can be deleted. But typically based on contract this will require notifying Amazon and will be extremely visible and can be reverted.

If the company does not pay, then the company breaches its contract and Amazon can delete the data. But typically there would be a warning period.