Are you using Standard TLS?

If you're looking for secure delivery, but you're not transferring personally identifiable information (PII), Standard TLS should work for you.

Note: Standard TLS is secure (HTTPS), but it is not PCI or FedRAMP compliant.

You need to create a property file ("property") using the Property Manager Editor in Control Center. This property serves multiple purposes, including the following:

  • You set up a "Property hostname to Edge hostname association" and associate your end-user-facing hostname with the Akamai Edge hostname. Requests to your property hostname are resolved to the Edge hostname, where an Edge server reads and applies what's set in the property file. In this association, you include vanity hostnames you've defined in the Standard TLS certificate to secure this connection.
  • You define the specific rules of match criteria and behaviors that determine how requests for content should be handled. Specifically for HTTPS connections, you need to properly configure the Origin Server behavior. You can do this using the "Default Rule," which applies to all requests. (This is recommended.)

Before you begin

You need a Standard TLS certificate. If you have the default certificate (limited availability) functionality added to your contract, you can create this certificate while setting up your property in Property Manager. Otherwise, you'll need to create one manually, using the CPS in Control Center before you can continue.

How do I set up the property for Standard TLS?

When setting up the property file for your selected product, you need to: