> For the complete documentation index, see [llms.txt](https://help.radiantsecurity.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.radiantsecurity.ai/radiant-connectors/network-security/akamai-cdn.md).

# Akamai CDN

Akamai CDN is a content delivery network that serves and accelerates internet-facing web applications from a globally distributed edge, shielding origin servers from volumetric traffic and DDoS attacks. Connecting Akamai CDN forwards edge access logs to Radiant Security via Amazon S3. Radiant uses these logs to correlate external requests against your web applications with identity, endpoint, and authentication activity during AI triage, giving analysts visibility into the traffic behind a web-facing alert.

### Prerequisites

* [ ] Admin access to Akamai Control Center
* [ ] DataStream 2 provisioned on your Akamai contract
* [ ] An AWS account with permissions to create or modify S3 buckets, SNS topics, and IAM policies
* [ ] An S3 bucket where Akamai will store logs (follow [Create an S3 bucket](https://docs.aws.amazon.com/AmazonS3/latest/userguide/create-bucket-overview.html) to create one)
* [ ] An AWS Access Key ID and Secret Access Key with `ListBucket`, `GetObject`, and `PutObject` permissions on the bucket

### Configure Akamai CDN

For full vendor instructions, see [Create a stream](https://techdocs.akamai.com/datastream2/docs/create-stream) and [Stream logs to Amazon S3](https://techdocs.akamai.com/datastream2/docs/stream-amazon-s3) in Akamai's documentation.

Akamai CDN forwards logs through DataStream 2. Create a stream that delivers your edge access logs to the S3 bucket Radiant reads from.

1. Sign in to Akamai Control Center with an admin account.
2. Open the DataStream application and click **Create stream**.
3. On the **Configuration** tab, enter a stream name and select the group and the delivery properties you want to monitor.
4. In **Data sets**, select the fields to include in your logs. Keep the defaults unless you have a specific need.
5. On the **Destination** tab, select **Amazon S3** and enter:
   * **Name**: a description for the destination
   * **Bucket**: your S3 bucket name
   * **Folder path**: the prefix within the bucket where logs are written (e.g., `akamai/`)
   * **Bucket region**: `us-west-2`
   * **Access key ID**: your AWS Access Key ID
   * **Secret access key**: your AWS Secret Access Key
   * **Log format**: JSON
6. Click **Validate & Save**. Akamai writes a verification file to the bucket to confirm access.
7. Continue to the **Summary** tab and click **Activate** to start the stream.

### Configure S3 and add the data connector in Radiant Security

Now that Akamai is writing logs to your S3 bucket, complete the setup by following the [Configure Amazon S3 to forward logs to Radiant Security](https://help.radiantsecurity.ai/radiant-connectors/ingestion-methods/configure-amazon-s3-to-forward-logs-to-radiant-security) guide. That guide walks through:

1. Configuring the bucket policy and creating an SNS topic.
2. Adding the **Amazon Web Services S3** data connector in Radiant Security.
3. Configuring S3 event notifications so new objects trigger ingestion.

When you select the **Amazon Web Services S3** connector in step 2, select the **Akamai CDN** data feed to continue. When the S3 setup is complete, return to this article to verify ingestion.

### Verify ingestion

After the S3 setup is complete, confirm events are reaching Radiant.

1. In Radiant, navigate to [Log Management](https://app.radiantsecurity.ai/logs).
2. Filter by `rs_connectorType:"akamai_cdn"`.
3. Confirm recent events appear.

{% hint style="info" %}
Allow several minutes for events to be parsed, indexed, and available for search.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.radiantsecurity.ai/radiant-connectors/network-security/akamai-cdn.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.