Logs are structured records that document events, actions, and changes that occur within a system or service. They capture what happened, when it happened, and relevant contextual details that help users understand activity over time. Because they offer a historical record, they support troubleshooting, monitoring, and security analysis.

The current release focuses on audit logs that capture control plane operations. These logs record user and system activity in structured JSON Lines (JSONL) format. Audit logs provide an authoritative record of changes and events, forming a critical foundation for security investigations and configuration tracking.

For related concepts and terminology, see the Logs section of Key concepts and terms.

📘

Audit logs are currently in limited availability for select services. Support for additional log types and services is planned for future releases.

How it works

Akamai Cloud Pulse collects events from supported Akamai Cloud services and delivers them to your chosen destination.

To access and view logs, you must:

1. Create a storage location where delivered logs will be stored.
2. Configure a destination that references this storage location.
3. Create a stream that delivers logs to the destination.

The storage location is the underlying location where your log files are written. Currently, Akamai Object Storage buckets are supported. See Protect logs in Object Storage for best practices when creating this bucket.

The destination is the configuration object that defines how Akamai Cloud Pulse accesses and writes data to your storage location. Each destination includes the information required to authenticate, connect, and deliver files to the sink.

The stream defines the flow of logs from supported Akamai Cloud services to your destination. A stream is the mechanism by which audit events are delivered to your storage location.

You can configure Akamai Object Storage, your destination, and your stream using Cloud Manager or the Linode API.

For additional terminology, see Key concepts and terms.

Authentication and access

To create and manage streams and destinations, you must:

• Have full account access
• Authenticate with a valid Personal Access Token (PAT)

You can create a PAT using the Linode API or Cloud Manager.

In Cloud Manager:

1. Open the account menu in the upper right and select API tokens.
2. Click Create A Personal Access Token.
3. Give your PAT a label and set and expiration.
4. Find Monitor and select Read/Write.
5. Click Create Token.

📘

Your access is limited to only the streams and destinations associated with your account.

Pricing and availability

Logs are currently available for the following Akamai Cloud services:

• Identity and Access Management (login events)
• Cloud Firewalls
• VPC
• LKE Enterprise
• Linodes
• Block Storage
• Object Storage (API only)

Logs are available for these services in all core regions.

You can create one audit_logs stream per account at no cost during the limited availability period.

📘

Access to the logs component is currently limited. To request access, contact Support .

Limits and Considerations

• You are limited to creating one stream per account. A single stream automatically delivers log data for all supported services in your account. There is no need to create separate streams for each service.
• Safeguarding log data is a shared responsibility between your organization and Akamai. See the responsibilities overview for more information.
• Audit logs may not reflect all billing-related events with complete accuracy. For consistent and reliable reconciliation, use the Billing API.