Setting Surrogate-Key headers for Amazon S3 origins

  Last updated August 16, 2018

You can mark content with a surrogate key and use it to purge groups of specific URLs at once without purging everything, or purging each URL singularly. On the Amazon S3 side, you can use the x-amz-meta-surrogate-key header to mark your content as you see fit, and then on the Fastly side set up a Header configuration to translate the S3 information into the header we look for.

IMPORTANT: Pay close attention to the capitalization. Amazon S3 only accepts all lowercase header names.

Follow these instructions to set Surrogate-Key headers for Amazon S3 origin servers:

1. Log in to the Fastly web interface and click the Configure link.
2. From the service menu, select the appropriate service.
3. Click the Edit configuration button and then select Clone active. The Domains page appears.
4. Click the Content link. The Content page appears.

5. Click the Create header button. The Create a header page appears.

   

6. Fill out the Create a header fields as follows:
   • In the Name field, type a human-readable name for the header. This name is displayed in the Fastly web interface.
   • From the Type menu, select Cache, and from the Action menu, select Set.
   • In the Destination field, type http.Surrogate-Key.
   • In the Source field, type beresp.http.x-amz-meta-surrogate-key.
   • From the Ignore if set menu, select No.
   • In the Priority field, type 10.
7. Click the Create button to create your header.
8. Click the Activate button to deploy your configuration changes.

NOTE: There are several limitations to surrogate keys. See the surrogate key limitations section for more information.

Was this guide helpful?

Yes No

Tell us what worked and what we could do better.

Do not use this form to send sensitive information. If you need assistance, contact support@fastly.com.

Back to Top