You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now gobackup does not specify a storage class when uploading objects to S3, resulting in every object beginning in the STANDARD class. We can transition objects to a different class using lifecycle rules on the S3 bucket but that has some limitations (ie. there's a minimum of 30 days from object creation in STANDARD before transitioning to another class).
It would be useful to have the possibility of specifying the S3 storage class to create new objects directly in a class different from STANDARD.
The text was updated successfully, but these errors were encountered:
Right now
gobackup
does not specify a storage class when uploading objects to S3, resulting in every object beginning in theSTANDARD
class. We can transition objects to a different class using lifecycle rules on the S3 bucket but that has some limitations (ie. there's a minimum of 30 days from object creation inSTANDARD
before transitioning to another class).It would be useful to have the possibility of specifying the S3 storage class to create new objects directly in a class different from
STANDARD
.The text was updated successfully, but these errors were encountered: