Skip to main content
Version: 1.5.0

DigitalOcean Spaces

DigitalOcean Long Term Storage

Synopsis

Creates a target that writes log messages to DigitalOcean Spaces with support for various file formats and authentication methods. The target handles large file uploads efficiently with configurable rotation based on size or event count. DigitalOcean Spaces provides simple, scalable object storage with built-in CDN integration.

Schema

- name: <string>
description: <string>
type: digitaloceans3
pipelines: <pipeline[]>
status: <boolean>
properties:
key: <string>
secret: <string>
region: <string>
endpoint: <string>
part_size: <numeric>
bucket: <string>
buckets:
- bucket: <string>
name: <string>
format: <string>
compression: <string>
extension: <string>
schema: <string>
name: <string>
format: <string>
compression: <string>
extension: <string>
schema: <string>
max_size: <numeric>
batch_size: <numeric>
timeout: <numeric>
field_format: <string>
interval: <string|numeric>
cron: <string>
debug:
status: <boolean>
dont_send_logs: <boolean>

Configuration

The following fields are used to define the target:

FieldRequiredDefaultDescription
nameYTarget name
descriptionN-Optional description
typeYMust be digitaloceans3
pipelinesN-Optional post-processor pipelines
statusNtrueEnable/disable the target

DigitalOcean Spaces Credentials

