--- title: AWS IoT Core slug: litmusedge/product-features/integration/integration-connectors/aws/aws-iot-core description: Review parameters for the AWS IoT Core connector. docTags: createdAt: 2026-09-28T20:44:42.292Z --- The AWS IoT Core connector enables Litmus Edge (LE) to connect with AWS IoT Core over SSL. ## Supported communication - Outbound (Publish data from Edge to MQTT Broker) - Yes - Inbound (Subscribe data from MQTT Broker to Edge) - Yes ## Configurations | **Field** | **Details** | **Required** | | ---------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | | Name | Connector instance name. | Yes | | Hostname | DNS name of MQTT host. | Yes | | Port | Port of MQTT host. | No | | Certificate | Client certificate for mutual TLS authentication with the MQTT broker. Paste the PEM-encoded certificate here. | Yes | | Private key | Private key corresponding to the client certificate. Must match the **Certificate** field above. | Yes | | CA Certificate | Amazon Root CA certificate used to verify the broker. | No | | Client ID | Client ID is required by MQTT server. | No | | QoS | Quality of Service delivery guarantee: `0` = at most once (fire-and-forget), `1` = at least once. AWS IoT Core does not support QoS `2`. | No | | Parallel Publish Count | Number of messages published in parallel. Higher values increase throughput and resource usage. | Yes | | Integration Topic | AWS IoT Core topic to publish messages to. Follows MQTT topic conventions. | Yes | | LWT topic | MQTT topic the broker publishes the Last Will message to if this client disconnects unexpectedly. | No | | LWT payload | Message content published to the LWT topic on unexpected disconnection. Typically a status or alert string. | No | | LWT payload type | Encoding of the LWT payload: `string` for plain text, `base64` for binary data. | No | | LWT QoS | QoS level for the Last Will message: `0` = at most once, `1` = at least once | No | | LWT retained | When enabled, the broker retains the Last Will message and immediately delivers it to any new subscriber on that topic. | No | | Throttling limit | Set a limit on the number of outbound messages per second. If sending data to a server that has restrictions on the rate of incoming messages, this ensures that no messages are lost. | No | ## Persistent storage configurations | **Field** | **Details** | **Required** | | ----------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | | Persistent storage | If enabled, messages in the outbound queue are stored on disk. If there are interruptions in connection or power loss, messages are retained and eventually sent when the connection is restored. | No | | Persistent storage size limit | Set the size limit for storing persisted data in GB. | No | | Queue Mode | Select the sequence of data transfer: `FIFO` or `LIFO`. Selecting `FIFO` (First In First Out) sends the earliest message first. Selecting `LIFO` (Last In First Out) sends the latest message first. | No | ## Related topics - [Add a Connector](docId:4YVfCEP7GYScJHMKYFCuM) - [Manage Connectors](docId\:tQoP7QtquSQqDq9yhbJ34)