Home
Use cases for AMD
Here you'll find topics that cover how to integrate various optional functionality via behaviors and rules in your AMD property.
How to add Breadcrumbs
The "Breadcrumbs" feature looks to improve real-time visibility of performance-impacting and error conditions for media streaming with AMD.
The Breadcrumbs response
The Breadcrumbs response header that's sent to a player includes various sub-fields of data.

Welcome to Adaptive Media Delivery
Adaptive Media Delivery (AMD) delivers streaming video by adapting, real-time to available bandwidth and providing a quality viewing experience with superior scalability, reliability, availability and reach.
Supported media formats with AMD
Adaptive Media Delivery (AMD) reliably delivers prepared, pre-segmented HTTP-based Live and On-Demand streaming media.
Get environment information
You need to review your environment and gather some specific pieces of information before creating your AMD property configuration.
Create your origin server DNS record
The origin server is the location from which Akamai Edge servers retrieve your content before serving it to end users.
Player integration requirements
AMD is designed for use with standard media players, such as an Open Source Media Framework (OSMF) player, JWPlayer, Flowplayer, HLS.js, and DASH.js. For the most part, modifications to the player are not necessary to deliver content through AMD.
Create a new property
To set up AMD, you first need to create a new property in Control Center.
Define Property Hostnames
You use this content panel to create your Property hostname to Edge hostname associations. These associations play a key role in getting your site, application or content out to our Edge servers, for access to requests from your clients.
Define Property Variables (optional)
Variable support gives you more control over your configuration. It's typically implemented for more complex properties.
Define Property Configuration Settings
The Property Configuration Settings content panel contains the rules for your property. Rules consist of match criteria and behaviors. If a request meets the conditions in a rule's match criteria, the behaviors in that rule are applied.
Finalize your AMD property
Once you've defined all Rules and Behaviors for your property, you need to address any noted conflicts or issues.
You may need to update your origin configuration
Other recommended tasks
This includes some highly recommended tasks such as setting up test objects, activating log delivery and alerts, scheduling reports, and other tasks.
Test your AMD property configuration
Go "Live"
Once all of the configuration steps and testing are complete, you can go live to begin delivering your content.
Use cases for AMD
Here you'll find topics that cover how to integrate various optional functionality via behaviors and rules in your AMD property.
- How to upgrade a request from HTTP to HTTPS
  Add the HTTP to HTTPS Upgrade behavior to your property if you want to convert HTTP (non-secure) requests from your clients to use secure HTTPS between the Akamai edge and your origin server.
- How to include the Vary HTTP header
  Do you need to support the inclusion of vary HTTP headers for your content? AMD automatically strips these headers out of requests to support caching for faster delivery.
- How to add AMD origin failover
  Adaptive Media Delivery (AMD) failover lets you switch from one origin to another, or send a specific HTTP status code to the requesting client if a failure occurs on your primary origin.
- How to add Bit Rate Limiting
  Bit Rate Limiting lets you control the rate that Akamai serves Adaptive Media Delivery (AMD) content to end users. You can optionally vary the speed based on file size or elapsed download time.
- How to add Breadcrumbs
  The "Breadcrumbs" feature looks to improve real-time visibility of performance-impacting and error conditions for media streaming with AMD.
  - Configure Breadcrumbs
    To add support for breadcrumbs, you need to apply various settings in a new or existing property configuration.
  - The Breadcrumbs response
    The Breadcrumbs response header that's sent to a player includes various sub-fields of data.
- How to add Cloud Access Manager
  Use Cloud Access Manager to securely store and manage your cloud origin credentials in the form of access keys.
- How to add Content Targeting - Protection
  Content targeting ("geo protection") allows you to permit or deny access to your content based on region-specific values associated with the requesting client.
- How to add Edge IP Binding
  Edge IP Binding (EIPB) lets you deliver traffic from a small, static set of IP addresses in an scalable manner.
- How to add EdgeWorkers
  Use EdgeWorkers to help optimize content delivery, by deploying JavaScript functions at the edge.
- How to add Enhanced Proxy Detection
  Enhanced Proxy Detection (EPD) lets you use services provided by our data provider, GeoGuard to apply proxy detection and location spoofing protection.
