Skip to main content
Sumo Logic

Forwarding Data from Sumo Logic to S3

You can configure Sumo to send ingested, indexed data—specifically partitions and scheduled views—to AWS S3. This feature is useful if you want to retain the information for longer than your Sumo data retention policy allows.  

Messages are buffered during data ingest for approximately 5 minutes, or until 100 MB of data is received. The messages are added to a CSV file, compressed with .gzip, and forwarded to AWS S3. Each CSV file is stored as a new file in the S3 bucket, even if the file only contains updates.

Data forwarding to S3 is supported for partitions or scheduled views only. You can configure different data forwarding configurations for different partitions and views.

After data forwarding is configured, file objects are posted to your configured bucket in the format described in File Format for Data Forwarding to an Amazon S3 Bucket

Configure data forwarding from Sumo to S3

Follow the steps below to set up Sumo to forward indexed data to S3.

Grant Sumo access to target bucket

Follow the instructions in Grant Access for Data Forwarding from Sumo Logic to S3 to allow Sumo to write to the destination bucket—you'll generate the Access Key ID and Secret Access Key that you must supply in the following step. 

Configure S3 bucket as data forwarding destination

  1. Make sure to have your AWS Key ID and Secret Access Key to allow Sumo Logic to write to the S3 bucket.
  2. In Sumo choose Manage Data > Settings > Data Forwarding (Manage > Data Forwarding in the classic UI).
  3. Click + to add a new destination.
  4. Select Amazon S3 for Destination Type.
  5. Configure the following:
    • Destination Name. Enter a name to identify the destination.
    • Bucket Name. Enter the exact name of the S3 bucket. The description is optional.
    • Access Key ID. Enter the Access Key ID generated for Sumo.
    • Secret Access Key. Enter the Secret Access Key generated for Sumo.
    • S3 Region. Select the S3 region or keep the default value of Others. The S3 region must match appropriate S3 bucket created in your Amazon account. For example, if the bucket is in Seoul, Seoul must be selected in here.
    • Enable S3 server-side encryption. Select the check box if you want the forwarded data to be encrypted.
    • Active. Select this check box to enable data forwarding for the S3 bucket. To start data forwarding you will also need to enable forwarding for the desired indexes, as described below in this topic.
  6. Click Save.

If Sumo is able to verify the S3 credentials, the destination will be added to the list of destinations, and you can start data forwarding for specific partitions or scheduled views, as described in the following section.


Start data forwarding to S3 

  1. In Sumo Logic, go to Manage Data > Settings > Partitions (Manage > Indexes or Manage > Partitions in the classic UI).
  2. Click the three-dot icon to the right of the index for which you want to enable data forwarding and select Edit Data Forwarding.
    You can also enable data forwarding when you first create a partition or scheduled view by selecting the Enable Data Forwarding check box.
  3. Select the forwarding destination. 
    You can choose a previously configured destination, or click New Amazon S3 Destination to set up a new one. If you select the new option, you’ll see all of the settings to add a new data forwarding destination. See the previous procedure in this topic for instructions on configuring the settings.
  4. In File Format, you can specify how the forwarded files will be named. Enter a path name or other file format and include any of the following variables, as in the previous screenshot: 

    {day} Replace with the day of the year in the yyyy-MM-dd format.
    {hour} Replace with hour in day (0-23).
    {minute} Replace with minute in hour.
    {second} Replace with second in hour.
    {uuid} Replace with a unique, randomly generated identifier (UUID).

    If you leave this field blank, the default format {index}_{day}_{hour}_{minute}_{second} is used, where index is the name of the index the message belongs to.

  5. Click Save to save your changes and start forwarding data. 

See Error and alert conditions below for examples of errors that can occur.

S3 error and alert conditions

An error or alert condition can occur with S3 data forwarding destination for the following reasons:

  • If Sumo Logic is not able to verify the S3 credentials when the destination is saved, an error message indicates that the credentials were rejected by Amazon. If this occurs, verify Access Key ID, Secret Access Key and the bucket configuration, reselect the Active check box, and save again.
  • Errors and alerts that are generated after the destination has been successfully saved and started are shown on the partitions page. 
    Partitions data forwarding 
  • Hover over the icon to display the message​.
    Data fowarding error 
  • In this example, Sumo Logic has disabled data forwarding due to errors in connecting to the S3 bucket. This occurs if the Amazon account or credentials change so that Sumo Logic is no longer able to authenticate to the bucket.