eCDN Automatic Certificates
Embedded CDN (eCDN) automated certificates allows you to serve storefront traffic over HTTPS without the hassle of managing certificates.
This guide covers how to enable it on new and existing hostnames as well as legacy eCDN zones.
- Familiarize yourself with Authorization for Admin APIs
- You must have an Account Manager API Client with the scope
- You must have an existing proxy zone associated with the hostname you'd like to use.
- You must have an proxy zone. Automatic certificates are not supported by legacy zones. If you have a legacy zone, first migrate to a proxy zone.
- You must know the zone ID of the proxy zone to be used with automatic certificates. To get this info, use getZonesInfo.
This call replaces the existing custom certificate with an automated certificate without downtime.
Let's review the data provided in the request body.
The value of
hostname is the domain you'd like to use with the automated certificate.
certificateType must be set to
certificateAuthority controls which certificate authority is used to issue the certificate. The value must be either
Automatic certificates are not available for legacy zones.
A zone is a legacy zone if it does not end in
For more information on proxy and legacy zones, review this article.
To use automatic certificates, you must first migrate to proxy zones.
To migrate to a proxy zone:
- Create the storefront zones with createStorefrontZone.
- Copy required settings from your legacy zones to the proxy zones.
- Request an automatic certificate with addCertificateForZone.
- Perform a DNS cutover by updating your storefront's DNS records.
First, create your storefront zone:
You must create the storefront zone for both your
dev organization IDs to continue to manage your zones in Business Manager.
Third, request an automatic certificate with addCertificateForZone:
Finally, perform a DNS cutover by updating your storefront's DNS records. Get the DNS CNAME record value from getZonesInfo's
You can update an automatic certificate to a custom certificate using updateCertificate.
For HTTP validation to complete, eCDN must serve a validation value for a URI matching this pattern:
This check is completed over HTTP, not HTTPS. Confirm the URI is available over HTTP.
If you use certificate pinning, using automatic certificates is not possible as the certificate may be updated at any time.
There are two choices of validation for automated certificates: HTTP and DNS.
HTTP validation is used by default is the right choice in most cases.
Where a short issue delay is not acceptable, use DNS validation by providing the
certificateValidation request property with a value of
customHostnameVerificationTXTValue response properties to create your validation DNS TXT record.
You can change a certificate's validation type using updateCertificate.
- Automated certificates are only available for proxy zones.
- You can request up to five automated certificates per realm.
- Automated certificates are only available from Let's Encrypt and Google certificate authorities. To use a different certificate authority or a certificate with extended validation, use custom certificates.