upload S3 backups using different storage classes

Comments

2 comments

  • Avatar
    Steven Premeau

    Isn't this something that can be handled via S3 lifecycle rules on the AWS side?

    0
    Comment actions Permalink
  • Avatar
    Will Groehler

    No, this is not the same as lifecycle policies. Lifecycle policies can transition objects from one storage class to another and even delete objects after a certain period of time from the initial upload.

    At the time of upload, one can specify the storage class for the object other than the default STANDARD class.  If using the AWS CLI, this is controlled by the '--storage-class' flag.

    http://docs.aws.amazon.com/cli/latest/reference/s3/cp.html

    The STANDARD storage class doesn't make sense for most archival or backup data because when retrieving and restoring from backup, time to first byte (TTFB) latency of the download is not that important—only the immediate availability of the backup data is important.  Backups are also not intended to be accessed frequently.  Besides that, the STANDARD storage class is almost twice as expensive as STANDARD_IA.

    https://aws.amazon.com/s3/pricing/

    The Reduced Redundancy class is more expensive than the Standard class at this time.  It shouldn't be used, and AWS are planning to deprecate that storage class entirely per https://mysteriouscode.io/blog/aws-s3-storage-classes-pricing-is-not-what-you-think/#update1

    0
    Comment actions Permalink

Please sign in to leave a comment.