Go live with AMD

Once all of the configuration steps and testing are complete, you can go live to begin delivering your content.

1 - Activate on production

The first step in the process is to push your AMD property to the production ("live") network to distribute your content to end users.


This process assumes that the target AMD property has already been activated on the Staging network, for use in testing. You must push a property to Staging before you can push it to Production.

  1. Select the appropriate Control Center Account. Use the top-right pull-down in the header to select the account.

  2. Access Property Manager configurations associated with the selected Control Center Account. Go to > CDN > Properties.

  3. Filter the results of the Property Groups table by inputting the desired AMD property name in the Filter by Property or Hostname field.

  4. Click the Property Name.

  5. In the Manage Versions and Activations content panel, locate the Version # of the property currently in Staging (the one created for Testing) and click it.

  6. Select the Activate tab.

  7. Click Activate v<#> on Production.

  1. Any warnings carried over from the configuration will be displayed as Validation Messages. You can click Cancel and edit the property to acknowledge them.


If you've created a new version of the property, an additional warning message is displayed here noting that this "new version:" has not been activated on Staging for testing. Click this message's checkbox to acknowledge and dismiss this warning.

  1. Optionally, add descriptive Notes and use the Notify via email field to define email address(es) that will receive notifications in the event of a property file changes. Separate multiple entries with a comma—", ")

  2. Click Activate v<#> on Production.

  3. Monitor the Activate tab to track progress. You can also click View Details to review settings and information regarding the property.

2 - Point to your configuration

This process can vary, based on the type of hostname you're using in your AMD property.

Custom certificate hostname

You need to change the existing DNS record of your hostname to be a CNAME record that points to the edge hostnameYou need to change the existing DNS record for your content to be a CNAME record that points to the edge hostname. Once you modify the DNS record, it's typically only a matter of minutes until your content is served via the ​Akamai​ edge network.

Here are some DNS record examples:

DNS RecordExampleNotes

A generic DNS record for your domain

www.example.com. IN A

Where is the IP address of your origin server

Your domain pointing to ​the Standard TLS network

www.example.com. IN CNAME www.example.com.edgesuite.net


Your domain pointing to ​the Enhanced TLS network

www.example.com. IN CNAME www.example.com.edgekey.net


Below are some examples of the DNS records required to deliver objects from a content delivery network. You need to replace www.example.com with the actual domain used to access your content.

Standard TLS-secured hostname example

  • Origin-server Hostname. origin-example.com IN A {IP address of the origin server}
  • Edge Hostname. www.example.com.edgesuite.net
  • Production Hostname. www.example.com. IN CNAME www.example.com.edgesuite.net

Enhanced TLS-secured hostname example

  • Origin-server Hostname. origin-example.com IN A {IP address of the origin server}
  • Edge Hostname. www.example.com.edgekey.net
  • Production Hostname. www.example.com. IN CNAME www.example.com.edgekey.net

How long does the DNS change take?

This depends on the time to live (TTL) set on the existing DNS record for the hostname in question. This is commonly set to one day, which means it would take up to 24 hours before your end users are directed to the Edge network. To shorten this, you could reduce your DNS TTL in advance of the change, and increase it to the normal TTL after the change.

You can switch your application to the edge network at any time after completing the activation steps and testing. No additional activation or monitoring is required.

Shared certificate hostname

You use the shared certificate hostname itself in the URLs of your content, in place of your origin server hostname. You could set up your player to make requests starting with the Shared certificate hostname URL and add any path elements as they exist on your origin server. For example, assume you have your player accesses a video clip on your origin server:


You'd update your player to access it using the shared certificate edge hostname, instead:


Now, when the player requests your content, the request is sent to the ​Akamai​ edge network where your AMD property is read. What you have configured in it including what's set in the Origin Server behavior is used to access and deliver your content.


If you notice a problem after switching your content to the edge network:

  1. Roll back any changes:

    • Custom cert edge hostname. Make a DNS change to point back to your origin servers.
    • Shared certificate hostname. Revert your player to request content directly from your origin server.
  2. Report the problem to ​Akamai​.

This helps you and ​Akamai​ identify the problem in a controlled environment without affecting live end users.