Home
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.
Client Characteristics and AMD
This behavior offers options you can use to optimize delivery to requesting Clients.

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.
- Best practices and use case-based provisioning
  Every AMD property automatically includes a set of “best practices” behaviors in the Default Rule that have been optimized for best performance. You can also apply "use case-based" provisioning to further optimize a configuration based on your specific use case.
- Origin Server and AMD
  An origin server is the physical location from which content is retrieved. It is required in all configurations that retrieve content from an origin.
- Content Provider Code and AMD
  Content Provider (CP) codes are numeric IDs assigned to client requests in your configuration. These codes are used to identify your content for billing, logging, reporting, and cache purging. This is a required behavior.
- Segmented Media Delivery Mode and AMD
  Use this to set the delivery mode for your content to tune the configuration for that specific mode: On Demand (Default) vs. Live.
- Origin Characteristics and AMD
  This behavior lets you set characteristics for your origin server to optimize access to it.
- Content Characteristics and AMD
  This behavior lets you define specific information about your content to optimize its delivery.
- Client Characteristics and AMD
  This behavior offers options you can use to optimize delivery to requesting Clients.
- Cache Key Query Parameters and AMD
  This behavior controls whether the query string (or portions of it) are used to differentiate objects in cache.
- Tiered Distribution and AMD
  Tiered distribution is automatically added as a best practice. It lets AMD retrieve your cached content from another mid tier of servers closer to your origin server, rather than directly from your origin server.
- Recommended behaviors in the Default Rule
  We automatically add various recommended behaviors to your configuration within the Default Rule, which applies to all requests. They are optional, but recommended.
- Optional behaviors in the Default Rule
  You can add more behaviors using the Add Behavior button.
- The Default CORS Policy Rule
  This is a separate Rule that is added by default for your AMD configuration. It includes multiple instances of the Modify Outgoing Response Header Behavior, predefined with recommended values. (They are applied as "recommended behaviors.")
- You can add optional rules
  You can add rules via the Add Rule button to include match criteria and behaviors outside of what's included automatically in the Default Rule for your AMD property configuration.
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.
Service Level Agreement for AMD
Notice

Client Characteristics and AMD

This behavior offers options you can use to optimize delivery to requesting Clients.

Client Location

Select a location that is geographically closest to the clients accessing content through this property configuration, to optimize the delivery. This is one aspect of what we consider optimization via "use case-based" provisioning.

Note: If you're unsure of your client's locations, leave this set to Unknown. Selection of an inappropriate geographic region could negatively affect delivery.

Client Characteristics and Mixed Mode Configuration

This is a "use case-based" behavior that's automatically included in the Default Rule and used to optimize delivery. You need to apply settings for this behavior in the Default Rule. However, with Mixed Mode Configuration for AMD (MMC), you can also include it in another rule and apply different match criteria to have separate requests use different client characteristics optimizations. For more details, see How to use Mixed Mode with AMD.