A destination defines where your audit logs are delivered once they've been collected and batched by a stream. It represents the final storage location or endpoint that receives the log data. Each active stream sends its output directly to its configured destination, making the destination the point at which you take ownership of the logs.

When choosing or configuring a destination, consider how the storage location will be secured, who will need access to the logs, and how downstream systems will consume them.

Supported destination types

Akamai Object Storage. Stream audit logs to an Object Storage bucket.

📘

Akamai Object Storage is currently the only supported destination type. Additional destination types are planned for future releases.

Prerequisites

Before creating a destination, ensure that:

• You meet the Akamai Cloud Pulse requirements for managing streams and destinations
• You have identified or created a storage location where your logs will be delivered
• You have the required credentials or authentication method for that storage location
• You have verified that you can write to that storage location using those credentials
• The storage location meets your organization's requirements for security, retention, and access control

For Akamai Object Storage, this means:

• The object storage bucket exists and is accessible
• You have generated valid access keys for the bucket
• You have write permissions for the bucket
• any required storage-side configuration, such as Object Lock or lifecycle policies, is in place according to your organization's policies

For guidance on securing your Akamai Object Storage destination, see Protect logs in Object Storage.

Destination attributes

A destination has the following attributes:

• Type (type). The destination type. Currently, only Akamai Object Storage is supported.

• Name (label). A unique name for the destination.

• Host (host). The hostname of the service or endpoint that will receive delivered log data. For Object Storage destinations, this is the Object Storage service endpoint associated with your bucket's region.

• Bucket (bucket_name). The name of the Object Storage bucket that receives log deliveries.

• Path (path). The path prefix used for organizing uploaded objects.

• Access key ID (access_key_id). The access key identifier used for authentication.

• Secret access key (access_key_secret). The confidential security credential used with the access key ID to access Object Storage.

Destination versions

Each time a destination is updated—for example, by changing bucket details or path settings—a new version is generated. Versioning provides visibility and traceability for long-lived or frequently updated destinations.

Versioning behaves as follows:

• Previous versions are retained
• The version with the highest version number is the active version
• You can retrieve a destination’s version history to examine past configurations and see how the configuration has changed over time

Managing destinations

You can configure and manage destinations using either Cloud Manager or the Linode API.

• Cloud Manager provides a guided, UI-based workflow for creating and editing destinations. For step-by-step instructions, see Manage Destinations.
• The Linode API offers full programmatic control. To learn the basics of configuring a destination using the Linode API, see this workflow.