Datadog Archives Destination

Overview

Use the Datadog Archives destination to send logs to Amazon S3 for archiving in Datadog-rehydratable format. You can then query these logs with Archive Search. Use Archive Search’s Search & Rehydration mode when you need to re-index results for full platform access.

Notes:

• The Datadog Archives destination compresses logs using gzip.
• Use the Amazon S3 destination if you want to send your logs to Amazon S3 in JSON or Parquet format.

You can also route logs to Snowflake using the Datadog Archives destination.

Prerequisites

To use the Datadog Archives destination, you must install Datadog’s AWS integration so you can configure Datadog Log Archives.

Configure Log Archives

If you already have Datadog Log Archives configured, skip to Set up the destination for your pipeline.

Create an Amazon S3 bucket

1. Navigate to Amazon S3 buckets.
2. Click Create bucket.
3. Enter a descriptive name for your bucket.
4. Do not make your bucket publicly readable.
5. Optionally, add tags.
6. Click Create bucket.

Set up an IAM policy that allows Workers to write to the S3 bucket

1. Navigate to the IAM console.
2. Select Policies in the left side menu.
3. Click Create policy.
4. Click JSON in the Specify permissions section.
5. Copy the below policy and paste it into the Policy editor. Replace <MY_BUCKET_NAME_1> and <MY_BUCKET_NAME_1>/<MY_OPTIONAL_BUCKET_PATH_1> with the information for the S3 bucket you created in the previous section.

   {
    "Version": "2012-10-17",
    "Statement": [
    {
    "Sid": "DatadogUploadAndRehydrateLogArchives",
    "Effect": "Allow",
    "Action": ["s3:PutObject", "s3:GetObject"],
    "Resource": "arn:aws:s3:::<MY_BUCKET_NAME_1>/<MY_OPTIONAL_BUCKET_PATH_1>/*"
    },
    {
    "Sid": "DatadogRehydrateLogArchivesListBucket",
    "Effect": "Allow",
    "Action": "s3:ListBucket",
    "Resource": "arn:aws:s3:::<MY_BUCKET_NAME_1>"
    }
    ]
   }
   

6. Click Next.
7. Enter a descriptive policy name.
8. Optionally, add tags.
9. Click Create policy.

Connect the S3 bucket to Datadog Log Archives

1. Navigate to Datadog Log Forwarding.
2. Click New archive.
3. Enter a descriptive archive name.
4. Add a query that filters out all logs going through log pipelines so that none of those logs go into this archive. For example, add the query observability_pipelines_read_only_archive, assuming no logs going through the pipeline have that tag added.
5. Select AWS S3.
6. Select the AWS account that your bucket is in.
7. Enter the name of the S3 bucket.
8. Optionally, enter a path.
9. Check the confirmation statement.
10. Optionally, add tags and define the maximum scan size for rehydration. See Advanced settings for more information.
11. Click Save.

See the Log Archives documentation for additional information.

Set up the destination for your pipeline

Configure the Datadog Archives destination when you set up an Archive Logs pipeline. You can set up a pipeline in the UI, using the API, or with Terraform. The steps in this section are configured in the UI.

After you select the Datadog Archives destination in the pipeline UI:

1. Enter your S3 bucket name. If you configured Log Archives, it’s the name of the bucket you created earlier.
2. Enter the AWS region the S3 bucket is in.
3. Enter the key prefix.
   • Prefixes are useful for partitioning objects. For example, you can use a prefix as an object key to store objects under a particular directory. If using a prefix for this purpose, it must end in / to act as a directory path; a trailing / is not automatically added.
   • See template syntax if you want to route logs to different object keys based on specific fields in your logs.
   • Note: Datadog recommends that you start your prefixes with the directory name and without a lead slash (/). For example, app-logs/ or service-logs/.
4. Select the storage class for your S3 bucket in the Storage Class dropdown menu. If you are going to archive and rehydrate your logs:
   • Note: Rehydration only supports the following storage classes:
     • Standard
     • Intelligent-Tiering, only if the optional asynchronous archive access tiers are both disabled.
     • Standard-IA
     • One Zone-IA
   • If you wish to rehydrate from archives in another storage class, you must first move them to one of the supported storage classes above.
   • See the Example destination and log archive setup section of this page for how to configure your Log Archive based on your Amazon S3 destination setup.

Optional settings

AWS authentication

Select an AWS authentication option. If you are only using the user or role you created earlier for authentication, do not select Assume role. Select Assume role only if the user or role you created earlier needs to assume a different role to access the AWS resource. The assumed role’s permissions must be explicitly defined.
If you select Assume role:

1. Enter the ARN of the IAM role you want to assume.
   • Note: The user or role you created earlier must have permission to assume this role so that the Worker can authenticate with AWS.
2. (Optional) Enter the assumed role session name and external ID.

Buffering

Toggle the switch to enable Buffering Options. Enable a configurable buffer on your destination to ensure intermittent latency or an outage at the destination doesn’t create immediate backpressure, and allow events to continue to be ingested from your source. Disk buffers can also increase pipeline durability by writing data to disk, ensuring buffered data persists through a Worker restart. See Destination buffers for more information.

• If left unconfigured, your destination uses a memory buffer with a capacity of 500 events.
• To configure a buffer on your destination:
  1. Select the buffer type you want to set (Memory or Disk).
  2. Enter the buffer size and select the unit.
     1. Maximum memory buffer size is 128 GB.
     2. Maximum disk buffer size is 500 GB.
  3. In the Behavior on full buffer dropdown menu, select whether you want to block events or drop new events when the buffer is full.

Example destination and log archive setup

If you enter the following values for your Datadog Archives destination:

• S3 Bucket Name: test-op-bucket
• Prefix to apply to all object keys: op-logs
• Storage class for the created objects: Standard

Then these are the values you enter for configuring the S3 bucket for Log Archives:

• S3 bucket: test-op-bucket
• Path: op-logs
• Storage class: Standard

Secret defaults

These are the defaults used for secret identifiers and environment variables.

Route logs to Snowflake using the Datadog Archives destination

You can route logs from Observability Pipelines to Snowflake using the Datadog Archives destination by configuring Snowpipe in Snowflake to automatically ingest those logs. Snowpipe continuously monitors your S3 bucket for new files and automatically ingests them into your Snowflake tables, ensuring near real-time data availability for analytics or further processing. When logs are collected by Observability Pipelines, they are written to an S3 bucket. To set this up:

1. Configure Log Archives.
2. Set up a pipeline to use Datadog Archives as the log destination. Use the configuration detailed in Set up the destination for your pipeline.
3. Set up Snowpipe in Snowflake. See Automating Snowpipe for Amazon S3 for instructions.

How the destination works

AWS Authentication

The Observability Pipelines Worker uses the standard AWS credential provider chain for authentication. See AWS SDKs and Tools standardized credential providers for more information.

Permissions

The Observability Pipelines Worker requires these policy permissions to send logs to Amazon S3:

• s3:ListBucket
• s3:PutObject
• s3:GetObject

Event batching

A batch of events is flushed when one of these parameters is met. See event batching for more information.

Request a personalized demo