Fastly does not provide direct support for third-party services. See Fastly's Terms of Service for more information.
Creating a Cloud Files user and container
Start by creating a Cloud Files user with restricted permissions via Rackspace's cloud control panel.
- Log in to Rackspace's cloud control panel.
- From the user account menu, select User Management.
- Click Create User and fill in all appropriate details.
- In the Product Access section, set User Role to Custom.
- Review the Product Access list. For all items in the Product column, set Role to No Access except the Files item.
- Set the Files item Role to Admin. This will allow you to create the files to store the logs in, but not access any other services.
Next, find the API key for your Cloud Files account. You'll use this later to authenticate using the Cloud Files API.
- From the user account menu, select Account Settings.
- Show the API key in the Login details and make a note of it.
Now that you've created the Cloud Files user and found the API key, you can set up a Cloud Files container.
- From the Storage menu, select Files.
- Click Create Container.
- Assign the container a meaningful name like
Fastly logs - my service.
- Choose a region to keep the files in and make sure the container is private.
- Click Create Container.
Adding a Cloud Files logging endpoint
Once you have created the Cloud Files user and container, follow these instructions to add Cloud Files as a logging endpoint:
- Review the information in our Setting Up Remote Log Streaming guide.
Click the Rackspace Cloud Files Create endpoint button. The Create a Cloud Files endpoint page appears.
- Fill out the Create a Cloud Files endpoint fields as follows:
- In the Name field, enter a human-readable name for the endpoint.
- In the Placement area, select where the logging call should be placed in the generated VCL. Valid values are Format Version Default, waf_debug (waf_debug_log), and None. See our guide on changing log placement for more information.
- In the Log format field, optionally enter an Apache-style string or VCL variables to use for log formatting. Our discussion of format strings provides more information.
- In the Timestamp format field, optionally enter a timestamp format for log files. The default is an
strftimecompatible string. Our guide on changing where log files are written provides more information.
- In the Bucket name field, enter the name of the Cloud Files container in which to store the logs.
- In the User field, enter the username of the Cloud Files user you created above.
- In the Access key field, enter the API key of your Cloud Files account.
- In the Period field, optionally enter an interval (in seconds) to control how frequently your log files are rotated. This value defaults to
Click the Advanced options link of the Create a Cloud Files endpoint page and decide which of the optional fields to change, if any.
- Fill out the Advanced options of the Create a Cloud Files endpoint page as follows:
- In the Path field, optionally enter the path within the bucket to store the files. The path ends with a trailing slash. If this field is left empty, the files will be saved in the bucket's root path. Our guide on changing where log files are written provides more information.
- In the PGP public key field, optionally enter a PGP public key that Fastly will use to encrypt your log files before writing them to disk. You will only be able to read the contents by decrypting them with your private key. The PGP key should be in PEM (Privacy-Enhanced Mail) format. See our guide on log encryption for more information.
- In the Select a log line format area, select the log line format for your log messages. Our guide on changing log line formats provides more information.
- From the Region menu, select the region to stream logs to.
- In the Compression field, optionally select the compression format you want applied to the log files. Our guide on changing log compression options provides more information.
- Click the Create button to create the new logging endpoint.
- Click the Activate button to deploy your configuration changes.