The tutorial explains how to create a service step-by-step.

The following steps will guide you through the process of creating a service:

In the first step, we need to navigate to the Edge CNAMEs page which is under the Settings page within the project's dashboard. You can visit the page by following the below path:

Dashboard -> Project -> Settings -> Edge CNAMEs

The following screenshots will help you better understand:

You need to open the project's dashboard from the main dashboard:

To reach the Edge CNAME page, expand the settings menu by clicking on the dropdown menu, as shown below:

To navigate to the Edge CNAMEs page, please click on the CNAMEs routing link, as the screenshot below:

Finally, you have reached the Edge CNAMEs page. In the screenshot below, you can see the inner page for the Edge CNAMEs page.

There are two platforms in our Delivery network, one for the delivery of the application, with the dynamic requests it requires, referred to as the Application Delivery Network (ADN), and one for the delivery of static assets, such as Javascript, Images, Stylesheets, etc. It is called a Content Delivery Network (CDN).

As a best practice, the ADN will deliver custom domains related to a whole site, such as:

In addition, CDNs deliver static content as best practices, enabling paralyzed downloads to gain better performance, typically looking like this:

The corresponding sectional card can be used to add a custom domain to the project by clicking 'Add New CNAME'.

Below is a screenshot to help you understand:

Please click the 'Add New CNAME' action button once you have recognized the platform to which you wish to add the custom domain.

The screen below shows how to add a CNAME to ADN.

In the requested field, enter the custom domain name and click 'Add'.

When you click 'Add', the new custom domain will be added to the platform. On the newly added row, you can see the Edge CNAME which must be mapped into your DNS records in order to redirect traffic to the custom domains.

Please note that the CNAME may take up to 1 hour to propagate across all PoPs and into the global edge!

Before redirecting traffic for production, you can always ping the Edge CNAME that needs to be mapped into the DNS records to see what IP address returns from the edge. Once you have the IP address, you can update your local host file for testing purposes.

Please find below instructions on how you can update your local hosts' files based on your operating system (Mac, Windows, Linux).

In a production environment, after completing Step 2 and adding the custom domain, you will need to enable HTTP(s) traffic for the newly added domains, which means including them in the SSL Certificate file and validating them.

For information on how to enable HTTPS traffic, please see the following article.

How to enable HTTP Traffic?

Once you finish, you can change the mapping of the additional domains into your DNS records and route the traffic through the delivery platform once you've validated that everything is working as expected.

Please note that you need to have created at least one service before you can follow the product tour.

Product tour: Add custom domain