To securely serve your content over HTTPS, you need an edge certificate that is verified between the client and the edge server. You use Akamai Control Center to create or access an edge certificate for use. This way, the private key remains secure within the Akamai platform, and is never transmitted or stored outside where it could be intercepted.
You may decide to use a default certificate that is automatically created behind the scenes while you add a new secure hostname to the Akamai platform. You just specify the deployment network and security level, either Standard TLS or Enhanced TLS. This simplified process doesn't involve any prerequisites.
See Add a hostname with a default certificate (LA) for complete details on the use of this certificate method.
If you'd rather create a custom, Akamai-managed certificate manually, use the Certificate provisioning System (CPS) in Akamai Control Center. All certificates created in CPS are signed by a Certificate Authority (CA) that is known to be trusted by every major browser or operating system. While creating new certificates in CPS, just like with default certificates, you specify the deployment network and security level, either Standard TLS or Enhanced TLS.
In CPS you can also provision certificates issued by a third-party Certificate Authority (CA). Work with your Account Representative to complete this process.
Create custom certs beforehand
You must create custom certificates before you start editing the hostname settings in your property. This applies to the Modify Existing Certificates option, too.
There's also a third option for secure delivery, a shared certificate. You don't need to provision and manage this certificate as Akamai maintains it for your use. You simply select this option while configuring edge hostnames for your property. Shared certificates use the applicable edge hostname suffixes, such as
See Use an Akamai shared certificate for complete details on the use of this certificate method.
Updated 10 months ago