CDN Providers | IO River Documentation

📄️Managing CDN Accounts

Connect Akamai, CloudFront, Cloudflare, Fastly, Edgio, GCore, and other major CDN providers to your IO River account via API credentials.

Connect a CDN provider to your IO River account with API credentials, then add it to a service and route traffic to it.

Update credentials or commitment for an existing CDN account, or remove a CDN account from IO River after unassigning it from all services.

Create a read-write Akamai API client with Property Manager, CPS, and edge hostname permissions so IO River can manage your Akamai CDN.

Create a scoped Cloudflare API token with account and zone permissions so IO River can manage your Cloudflare CDN.

Create an AWS IAM role with an External ID so IO River can manage your CloudFront distributions.

Create a Fastly automation token with global API access and TLS management permissions so IO River can manage your Fastly CDN.

Configure a GCP IAM member with load balancer permissions so IO River can manage your Google Cloud CDN.

Set up a Key Vault, managed identity, and role assignment so IO River can manage your Azure Front Door CDN.

Required CDNetworks products, permissions, and API endpoints needed to integrate and manage your CDNetworks account with IO River.

Create a read-only Akamai API client so IO River can import your configuration, monitor traffic, and steer traffic without write access.

Generate a read-only Cloudflare API token so IO River can import your configuration, monitor traffic, and steer traffic.

Create an AWS IAM role granting IO River read-only access to import CloudFront configuration, monitor traffic, and steer traffic.

Generate a read-only Fastly automation token so IO River can monitor and steer traffic without modifying your Fastly configuration.

Use an unmanaged CDN provider in IO River for traffic routing and monitoring without providing API credentials or configuration access.