Two-way sync on S3

Two-way sync reflects changes made directly in your bucket back into Salesforce. Read Two-way sync first for what it does and does not cover. This page is the S3-side wiring.

Two-way sync is a premium feature. It is switched on for your org by Sliick. Contact Sliick before you start.

1. Create an SNS topic

Create it in the same region as the bucket, for example sliick-s3-events, with an access policy that allows S3 to publish to it:

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "AllowS3Publish",
      "Effect": "Allow",
      "Principal": { "Service": "s3.amazonaws.com" },
      "Action": "SNS:Publish",
      "Resource": "arn:aws:sns:YOUR_REGION:YOUR_ACCOUNT:Sliick-s3-events",
      "Condition": {
        "ArnLike": { "aws:SourceArn": "arn:aws:s3:::YOUR-BUCKET-NAME" },
        "StringEquals": { "aws:SourceAccount": "YOUR_ACCOUNT" }
      }
    }
  ]
}

2. Subscribe the topic to Sliick

Subscribe the topic to the HTTPS endpoint https://files.sliick.com/webhooks/sns. The confirmation handshake is answered automatically, and the subscription flips to Confirmed within seconds.

3. Create the bucket event notification

On the bucket, go to Properties → Event notifications and create one:

• Events: all object create and all object removal events.
• Destination: the SNS topic from step 1.
• Prefix filter: Salesforce-Files-<your org id>/, or your custom storage root folder followed by /.

S3 validates that it can publish when you save.

The prefix filter keeps the bucket from notifying on anything outside your managed root, including Sliick’s own staging writes. Sliick filters again on its side, so out-of-scope events are discarded either way.

If your storage root folder contains spaces, leave the prefix filter empty. S3’s filter matching silently never matches a prefix with spaces, so filtered events are simply never emitted. Better still, rename the root: the sync save rejects a spaced root for exactly this reason. See Folders and breadcrumbs.

4. Turn sync on in Salesforce

1. Open Sliick Files Setup → Sync.
2. Paste the topic ARN into the SNS topic ARN field.
3. Turn on Enable two-way sync and save.

This registers the topic against your org so deliveries route to your Salesforce instance.

What to expect

An object added under a record’s folder appears on that record within seconds of S3 emitting the event. Two AWS behaviours are worth knowing:

• A freshly created notification configuration can take a while to emit reliably. Deliveries are instant once S3 publishes, but the first events after setup may lag by minutes.
• With Bucket Versioning enabled, an external delete places a delete marker. Sliick reflects that by parking the file in the admin Deleted Files tab: its record links are removed, the entry is kept for the retention window, and Restore removes the marker and re-attaches the file. See Deleted files and restore.

Enabling sync does not import files that were already sitting in the bucket. It applies to changes from that point on.

Not available on S3-compatible providers. Wasabi, Backblaze B2 and MinIO have no SNS equivalent, so there is nothing to point the notification at. See Wasabi.