Getting Started

EaaS (Edge as a Service) lets you control Akamai edge delivery and security through a single JSON configuration per tenant. This guide covers the config structure and key concepts to get you started.

What's in a Tenant Config

A tenant config has three main areas. Each is optional — only configure what you need.

Delivery

Caching, routing, headers, redirects, timeouts, and response generation.

{
"delivery_config": {
  "onClientRequest": {
    "features": { ... }
  }
}
}

Full reference →

Match Conditions

Target rules by path, header, IP, geography, and more with AND/OR/NOT logic.

{
"matchAll": {
  "paths": ["/api/*"],
  "methods": ["GET"]
}
}

Full reference →

Security

WAF rules, IP blocking, bot detection, and rate limiting with path/IP exceptions.

{
"security_config": {
  "deny_groups": ["SQL..."],
  "exceptions": { ... }
}
}

Full reference →

Quick Start

The smallest useful config routes traffic to your origin:

tenant.jsonJSON

{
"tenant_id": "my-app",
"delivery_config": {
  "version": "1.0",
  "onClientRequest": {
    "features": {
      "route": {
        "rules": [{
          "args": { "originId": "default_eaas" },
          "pm_variables": {
            "RT_ORIGIN_DNS": "origin.example.com",
            "RT_ORIGIN_HOST_HEADER": "origin.example.com"
          }
        }]
      }
    }
  }
}
}

From here, add caching rules, security policies, headers, and other features as needed.

Key Concepts

Rules

Most features use a rules[] array with match conditions and args. First match wins.

Lists

Named value sets referenced with {{list.name}} to reuse IPs, paths, etc. across rules.

Tenant ID

Identifies the tenant in logs. A string or array of up to 5 strings, max 20 chars each.

Supported HTTP methods

EaaS runs as an Akamai EdgeWorker, and EdgeWorkers execute only for a fixed set of HTTP request methods. Your tenant configuration — every match condition, feature, and rule — is evaluated only for requests using these methods:

GET, POST, PUT, PATCH, DELETE, HEAD, and OPTIONS

supported request methods reference.

Other methods don't run the EdgeWorker

For any other method — including the WebDAV extension methods PROPFIND, PROPPATCH, MKCOL, COPY, MOVE, LOCK, and UNLOCK — the EdgeWorker does not execute, so none of your tenant configuration is applied. The request still flows through the Akamai property; it just isn't processed by EaaS. This is an Akamai EdgeWorker platform constraint, not an EaaS limitation. Handle those methods in the Akamai property directly (for example, with the WebDAV behavior in Property Manager).

OPTIONS is supported by default in the EaaS CDN configuration.

Available Features

Click a feature name to see its full documentation and examples.

Feature	Event Handlers	Description
`caching`	onClientRequest	Control how content is cached with flexible TTL rules and behaviors
`downstreamCaching`	onClientRequest	Control how edge servers instruct client browsers and intermediate proxies to cache content.
`compression`	onClientRequestonClientResponse	Enable gzip compression for specified content types to reduce bandwidth
`setVariable`	onClientRequestonOriginResponseonClientResponse	Set custom variables that can be used for logging and conditional processing
`route`	onClientRequest	Route requests to different origins based on path patterns
`redirect`	onClientRequest	Configure HTTP redirects with custom status codes and destination URLs
`allowPost`	onClientRequest	Enable or disable POST requests with rule-based conditions
`allowPut`	onClientRequest	Enable or disable PUT requests
`allowDelete`	onClientRequest	Enable or disable DELETE requests with rule-based conditions
`allowPatch`	onClientRequest	Enable or disable PATCH requests
`respondWith`	onClientRequestonClientResponse	Return custom responses without contacting the origin
`setHeaders`	onClientRequestonClientResponseonOriginResponse	Add, modify, or remove HTTP headers in requests and responses
`http2`	onClientRequest	No longer supported in tenant file. HTTP/2 is enabled by default for all tenants.
`http3`	onClientRequest	No longer supported in tenant file. HTTP/3 is enabled by default for all tenants.
`webSockets`	onClientRequest	Enable WebSocket support with conditional rules
`chunkedTransferEncoding`	onClientRequest	Enable or disable chunked transfer encoding
`hsts`	onClientRequest	Configure HTTP Strict Transport Security headers to enforce secure connections
`originIpAcl`	onClientRequest	Configure origin IP access control lists. [https://techdocs.akamai.com/origin-ip-acl/docs/welcome](https://techdocs.akamai.com/origin-ip-acl/docs/welcome)
`breadcrumbs`	onClientRequest	Enable breadcrumb tracking for debugging and monitoring
`cacheTag`	onOriginResponse	Tag cached content for easier invalidation
`tenantTag`	onClientRequest	Legacy tenant identification. Use top-level tenant_id instead
`readTimeout`	onClientRequest	Configure timeout for reading from origin with rule-based support
`firstByteTimeout`	onClientRequest	Configure timeout for first byte from origin with rule-based support
`connectTimeout`	onClientRequest	Configure timeout for establishing connection to origin (integer seconds, or rules object for conditional timeouts)