FieldRequiredDefaultDescription
keyY-DigitalOcean Spaces access key
secretY-DigitalOcean Spaces secret key
regionY-DigitalOcean region (e.g., nyc3, sfo3, ams3, sgp1)
endpointY-Spaces endpoint URL (format: https://<region>.digitaloceanspaces.com)

Connection

FieldRequiredDefaultDescription
part_sizeN5Multipart upload part size in megabytes (minimum 5MB)
timeoutN30Connection timeout in seconds
field_formatN-Data normalization format. See applicable Normalization section

Files

FieldRequiredDefaultDescription
bucketN*-Default Spaces bucket name (used if buckets not specified)
bucketsN*-Array of bucket configurations for file distribution
buckets.bucketY-Spaces bucket name
buckets.nameY-File name template
buckets.formatN"json"Output format: json, multijson, avro, parquet
buckets.compressionN"zstd"Compression algorithm
buckets.extensionNMatches formatFile extension override
buckets.schemaN*-Schema definition file path (required for Avro and Parquet formats)
nameN"vmetric.{{.Timestamp}}.{{.Extension}}"Default file name template when buckets not used
formatN"json"Default output format when buckets not used
compressionN"zstd"Default compression when buckets not used
extensionNMatches formatDefault file extension when buckets not used
schemaN-Default schema path when buckets not used
max_sizeN0Maximum file size in bytes before rotation
batch_sizeN100000Maximum number of messages per file

* = Either bucket or buckets must be specified. When using buckets, schema is conditionally required for Avro and Parquet formats.

note

When max_size is reached, the current file is uploaded to Spaces and a new file is created. For unlimited file size, set the field to 0.

Scheduler

FieldRequiredDefaultDescription
intervalNrealtimeExecution frequency. See Interval for details
cronN-Cron expression for scheduled execution. See Cron for details

Debug Options

FieldRequiredDefaultDescription
debug.statusNfalseEnable debug logging
debug.dont_send_logsNfalseProcess logs but don't send to target (testing)

Details

The DigitalOcean Spaces target provides simple, developer-friendly object storage with comprehensive file format support. Spaces includes built-in CDN functionality powered by DigitalOcean's global network for fast content delivery.

Authentication

Requires DigitalOcean Spaces access credentials. Access keys can be generated through the DigitalOcean Control Panel under API settings. Each key provides full access to all Spaces in the account.

Endpoint Configuration

The endpoint URL follows the pattern https://<region>.digitaloceanspaces.com where <region> is your chosen DigitalOcean datacenter location.

Available Regions

DigitalOcean Spaces is available in the following regions:

Region CodeLocation
nyc3New York City, USA
sfo3San Francisco, USA
ams3Amsterdam, Netherlands
sgp1Singapore
fra1Frankfurt, Germany
syd1Sydney, Australia

File Formats

FormatDescription
jsonEach log entry is written as a separate JSON line (JSONL format)
multijsonAll log entries are written as a single JSON array
avroApache Avro format with schema
parquetApache Parquet columnar format with schema

Compression

All formats support optional compression to reduce storage costs and transfer times. Compression is applied before upload.

FormatCompression Options
JSON/MultiJSONzstd (default), gzip
Avronull, deflate, snappy, zstd
Parquetuncompressed, gzip, snappy, zstd, brotli, lz4

File Management

Files are rotated based on size (max_size parameter) or event count (batch_size parameter), whichever limit is reached first. Template variables in file names enable dynamic file naming for time-based partitioning.

Templates

The following template variables can be used in file names:

VariableDescriptionExample
{{.Year}}Current year2024
{{.Month}}Current month01
{{.Day}}Current day15
{{.Timestamp}}Current timestamp in nanoseconds1703688533123456789
{{.Format}}File formatjson
{{.Extension}}File extensionjson
{{.Compression}}Compression typezstd
{{.TargetName}}Target namemy_logs
{{.TargetType}}Target typedigitaloceans3
{{.Table}}Bucket namelogs

Multipart Upload

Large files automatically use multipart upload protocol with configurable part size (part_size parameter). Default 5MB part size balances upload efficiency and memory usage.

Multiple Buckets

Single target can write to multiple Spaces buckets with different configurations, enabling data distribution strategies (e.g., raw data to one bucket, processed data to another).

Schema Requirements

Avro and Parquet formats require schema definition files. Schema files must be accessible at the path specified in the schema parameter during target initialization.

CDN Integration

DigitalOcean Spaces includes built-in CDN functionality. Files stored in Spaces can be served globally through the CDN with no additional configuration required.

Cost Structure

DigitalOcean Spaces offers predictable pricing with no egress fees within reasonable limits, making it cost-effective for applications with moderate data transfer requirements.

Examples

Basic Configuration

The minimum configuration for a JSON Spaces target:

targets:
- name: basic_spaces
type: digitaloceans3
properties:
key: "DO00ABC123XYZ456"
secret: "abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789"
region: "nyc3"
endpoint: "https://nyc3.digitaloceanspaces.com"
bucket: "datastream-logs"

Multiple Buckets

Configuration for distributing data across multiple Spaces buckets with different formats:

targets:
- name: multi_bucket_export
type: digitaloceans3
properties:
key: "DO00ABC123XYZ456"
secret: "abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789"
region: "sfo3"
endpoint: "https://sfo3.digitaloceanspaces.com"
buckets:
- bucket: "raw-data-archive"
name: "raw-{{.Year}}-{{.Month}}-{{.Day}}.json"
format: "multijson"
compression: "gzip"
- bucket: "analytics-data"
name: "analytics-{{.Year}}/{{.Month}}/{{.Day}}/data_{{.Timestamp}}.parquet"
format: "parquet"
schema: "<schema definition>"
compression: "snappy"

Parquet Format

Configuration for daily partitioned Parquet files:

targets:
- name: parquet_analytics
type: digitaloceans3
properties:
key: "DO00ABC123XYZ456"
secret: "abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789"
region: "ams3"
endpoint: "https://ams3.digitaloceanspaces.com"
bucket: "analytics-lake"
name: "events/year={{.Year}}/month={{.Month}}/day={{.Day}}/part-{{.Timestamp}}.parquet"
format: "parquet"
schema: "<schema definition>"
compression: "snappy"
max_size: 536870912

High Reliability

Configuration with enhanced settings:

targets:
- name: reliable_spaces
type: digitaloceans3
pipelines:
- checkpoint
properties:
key: "DO00ABC123XYZ456"
secret: "abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789"
region: "sgp1"
endpoint: "https://sgp1.digitaloceanspaces.com"
bucket: "critical-logs"
name: "logs-{{.Timestamp}}.json"
format: "json"
timeout: 60
part_size: 10

With Field Normalization

Using field normalization for standard format:

targets:
- name: normalized_spaces
type: digitaloceans3
properties:
key: "DO00ABC123XYZ456"
secret: "abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789"
region: "fra1"
endpoint: "https://fra1.digitaloceanspaces.com"
bucket: "normalized-logs"
name: "logs-{{.Timestamp}}.json"
format: "json"
field_format: "cim"

Debug Configuration

Configuration with debugging enabled:

targets:
- name: debug_spaces
type: digitaloceans3
properties:
key: "DO00ABC123XYZ456"
secret: "abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789"
region: "nyc3"
endpoint: "https://nyc3.digitaloceanspaces.com"
bucket: "test-logs"
name: "test-{{.Timestamp}}.json"
format: "json"
debug:
status: true
dont_send_logs: true