Add hostnames with custom certificates to the bucket
Hostname buckets are BETA
This feature is still in BETA. If you're interested and would like to use hostname buckets now, contact your Akamai account team.
Some products such as Adaptive Media Delivery, IoT Edge Connect Message Store, IoT Edge Connect Message Store, and Akamai Cloud Embed are not supported with hostname buckets yet.
Adding property hostnames to a bucket automatically activates them on the network you select in the Property Hostnames Bucket panel. Hostname activations are independent from property activations, however any modifications to hostnames will apply to all versions of your property.
Perform these steps to set up property hostnames using a custom certificate you created with Akamai's Certificate Provisioning System (CPS) or the one you set up with a third-party service.
Before you begin
Make sure you complete the initial setup.
You need to prepare your edge certificate before you can start this process.
- Go to ☰ > CDN > Properties.
- On the Property Groups page, click a property with the bucket hostname you want to add hostnames to.
- On the Property Details page, in the Property Hostnames Bucket panel, click +Hostnames and select the network.
As best practice, first add hostnames to staging. Once you verify the hostnames work as expected, add them to production.
- In the Add Hostname(s) field, enter the hostnames you want to use. The names don't need to contain
https://, just the domain.
- If you have a certificate in CPS, enter the domain that matches what you've set up in that certificate as either the Common Name (CN) or a SAN (Subject Alternate Name).
- If you have a third-party custom certificate, enter the exact domain associated with the certificate you've provided to your Akamai account team.
You can add multiple hostnames by pasting them into the field. Each value needs to be separated by a space or comma, or contained on separate lines. Duplicate names are skipped.
You can specify up to 1000 hostnames at a time.
- Click Next.
- Switch off the Automatically request certificates toggle.
- Select the custom certificate you previously created and associated with your domain name. You can create custom certificates in CPS at this point, but you'll have to wait for the certificate to provision (3-6 hours, depending on the level of security). To check whether the new certificate is available for selection, click Refresh to update certificates.
- Click Next.
- Select the appropriate IP version, based on what your application or site can support.
- Select an existing edge hostname. Use a single Edge hostname for all property hostnames in the bucket. For Standard TLS certificates, use an edge hostname with the
edgesuite.netsuffix. For Standard TLS certificates, use an edge hostname with the
As best practice, use a single edge hostname, CP code and property for all the hostnames in the bucket that share the same security level, either Standard or Enhanced TLS.
- Click Submit. The activation for the specified hostnames starts automatically on the network you selected.
- Read the instructions in the Success message, and click Close.
- To check the status of the property hostname activations, on the Property Details page, click the Activation History tab. In the Activation Types, select Hostnames.
Test the activated hostnames.
Instruct your customer to redirect traffic to Akamai by replacing the existing CNAME record with a new one, setting its value to the Akamai edge hostname.
You can pass the Akamai edge hostnames directly to your customers, or alternatively create intermediary CNAMEs on your own domain and pass those to your customers.
Now, requests to the domains you added will resolve to the Akamai edge network. Your property will be read and the content will be delivered based on how you've set up your property.
If you're using Standard TLS Domain Validated (DV) certificate, you can automate the certificate renewal by adding the Auto Domain Validation to your property's rule. Make sure you selected the appropriate renewal settings in the Certificate Provisioning System. The renewal process starts automatically 16 days before the certificate's 90 lifecycle ends.
Updated about 2 months ago