Instant Config Hostname is a tool in Property Manager that you can use to quickly create an edge hostname for HTTP (non-secure) delivery.

📘

While HTTP (non-secure delivery) is still available in Property Manager, it's not recommended. HTTPS delivery is now the industry standard.

How Edge IP Binding works with an instant config hostname

You define a prefix value and enable Edge IP Binding in a property hostname. The prefix is automatically combined with a fixed domain value, mdc.akamaized.net to form your edge hostname. Once your property is activated, you have an edge hostname and several Edge IP Binding IP addresses that you use as follows:

• Use the edge hostname directly in access URLs Provide them to your end users to directly access your content via HTTP.

• Provide the Edge IP Binding IP addresses to your third party. They use them for zero-rated billing and Access Control List (ACL) purposes. HTTP requests to these IP addresses access your property in the same way the edge hostname does.

Understand the connections

There are two connections involved in a request using the ​Akamai​ platform:

• The client to ​Akamai​ edge server. This is the initial HTTP connection between the end user and the edge server to get your property. The property determines how to deliver the requested content. This is the connection you're configuring here, in the property hostname to support Edge IP Binding.

• The ​Akamai​ edge server to origin. This is the connection between the edge server and your designated origin, to get your content and deliver it to the end user. To configure this connection, you set options in the Origin Server behavior in your property. More on this later.

Set up Edge IP Binding with an instant config hostname

Follow these steps to add Edge IP Binding in an instant config hostname.

1. Ensure that Standard TLS ready is selected in Security Options. (You're not applying security, but this needs to be selected.)

2. In the Property Hostnames content panel, click the dropdown menu next to the Add button and select Add Instant Config Hostname.

3. Set the following values:

   • Edge Hostname. Enter your desired prefix value. Use alphanumeric or hyphen characters, with a total length of 4-60 characters. You can't start this prefix with a hyphen.

   • IP version. Select the appropriate version, based on what your application or site can support.

   • Edge IP Binding. Enable this.

📘

If you're using Adaptive Media Delivery or Download Delivery, you'll also have access to the options, Segmented Media Mode or FOREGROUND, respectively. These are not supported for use with Edge IP Binding. Once you enable Edge IP Binding, this option will become grayed-out and unavailable.

Verify status and finish your property

The status of your new Edge IP Binding configuration is shown in the Property Hostnames panel:

• The Status icon is gray. Activation of your Edge IP Binding addresses is pending.

• The Status icon is green. Your addresses have been provisioned and are ready. You can use them after your property has been activated on ​Akamai​'s staging (testing) or production (live) networks.

📘

It can take from 30 - 40 minutes to generate your Edge IP Binding addresses.

Perform these steps to complete the process:

1. You can optionally add variables.

2. You need to define property configuration settings that include rules to match requests and the behaviors that should be applied. Available rules and behaviors vary, based on the product you're using:

   • Adaptive Media Delivery
   • Download Delivery
   • Object Delivery
   • Ion
   • API Acceleration

3. There are two connections in a request. The process here addressed the first connection between the end user and ​Akamai​ edge servers. You need to configure the second connection between an edge server and the origin server to get content. Set up this connection using the Origin Server behavior in a rule in your property.

4. Activate the property on the staging network where you can test it, and then activate it on production.

5. Optionally, you can create the following alerts:

   • DNS does not contain an authorized certificate authority.
   • Domain validation failed.
   • Certificate’s domain is blocked.
   • Expired default certificate.
   • Expired default certificate removal.