Akamai Platform Configuration and Property Management
The mental model
Akamai configuration is organized around properties (a named set of rules for a hostname/path space), rule trees (ordered match criteria with behaviors), and behaviors that implement features. A property is versioned; changes are made in a new version, validated, then activated on a staging or production network. Hostnames must have DNS mapped (typically via CNAME or Edge DNA/zone delegation) and be associated with the property. Certificates (CPS or third-party) must cover the hostname before HTTPS works.
Concepts to know
Match criteria include hostname, path, file extension, query string, and request headers; the first matching rule wins in a default top-down evaluation, so rule order is a classic exam trap. Origin behavior defines origin server, hostname handling, and forward host header. Other behaviors include caching, compression, redirects, and header manipulation. Understand the difference between property-level settings and account/network-level settings, and that activation propagates across many edge servers, so it is not instantaneous.
Traps
- Assuming an inactive version takes effect - only the activated version serves traffic.
- Putting a broad catch-all rule above a specific rule, causing the specific rule never to match.
- Forgetting that a certificate or hostname mapping is a prerequisite for TLS.
- Confusing staging activation (testing) with production activation.
Rule of thumb
Order rules from most specific to most general, and treat every change as: edit version → validate → activate staging → test → activate production.