We've been making changes to how we organize and display our docs. Our work isn't done but we'd love your feedback.
Getting started
Domains & Origins

Domains & Origins
Request settings
Cache settings
Custom VCL
Image optimization

Access Control Lists
Monitoring and testing
Securing communications
Web Application Firewall

Logging endpoints
Non-Fastly services

Streaming logs
Debugging techniques
Common errors

Account info
Account management
User access and control


    Log streaming: SFTP

      Last updated May 31, 2019

    Fastly's Real-Time Log Streaming feature can send log files to SFTP, a secure file transfer subsystem for the Secure Shell (SSH) protocol. Our SFTP endpoint supports both password-based authentication and SSH public-key authentication, with SSH public-key authentication being preferred. To learn more about SSH public-key authentication, or to learn how to generate public and private key pairs, see this guide.

    Adding SFTP as a logging endpoint

    Follow these instructions to add SFTP as a logging endpoint:

    1. Review the information in our Setting Up Remote Log Streaming guide.
    2. Click the SFTP image. The Create an SSH File Transfer Protocol (SFTP) endpoint page appears.

      the create an SFTP endpoint page

    3. Fill out the Create an SSH File Transfer Protocol (SFTP) endpoint fields as follows:
      • In the Name field, type a human-readable name for the endpoint.
      • In the Log format field, optionally type an Apache-style string or VCL variables to use for log formatting. The Apache Common Log format string appears in this field by default.
      • In the Timestamp format field, optionally type a timestamp format for log files. The default is an strftime compatible string. Our guide on changing where log files are written](/en/guides/changing-where-log-files-are-written) provides more information.
      • In the Address field, type the hostname or IP address of the SFTP server. In the port field after the colon, type the port number you're using for SFTP (the default is 22).
      • In the Path field, type the path to use for storing log files. Leaving the default / in this field means the files will be saved in the root path. We describe this variable in more detail in our guide on changing where log files are written.
      • In the User field, type the username used to authenticate to the SFTP server.
      • In the Known hosts field, type a host key for each host you can connect to over SFTP. Each host key you enter must be on its own line. Known hosts entries should match what’s stored in your known_hosts file located in your home directory (or the local account settings if you're working with a Mac or Windows operating system). A known hosts entry looks like this: ecdsa-sha2-nistp256 aBc123xYz…

        where the is the SFTP IP address, ecdsa-sha2-nistp256 is your host key algorithm, and aBc123xYz… is your public key.

      • In the Secret key field, type the SSH secret key used to connect to the server. If both Secret key and Password are entered, the Secret key will be used in preference.
      • In the Password field, type the password used to authenticate to the SFTP server. If both Password and Secret key are entered, the Secret key will be used in preference.
      • In the Period field, type 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 an SSH File Transfer Protocol (SFTP) endpoint page and decide which of the optional fields to change, if any.

      the advanced options on the create an SSH File Transfer Protocol (SFTP) endpoint page

    5. Fill out the Advanced options of the Create an SSH File Transfer Protocol (SFTP) endpoint as follows:
      • 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 PGP public key field, optionally type a PGP public key that Fastly will use to encrypt your log files before writing them to disk. You only can read the contents by decrypting them with your private key. The PGP key should be in PEM (Privacy-Enhanced Mail) format. Our guide on log encryption provides more information.
      • In the Placement area, select where the logging call should be placed in the generated VCL. Valid values are Format Version Default, None, and waf_debug (waf_debug_log). Selecting None creates a logging object that can only be used in custom VCL. See our guide on WAF logging for more information about waf_debug_log.
      • In the Gzip level field, optionally type the level of gzip compression you want applied to the log files. You can specify any whole number from 1 (fastest and least compressed) to 9 (slowest and most compressed). This value defaults to 0 (no compression).
    6. Click the Create button to create the new logging endpoint.
    7. Click the Activate button to deploy your configuration changes.
    Back to Top