Before FilePreserve can archive anything, a Salesforce admin needs an Amazon S3 bucket and an IAM user in the company's own AWS account, then points FilePreserve's Named Credential and External Credential at them; it takes roughly 20 to 30 minutes.

The checklist

  1. Assign the FilePreserve permission set to the people who will use it.
  2. Create the S3 bucket in your own AWS account. Enabling S3 Object Lock is recommended if immutability matters to you.
  3. Create an IAM user and policy with access to that bucket.
  4. Point the Named Credential at your bucket's endpoint, and the External Credential at your AWS credentials.
  5. Confirm the connection works, then create your first Archive Job.

FilePreserve ships with a non-functional placeholder for storage, on purpose, so a misconfigured org can never silently write your data somewhere else. Nothing is archived until you connect your own bucket.

Which storage providers work

Amazon S3 is the only supported and tested backend. S3-compatible services that use the same signing scheme, such as Backblaze B2, Wasabi and Cloudflare R2, would likely work by repointing the endpoint, but that has not been tested, so treat it as untested, not supported. Azure Blob Storage and Google Cloud Storage use a different signing scheme and will not work as shipped.

Test small first

If you leave an Archive Job's filter criteria blank, it archives every matching record's files immediately. For a first test, scope the filters to a small set of records, confirm the run succeeded on the dashboard and that an archive entry appears on a record, then widen.

Full steps

The exact click-by-click instructions are in the setup guide. Availability: FilePreserve is being prepared for AppExchange and is not yet listed there, so you can join the waitlist for early access.

Related

This guide describes how FilePreserve works and is not legal or compliance advice. Reviewed against the FilePreserve product documentation. Have a question? hello@filepreserve.com.