Use case 3: HTTPS using a cloud partner-owned DNS name: wildcard certificate
Some subcustomers may want to serve content securely using one of your Cloud Partner-managed DNS namespaces.
Value | Example |
---|---|
Partner Domain |
|
End-Client-facing Domain CNAME |
|
Example End-Client-facing Domains |
|
Complete End-Client CNAME Chain |
|
In this example, let's assume that you operate one or more Cloud Partner infrastructure domains where each subcustomer is given a unique prefix, for example:
{sub-customer-prefix}.secure.cloudplatform.net
To configure secure delivery, we deploy a separate certificate, in which the
Common Name (CN) is a wildcard DNS name *.secure.cloudplatform.net
,
and the Akamai Secure Edge Hostname CNAME, secure.cloudplatform.net.edgekey.net
is provisioned to ensure that the
correct certificate is returned to the End-Client.
The Akamai server requires a separate DNS hostname to use
as origin. The origin-
prefix method works, as well as the practice of creating an origin
behavior for each subcustomer as shown in the examples for Use case 1: HTTP-only, using a partner-owned DNS name.