AMQP SSL Integration Guide

review the following guide for setting up an integration between litmus edge and an amqp broker with ssl authentication before you begin you will need the following access to an amqp broker that uses ssl authentication the ca certificate and other required authentication parameters needed to access the broker refer to the following links to learn more downloading and installing rabbitmq https //www rabbitmq com/download html enabling tls support in rabbitmq https //www rabbitmq com/ssl html#enabling tls openssl downloads https //www openssl org/source/ step 1 add a device step 2 add tags step 3 add the amqp ssl connector follow the steps to add a connector docid\ ytswgweu6h6oeunhj5hw3 and select the amqp ssl provider note for configuring exchange options, see amqp ssl docid\ ixye3z vgvaiep7c ezf0 and refer to the exchange options section to learn more enter the details for the connector name enter a name for the connector hostname enter the ip address for the amqp broker port enter the port number for the amqp broker the default value is 5671 virtual host (optional) enter the virtual host path, which specifies the namespace for permissions, exchanges, queues, and bindings on the server username (optional) enter the username for authentication with the amqp broker the default value is guest password (optional) enter the password for authentication with the amqp broker the default value is guest exchange (optional) enter the northbound (third party) topic to publish to through the connector exchangetype select the exchange type (direct, fanout, topic, x custom) exchange durable select the checkbox to allow the exchange to survive restarts exchange auto delete select the checkbox to make the server no longer remain declared when there are no remaining bindings exchange internal select the checkbox to enable the internal flag exchange no wait select the checkbox to instruct the exchange to not wait for a response routing key the amqp routing key that the exchange might use to determine how to route messages to the queue iso8601 timestamp select this checkbox to convert message timestamps to the iso8601 format before sending ca certificate paste or upload the ca certificate associated with the broker certificate (optional) paste or upload the ssl certificate private key (optional) enter or paste the ssl private key throttling limit (optional) the maximum number of messages per second to be processed the default value is zero, which means that there is no limit persistent storage when enabled, this will cause messages to undergo a store and forward procedure messages will be stored within litmus edge when cloud providers are online queue mode select the queue mode as lifo (last in first out) or fifo (first in first out) selecting lifo means that the last data entry is processed first, and selecting fifo means the first data entry is processed first step 4 enable the connector after adding the connector, click the toggle in the connector tile to enable it if you see a failed status, you can review the connector logs docid\ beqq0sszwsv9v9rif3rhk and relevant error messages step 5 create topics for connector you will now need to create outbound topics for the connector from the tags created in step 2 after adding all required topics, navigate to the integration overview page and ensure the connector is not disabled and still shows a connected status step 6 enable topics step 7 verify successful connection access the amqp broker and ensure that data is being sent from litmus edge to the broker