The tutorial explains how to enable HTTPS traffic step-by-step.

The following steps will guide you through the process of enabling HTTPS traffic:

First-time SSL Certificate configuration may require you to know the following:

There are different SSL options available depending on your plan. For Standard, Business, and Enterprise plans, a dedicated SSL is included in the plan. Shared SSLs can be issued with no additional charge when using the Basic plan, but if you require dedicated SSLs, additional charges will apply to the subscription.

The process for adding a new SSL certificate or updating a current one is almost the same. However, there are differences in the provision between the dedicated SSL Certificates and the shared SSL Certificates, so differences are in the validation process. DNS TXT records are used for verification of dedicated SSL, while CNAME records are used for verification of shared SSL. In Shared SSL, if you have validated the top-level domain, such as example.com, then all subdomains that follow are automatically validated as well.

By adding a dedicated SSL, by default, we provide you with anycast dedicated IP addresses across all regions and our dedicated SSLs are commercial and highly secure enterprise-grade certificates.

At this stage we support Domain Validation (DVs) within the platform's provisioning tool, however, you can always contact our support for getting Organization Validation (OV) SSLs or Extended Validation (EV) SSLs. In the next releases, we will enable automation for OV and EV SSls within the dashboard.

The process for adding a new SSL certificate or updating a current one with new custom domains is almost the same.

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 SSL

The following screenshots will help you better understand:

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

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

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

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

As soon as you have reached the Edge SSL page, we need to begin the activation process, so let's start by issuing a dedicated SSL certificate for the purpose of this tutorial.

First, we need to open and click on the 'Enable SSL' action button in the Custom SSL section.

The next step is to add the custom domains to the SSL certificate. As shown in the screenshot below, click on the 'Add new domains' action button:

Fill in the domain name within the text box of the opened window and click the 'Add' action button.

Multiple domain names can be added. Normally, you will need to add all custom domain names for the ADN platform, as well as for the CDN platform. The screenshot below shows an example:

To initiate the process, click on the 'Save' button after adding the custom domains. The screenshot below shows an example:

Upon clicking the 'Save' button, the window will close and you will see the screenshot below:

We are waiting for the DNS token so that we can validate the ownership of the domain name, which usually takes up to 5 minutes. You can track the process by clicking the 'Enable SSL' button. The screenshot below shows an example:

When the process reaches the third step, the show validation token button will be activated and accessible, and the token will be available. The screenshot below shows an example:

By clicking the Copy button, you can copy the Validation Token automatically to your keyboard, or you can see the Validation code by clicking the Show Validation Token action button, so you can manually copy it. The screenshot below shows an example:

After copying the validation code, you can now navigate to your domain management solution such as GoDaddy, Edgeport, DnsMadeEasy, etc. This tutorial will focus on Edgeport's routing.

For the Domain Validation (DV) SSL, the SSL is been validated with a TXT DNS record, on the hostname (@) or to the specific subdomain.

Example of a TXT record:

See how to add a TXT record on specific providers:

After adding the TXT record, the SSL will be auto-validated, but it is also possible to validate manually by clicking Validate. The screenshot below shows an example:

Validating the SSL is an automated process. Once it has been validated, it must be activated and propagated to the Edge. The dashboard's service onboarding process includes information about propagation.

First, let's see that SSL has been issued and the deployment has begun. The screenshot below demonstrates how this works:

In the dashboard, we can see the SSL deployment as soon as it has been completed. Below you can see screenshots that show the progress so far and the status of the SSL deployment.

Please note that as our service is an enterprise-grade network, there is no centralized proxy service like the competition, but isolated PoPs that handle each request individually, and as new IP addresses were created during the process, it could take up to six hours for the SSL to propagate across all regions and PoPs once the process has been completed and validated.

Decentralized delivery provides enhanced security metrics per point of presence, advanced scalability capabilities to handle more requests per second, and improved availability since there is no single point of failure.