- How to add Manifest Personalization for DASH
  With the increasing demand for online content, you may be challenged to deliver even more when network and bandwidth capacity are limited. To help with this, you can include Manifest Personalization ("MPer") with AMD to limit or restrict the maximum bit rate for DASH content served to your customers.
- How to add Manifest Personalization for HLS
  This lets you enhance the viewing experience by individualizing Apple HTTP Live Streaming (HLS) video quality to best suit your end user's devices.
- How to add Media Encryption
  This functionality encrypts individual media segments, before delivering them to a requesting client.
- How to use Mixed Mode with AMD
  Mixed Mode lets you use the same use case-based behaviors in multiple rules in the same Adaptive Media Delivery (AMD) property. This lets you simplify the configuration process and also get the best performance, by applying best practices for each use case.
- How to add Prefetching
  Prefetching positions target media content at the Edge in anticipation of requests by end users. This reduces the time to deliver that content.
- How to add Quick Retry
  Quick retry detects slow forward throughput while fetching a streaming media object and attempts a different forward connection path to try to avoid congestion.
- How to add Protocol Downgrade
  If you're incorporating Standard TLS or Akamai's shared certificate delivery security (HTTPS L1), you may want to apply HTTPS to the request from the client to our Edge servers, but "downgrade" the connection to HTTP-only between Akamai and your origin. We refer to this as "Protocol Downgrade."
- How to add Token Authentication
  Token Authentication ("Token Auth") is the process of generating tokens, associating them with an authenticated user session, and then validating the stream using these tokens to prevent unauthorized sharing of links to your content.
- How to add Token-based Access Revocation
  Token-based access revocation lets you generate a "revocation list" of specific Token Authentication tokens to block access requests that include them. This helps to prevent token sharing between end users.
- How to add ULL streaming
  Ultra low latency (ULL) streaming takes advantage of Akamai's chunked transfer encoding (CTE) feature as well as various Property Manager behaviors to reduce latency and decrease overall transfer time of live streams.
- How to add Watermarking
  When a valid user requests content, watermarking distributes segments of content based on a pattern that’s unique to that user. If your content is pirated or redistributed, you can analyze the content and extract the user’s watermarking pattern to identify the user that originally leaked the content.
- How to add Use Case-based Edge Mapping
  Use Case-based Edge Mapping (UCEM) lets you apply a specific use case to an edge hostname to aid in delivering your content. With AMD, you can select a use case to best deliver either live or on demand format media.
Service Level Agreement for AMD
Notice

The Breadcrumbs response

The Breadcrumbs response header that's sent to a player includes various sub-fields of data.


Sub-field key	Sub-field value	Additional info
b	<Request ID>	A unique identifier assigned to the request. (This helps Akamai support teams quickly pull the relevant log line associated with the request.)
a	<Component IP>	The IP address of the node/host currently processing the request. This can be an edge server or an origin. Note: If the node or host is not either of these two types, it's excluded.
c	<Component Letter>	This is a single letter identifier for the Akamai network component that was involved during that phase of the request. (Your Akamai representative can use this value to determine where in the request phase the breadcrumb was gathered.)
n	<Component Geo>	Geographic details associated with the node/host currently processing the request.
o	<Component ASN>	The autonomous system number associated with the current node/host.

Example 1: When served from within Akamai

In this example, the request flow is Edge to Peer, so the Breadcrumbs format would be: [<component-ip>,<request-id>,<component-letter>,<component-geo>,<component-asn>],[<component-letter>,<component-geo>,<component-asn>]:


[a=12.34.567.89,b=12345678,c=g,n=US_CA_SANJOSE,o=20940],`[c=p,n=US_CA_SANJOSE,o=55155]`

Example 2: When served from an origin

In this example, the request flow is Edge to Cache to Origin, so the Breadcrumbs format would be: [<component-ip>,<request-id>,<component-letter>,<component-geo>,<component-asn>,[<component-letter>,<component-geo>,<component-asn>],[<component-ip>,<component-letter>]:


[a=12.34.567.89,b=12345678,c=g,n=US_CA_SANJOSE,o=20940],`[c=c,n=US_CA_SANJOSE,o=55155]`,[a=987.654.321.09,c=o]