Object Storage as a Backup Target • Remove existing S3 immutable backups before compliance period?

Our current backup system has S3 immutable buckets in capacity tier to offload data as soon as they appear on the performance tier.

We are currently undergoing a major overhaul of the backup system including completely wiping out the existing performance storage and starting off new (the way I set up the repository size and other settings are not scaling well, and the S3 bill is blowing up as a result).

I understand the concept of compliance mode S3 immutable storages and the inability to conventionally remove immutable buckets even using AWS console. But the migration period means I have to run parallel backups with the existing buckets and the new buckets for at least a month and a half. This would not be feasible since our office payment card has a monthly dollar limit (3rd world problems). Hence, I will need to remove the existing buckets somehow, and then create new buckets.

So my question is, how do I completely remove the immutable buckets before hitting the object lock date? Can i remove the associated user, thereby removing the S3 buckets associated with it? (It is under an IAM user created by a root user in our AWS organization, and there is another unrelated root user in the same organization as well). Or would I actually need to remove the whole organization from AWS to make this possible? Or is either of these options even possible?

Thanks,
Sam

Statistics: Posted by CatMDV — Jul 14, 2024 8:51 am

---