The adaptive-media-delivery Developer Hub

Welcome to the adaptive-media-delivery developer hub. You'll find comprehensive guides and documentation to help you start working with adaptive-media-delivery as quickly as possible, as well as support if you get stuck. Let's jump right in!

Get Started    

Get your unique information

You need to review your environment and gather some specific pieces of information before creating your Adaptive Media Delivery (AMD) property.

Get your account information

Within five days of your service contract submission, you should receive your account information. You need this information to activate your configuration for use with Adaptive Media Delivery. If you haven't received it (or you don't have it), contact your ​Akamai​ account representative.

You should receive the following information:

  • Your account name and ID. This is the unique name for your account and its unique identifier. This is not your login information.

  • Content provider (CP) codes. These are used for reporting and billing. You'll use this value when setting up your AMD property.

  • An administrator login. This is used to access the following:

    • ​Akamai Control Center​. This is ​Akamai​'s user interface portal.

    • Content storage servers. This applies if you've included NetStorage in your service package, for use as the origin to store your content for delivery.

Additional items you'll need

In addition to the information ​Akamai​ gives you, you need these items, some of which are gathered during the processes discussed in this documentation.

  • Your Domain. This is the hostname that end users are using to access your site or application. This is used to create a property hostname.

  • The origin server hostname. This applies if you're housing deliverable content in a custom origin. (NetStorage is not being used.) This is used for Edge servers to fetch target content for a request.

  • Your ​Akamai​ edge server hostname(s). During this process, you need to associate a property hostname with ​Akamai​ edge servers to resolve requests from end users, so that settings applied in your Adaptive Media Delivery property are applied to deliver your content. The end result of this association is referred to as an edge server hostname. You need to generate a CNAME for your website or application to resolve to this edge server hostname.

Multiple origin servers

If you're using multiple origin servers, your overall configuration might be impacted. You should contact your account representative before creating a property for Adaptive Media Delivery. Explain the use and purpose of the various origin servers. For example, assume origin server center "A" is active, and origin server center "P" is passive, to be used only when required by heavy traffic or failover. If this is the case, you can set up multiple rules in your Adaptive Media Delivery property to accommodate them, using different match criteria for requests. See Mixed Mode & AMD for details on this process. However, you can also reach out to your account representative for additional tips, or for assistance in setting this up.

There are some other ways that multiple origin servers can affect your configuration:

  • When using SureRoute, ​Akamai Technologies, Inc.​ edge servers race test objects to determine the optimal edge-to-origin routes. By default, the assumption is that only one origin server location needs to be evaluated.

  • When configuring cacheable objects, there are ways to avoid caching multiple instances of the same object that may be obtained from different origin servers.

Updated 22 days ago

Get your unique information

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.