Example for applying expiration policy on Digitalocean Spaces

lifecycle.xml

<LifecycleConfiguration xmlns="http://s3.amazonaws.com/doc/2006-03-01/">
  <Rule>
    <ID>Prune files starting with backup- after 30 days</ID>
    <Prefix>backup-</Prefix>
    <Status>Enabled</Status>
    <Expiration>
      <Days>30</Days>
    </Expiration>
  </Rule>
</LifecycleConfiguration>

Digitalocean Spaces is S3-compatible object storage

It is possible to set expiration policies for the stored files that they are deleted automatically based on rules.

The filesystem is not hierarchical, it is "flat". This means that folders within the Space aren't "directories", but rather an extended prefix of the filename.

I found this helpful: hyperborea.org/tech-tips/s3-expiration

Config:

• Install s3cmd to interact with Spaces.
• Create a lifecycle.xml (at root of repo) text file (see above) and configure one or more <Rule> element(s)
• The <Prefix> element tells the rule what to filter by.
• For example, this rule deletes backup- files after 30 days.
• One could also store these backups within a "folder" on the Space by adding to the prefix.
  • <Prefix>assets/backup-</Prefix>
  • assets/ in this example is a "folder" in the Space.
• Upload the policy with: s3cmd setlifecycle lifecycle.xml s3://example-assets-01
  • NB: example-assets-01 is the bucket's name
• Check the policy with: s3cmd getlifecycle s3://example-assets-01