Requirements

This page lists ClearBlade IoT Core requirements and related information.

Regions and versions

Cloud regions

Only these cloud regions are available: us-central1, europe-west1, and asia-east1.

Transport layer security (TLS)

ClearBlade IoT Core requires TLS version 1.2 or higher. For more guidance on TLS, see the Minimum standards for TLS clients section in Disabling SSLv3 and RC4.

MQTT bridge

MQTT version 3.1.1 is required.

These features are not supported:

MQTT QoS 2
Arbitrary MQTT topics and subscriptions. For topic requirements, see connecting devices using MQTT
Last will and testament (LWT)
Retained messages
Persistent sessions

HTTP bridge

Secure communication (HTTPS) is required.

ClearBlade IoT Core supports HTTP 1.1 only (not 2.0).

Permitted characters and size requirements

Registries, device identifiers, and their associated fields are limited to certain characters. These fields are also limited in size (length or byte size).

This table lists the permitted characters and sizes for each resource:

Resource	Limitations
Registry IDs	Permitted characters: `[a-zA-Z][-a-zA-Z0-9._+~%]+` The first character must be a letter (`[a-zA-Z]`) Cannot start with "goog" Minimum length: 3 characters Maximum length: 255 characters
Device IDs	Must be unique within the parent device registry Permitted characters: `[a-zA-Z][-a-zA-Z0-9._+~%]+` The first character must be a letter (`[a-zA-Z]`) Cannot start with "goog" Minimum length: 3 characters Maximum length: 255 characters
Device metadata keys	Permitted characters: `[a-zA-Z][-a-zA-Z0-9._+~%]+` The first character must be a letter (`[a-zA-Z]`) Minimum length: 1 character Maximum length: 128 characters Maximum combined total size of all device metadata key-value pairs: 256 KB
Device metadata values	Minimum size: 0 KB Maximum size: 32 KB Maximum combined total size of all device metadata key-value pairs: 256 KB
Subfolders^*	Permitted characters: `[a-zA-Z][-a-zA-Z0-9._+~%]+` The first character must be a letter (`[a-zA-Z]`) Maximum size: 256 bytes

*Subfolders refer to the eventNotificationConfigs.subfolderMatches device registry field. It is used when matching MQTT or HTTP subfolders to a Cloud Pub/Sub topic.