A property configuration manages how ​Akamai​ edge servers process requests, responses, and objects served over the ​Akamai​ platform. A property indicates which property configuration file and product to use when processing incoming requests. It also defines the types of service, for example, how topics can be accessed.

Configure the IoT Edge Connect property

You need to configure a property to bind a property to hostnames.

1. Go to ☰ > CDN > Properties, and then click New Property.

2. Select IoT Edge Connect form the Product list.

3. In the Property Name field, enter a name for your property and click Create Property.

4. In Property Version Information, make sure that Security Options is set to Standard TLS ready.

5. In Property Hostnames, click Add.

6. In the Add Hostnames wizard:

   1. Enter your property hostname or an appropriate portion of that hostname and click Next.

      This should be the hostname of the broker.

   2. If needed, change the protocol to IPv4 and click Next.

   3. On the Certificates Matching All Property Hostnames tab, select an SSL certificate, click to modify an existing certificate, or click to create a new SSL certificate. When done, click Next.

      You should see the certificate that you pre-created in Create a TLS certificate as the candidate.

      This certificate is presented by your namespace to authenticate itself to the connecting user. It's not the same as a Mutual Authentication certificate.

   4. Click the pen icon and select the edge hostname that your account representative provided. Then click Submit.

7. In the Content Provider Code behavior, select your CP code from Content Provider Code.

Configure the IoT Edge Connect behavior

Configure this behavior to enable the IoT Edge Connect product, connect previously reserved namespaces, and decide which protocols users can use to publish and receive messages. Each jurisdiction requires a separate configuration.

1. Make sure that the Enable switch is set to On.

2. Select the namespace-jurisdiction pair from the Namespace dropdown.

3. Enable at least one communication protocol:

   • MQTT
     Uses a secure connection using port 8883.

   • MQTT over WebSocket
     Uses a secure connection using port 443.

   • HTTP
     Uses a secure connection using port 443.