Log streaming: Wasabi Hot Cloud Storage

Fastly's Real-Time Log Streaming feature can send log files to Wasabi Hot Cloud Storage using Wasabi's S3-compatible API connectivity option. Wasabi Hot Cloud Storage is a static file storage service used by developers and IT teams.

Prerequisites

Before adding Wasabi Hot Cloud Storage as a logging endpoint for Fastly services, we recommend creating an Access Key to which you've given read and write permissions on the bucket.

Adding Wasabi Hot Cloud Storage as a logging endpoint

After you've registered for an Wasabi Hot Cloud Storage account and created an Access Key, follow these instructions to add Wasabi Hot Cloud Storage as a logging endpoint:

  1. Review the information in our Setting Up Remote Log Streaming guide.
  2. Click the Amazon Web Services S3 logo. The Create an Amazon S3 endpoint page appears.

    the create a S3 endpoint page

  3. Fill out the Create an Amazon S3 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 strftime compatible string. Our guide on changing where log files are written provides more information.
    • In the Bucket name field, enter the name of the Wasabi Hot Cloud Storage bucket in which to store the logs.
    • In the Access method area, select User Credentials.
    • In the Access key field, enter the access key associated with the Wasabi account. See Wasabi's Access Key Guide for more information.
    • In the Secret key field, enter the secret key associated with the Wasabi account. See Wasabi's Access Key Guide for more information.
    • In the Period field, optionally enter an interval (in seconds) to control how frequently your log files are rotated. This value defaults to 3600 seconds.
  4. Click the Advanced options link of the Create a new S3 endpoint page.

    the advanced options on the create a new S3 endpoint page

  5. Fill out the rest of the Advanced options of the Create an Amazon S3 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 Domain field, enter s3.wasabisys.com.
    • 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.
    • 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.
    • The Redundancy level option is not useful as Wasabi only provides a single storage class which is most like the standard AWS S3 storage class. Wasabi's Object Storage Class documentation provides more information on using reduced redundancy storage.
    • In the Server side encryption area, optionally select an encryption method to protect files that Fastly writes to your Wasabi Hot Cloud Storage bucket. Valid values are None and AES-256. See Wasabi's guide to this feature which is functionally identical to Amazon's implementation except for lack of support for a key management service.
  6. Click the Create button to create the new logging endpoint.
  7. Click the Activate button to deploy your configuration changes.
Back to Top