Configure your property to serve objects non-securely over HTTP.

📘

Secure hypertext transfer protocol (HTTPS) has become the standard for access on the Internet. All processes covered here focus on the use of this security to deliver your content via the ​Akamai​ network. While non-secure HTTP is still supported, it's not recommended.

Before you begin

You'll need an origin server set up. This is where you store the resources—your website, application, media, etc.—that you want to deliver to requesting clients. Take a look at Prepare your origin server before you get going here.

Add a non-secure hostname

Some steps may slightly vary depending on the Property Manager release you're using, either General Availability (GA) or Limited Availability (LA). The procedures cover two variants of the custom hostnames setup.

General Availability

1. In the Property Manager Editor, in the Property Information content panel, ensure that Standard TLS ready is selected as the security option. (You won't be applying Standard TLS, but this security level setting is required here.)

2. In the Property Hostnames content panel, click Add.

3. In the Add Hostname(s) field, enter the property hostnames you want to use, and click Next.

4. Select the appropriate IP version, based on what your application or site can support, and click Next.

5. If applicable, specify the desired Mapping Solution. If none of the following applies to you, go to the next step.

   • Are you using Adaptive Media Delivery or Download Delivery? You can apply a specific Use Case. See What is Use Case-based Edge Mapping?

   • Do you have Edge IP Binding on your contract? You can enable it here. See What is Edge IP Binding?

   📘

   You can only select one Mapping Solution—you can enable Edge IP Binding, or select a Use Case, but not both.

6. Review the edge hostnames.

7. Do you want to use the auto-generated edge hostname? This is what Property Manager automatically sets for the association. If this suits your needs, click Submit.

8. Do you want to modify the edge hostname? If so, click the pencil icon .

   • Create. With this option selected, you can define a fully custom edge hostname, select a different domain, and change the IP version, if desired.

   • Select existing. Select this option if you want to associate your property hostname with an existing edge hostname.

   • Custom. Select this option to manually input a CNAME target to be used in the association. Contact your account representative for further details on the proper use of this field, and whether it applies to your environment configuration.

9. When you're happy with the selections here, click Update. Review what's set and click Submit.

10. Review information in the Success window and apply its instructions as required.

Next steps

1. Continue configuring your property to add variables (optional), your origin server, and set up Rules and behaviors for delivery.

2. Activate your property on the staging network so you can test your configuration.

3. When you're satisfied with testing, activate your property on production to go live with delivery.

4. Finally, you need to access your DNS (outside of ​Akamai​) and add CNAME records for all of your edge hostnames.

Now, requests to your domain will resolve to the ​Akamai​ edge network through your edge hostnames. Your property will be read and your content will be delivered based on how you've set up your property.

Limited Availability

1. In the Property Manager Editor, in the Property Hostnames panel, click Add.

2. In the Add Hostname(s) field, enter the hostnames you want to use:

   • You don't need to include http://. Just enter the domain.
   • You can add multiple hostnames. Each one needs to be separated by a space or comma, or contained on separate lines. Duplicate names are ignored.

3. Click Next.

4. Select the appropriate IP version, based on what your application or site can support, and click Next.

5. Switch Automatically request certificates to Off. If any custom certificates display in the Select Certificates list, you need to delete them from the Certificate Provisioning System (CPS) before you can continue.

6. Check I don't need a TLS certificate, and click Next. A table displays, containing the edge hostnames. Make note of all of the edge hostnames you added. You'll need them later.

7. Click Submit.

8. Read the instructions in the Success message, and click Close when you are done.

Next steps

1. Continue configuring your property to add variables (optional), your origin server, and set up Rules and behaviors for delivery.

2. Activate your property on the staging network so you can test your configuration.

3. When you're satisfied with testing, activate your property on production to go live with delivery.

4. Finally, you need to access your DNS (outside of ​Akamai​) and add CNAME records for all of your edge hostnames.

Now, requests to your domain will resolve to the ​Akamai​ edge network through your edge hostnames. Your property will be read and your content will be delivered based on how you've set up your property.

Add an Instant Config hostname

Instant Config Hostname is a tool in Property Manager that allows you to automatically create an edge hostname for HTTP delivery.

Once the property configuration is activated, a new edge hostname is created and points to ​Akamai​ edge servers. It uses a prefix you define, combined with a fixed domain value—.mdc.akamaized.net.

1. GA release only: In the Property Information content panel, ensure that Standard TLS ready is selected as the Security Option. (You won't be applying Standard TLS, but this security level setting is required here.)

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

3. Enter your desired prefix value in the Edge Hostname field. Only alphanumeric (a-z, A-Z, 0-9) and hyphen ("-") characters are supported, with a length 4-60 characters. It cannot begin or end with a hyphen.

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

   • IPv4 only: Support for IP addresses using version 4, only.

   • IPv4 + IPv6 (dual stack): Support for both address formats.

   📘

   If you select IPv4 + IPv6 (dual stack) as your IP version, your site or application must support IPv6 in HTTP request headers and delivered log lines.

5. If applicable, specify the desired Mapping Solution. If none of the following applies to you, go to the next step.

   • Are you using Adaptive Media Delivery or Download Delivery? You can apply a specific Use Case. See What is Use Case-based Edge Mapping?

   • Do you have Edge IP Binding on your contract? You can enable it here. See What is Edge IP Binding?

6. Click Save.

Next steps

1. Continue configuring your property to add variables (optional), your origin server, and set up Rules and behaviors for delivery.

2. Activate your property on the staging network so you can test your configuration.

3. When you're satisfied with testing, activate your property on production to go live with delivery.

4. Finally, you need to access your DNS (outside of ​Akamai​) and add CNAME records for all of your edge hostnames.

Now, requests to your domain will resolve to the ​Akamai​ edge network through your edge hostnames. Your property will be read and your content will be delivered based on how you've set up your property.