---
title: Amazon AWS IoT Core over SSL Integration Guide
slug: litmusedge/how-to-guides/integration-guides/amazon-aws-iot-core-over-ssl
description: Learn how to set up the AWS IoT Core over SSL connector. 
docTags: 
createdAt: 2022-11-28T18:23:32.000Z
---

Review the following guide to set up an integration between Litmus Edge and AWS IoT Core with SSL authentication. 

# Before You Begin

You must have an AWS account with the appropriate user privileges. 

# Set Up Integration in AWS

## Step 1: Onboard Device

**To onboard a device: **

1. Open the AWS IoT browser tab and click **Manage **>** Things**.
   The *Things *pane appears.
2. From the left pane, click **Onboard**.
   The *Connect to AWS IoT* pane appears.
   ::Image[]{src="https://api.archbee.com/api/optimize/SSUUxKZUk9bFTEPNn_6Zo/V3BO-G9gCkJgBquUU1wEG_aws-iot-onboard.png" size="80" width="1397" height="588" caption="Connect to AWS IoT pane" position="center" showCaption="true"}
3. From the Onboard a device box, click **Get Started**.
   The *Connect to AWS IoT* wizard appears.
   ::Image[]{src="https://api.archbee.com/api/optimize/SSUUxKZUk9bFTEPNn_6Zo/BHiU0IKv0X6aUQDOo0UdD_aws-iot-wizard.png" size="80" width="740" height="493" caption="Connect to AWS IoT wizard" position="center" showCaption="true"}
4. Click **Get Started**.
   The *How are you connecting to AWS IoT* screen appears.
   ::Image[]{src="https://api.archbee.com/api/optimize/SSUUxKZUk9bFTEPNn_6Zo/hsDisp19aOwYBl-wpuGtc_aws-iot-how.png" size="80" width="743" height="566" caption="How are you connecting to AWS IoT screen" position="center" showCaption="true"}
5. From the *Choose a platform*** **section, select **Linux/OSX**.
6. From the *Choose a AWS IoT Device SDK* section, select **Java**, and then click **Next**.
   The *Register a thing* screen appears.
   ::Image[]{src="https://api.archbee.com/api/optimize/SSUUxKZUk9bFTEPNn_6Zo/E-Fl8AkTeMQeWdkRi_4vG_aws-iot-register.png" size="80" width="741" height="335" caption="Register a thing screen" position="center" showCaption="true"}
7. In the **Name **field, enter **Thing1**, and then click **Next step**.
   The *Download a connection kit *screen appears.
   ::Image[]{src="https://api.archbee.com/api/optimize/SSUUxKZUk9bFTEPNn_6Zo/JcU-bFVza3ql5LxJWwnCD_aws-iot-download.png" size="80" width="743" height="581" caption="Download a connection kit screen" position="center" showCaption="true"}
8. Click **Linux/OSX**, view the downloaded .zip file at the bottom of the screen, and then click **Next step**.
   The *Configure and test your device *screen appears.
   ::Image[]{src="https://api.archbee.com/api/optimize/SSUUxKZUk9bFTEPNn_6Zo/Sjr9VXe3uXxpsrKksZ_RU_aws-iot-test-device.png" size="80" width="742" height="472" caption="Configure and test your device screen" position="center" showCaption="true"}
9. View the downloaded .zip file at the bottom of the screen, and then click **Done**.
   The *Connected successfully* screen appears.
   ::Image[]{src="https://api.archbee.com/api/optimize/SSUUxKZUk9bFTEPNn_6Zo/nGT4A0Jc2g1xP8YmtleOM_aws-iot-connected.png" size="80" width="740" height="523" caption="Connected successfully screen" position="center" showCaption="true"}
10. Click **Done**.
    The named *Thing1* appears in the Things pane.

## Step 2: Create Policy

**To create the policy: **

1. From the left pane in the AWS Things pane, click **Secure > Policies**.
2. Refresh the page. 
   The named *Thing1-Policy* appears.
   ::Image[]{src="https://api.archbee.com/api/optimize/SSUUxKZUk9bFTEPNn_6Zo/Sxu_BWI5z7d3niexH9xGb_aws-iot-thing-policy.png" size="80" width="1409" height="433" caption="Policy item" position="center" showCaption="true"}

## Step 3: Create and Download Certificate and Private Key

You will need to download the certificate and private key that you will use to configure the AWS connector in Step 8. 

**To create and download the certificate and private key: **

1. From the left pane, click **Certificates**.
   The certificate for the named Thing appears.
   ::Image[]{src="https://api.archbee.com/api/optimize/SSUUxKZUk9bFTEPNn_6Zo/csua6h_nIb2AtvPRf7XrW_aws-iot-thing-certificate.png" size="80" width="1410" height="490" caption="Certificate pane" position="center" showCaption="true"}
2. Click the **Actions **icon for the certificate, and select **Delete**.
   The *Confirmation *dialog box appears.
3. Click **Yes, continue with delete**.
4. Refresh the page.
   The *Certificates *wizard appears.
   ::Image[]{src="https://api.archbee.com/api/optimize/SSUUxKZUk9bFTEPNn_6Zo/0wDcTp89OT15aFLewKYbq_aws-iot-certificates.png" size="50" width="388" height="408" caption="Certificate wizard" position="center" showCaption="true"}
5. Click **Create a certificate**.
   The *Create a certificate* screen appears.
   ::Image[]{src="https://api.archbee.com/api/optimize/SSUUxKZUk9bFTEPNn_6Zo/sehdtYmb71A0NICh4Nyml_aws-iot-create-certificate.png" size="80" width="746" height="382" caption="Create a certificate screen" position="center" showCaption="true"}
6. Click **Create certificate**.
   The *Certificate created* screen appears.
   ::Image[]{src="https://api.archbee.com/api/optimize/SSUUxKZUk9bFTEPNn_6Zo/4xECEOxkSnjbd8n6dKL7r_aws-iot-certificate-success.png" size="80" width="1037" height="526" caption="Certificate created screen" position="center" showCaption="true"}
7. Click **Download **next to *A certificate for this thing*.
8. Click **Download **next to *A private key*.
9. Click **Keep **next to the downloaded files.
10. Click **Activate**, and then click **Attach a policy**.
    The *Add authorization to certificate* screen appears.
    ::Image[]{src="https://api.archbee.com/api/optimize/SSUUxKZUk9bFTEPNn_6Zo/CER_7HJZXXmFRNvhXVaWO_aws-iot-policy.png" size="80" width="751" height="402" caption="Add authorization to certificate screen" position="center" showCaption="true"}
11. Select the named **Thing1-Policy**, and then click **Done**.
    ::Image[]{src="https://api.archbee.com/api/optimize/SSUUxKZUk9bFTEPNn_6Zo/xT6c811L9MGH58HgKZa8J_aws-iot-certificate-success.png" size="80" width="1037" height="526" position="center" showCaption="false"}

## Step 4: Edit Policy

**To edit the policy: **

1. From the left pane, click **Policies**.
   The *Policies *pane appears. 
2. Click the named **Thing1-Policy**.
   The named *Thing1-Policy* dialog box appears.
   ::Image[]{src="https://api.archbee.com/api/optimize/SSUUxKZUk9bFTEPNn_6Zo/klxQ58Tn_WLxFba6BIi68_aws-iot-policy-details.png" size="80" width="749" height="530" caption="Policy dialog box" position="center" showCaption="true"}
3. Click **Edit policy document**.
   The *Edit Policy* screen appears.
   ::Image[]{src="https://api.archbee.com/api/optimize/SSUUxKZUk9bFTEPNn_6Zo/cRhCT48jqWCWdGVcb-8hn_aws-iot-policy-edit.png" size="80" width="752" height="526" caption="Edit Policy screen" position="center" showCaption="true"}
4. Scroll down the policy document, copy the last line, paste the copied line below, and edit it as follows:
   Change **sdk-nodejs** to *sdk-golang*.
   ::Image[]{src="https://api.archbee.com/api/optimize/SSUUxKZUk9bFTEPNn_6Zo/Fnaf_Q5NpkRt77wlgHJ7P_aws-iot-policy-edit-golang.png" size="80" width="590" height="101" caption="Edit policy code" position="center" showCaption="true"}
5. Click **Save as new version**.
6. Click the **Back **arrow to return to the *Policies *pane.

# Set Up Integration in Litmus Edge

After setting up your AWS account, you will need to log in to Litmus Edge to complete the steps below and complete the integration. 

## Step 5: Add Device

Follow the steps to [Connect a Device](docId:3eyAfPpweuVmBLCEy17sq). The device will be used to store tags that will be eventually used to create outbound topics in the connector. Make sure to select the **Enable Data Store** checkbox. 

## Step 6: Add Tag to Device

After connecting the device in Litmus Edge, you can [Add Tags](docId:8sE7z3PmRfwL1nmzcwaLX) to the device. Create tags that you want to use to create outbound topics for the connector. 

## Step 7: Retrieve Parameters for AWS Connector

You will have to log in to your AWS account to retrieve the parameters for the AWS connector. 

**To retrieve the parameters:**

1. Log in to your AWS account. 
2. Open the AWS IoT browser tab and click **Manage **>** Things**.
   The *Things *pane appears. 
3. Click **Thing\[#]**.
   The *Thing\[#}* dialog box appears.
4. From the left pane, click **Interact**.
   The pane changes to reflect your selection.
5. Copy the **REST API Endpoint **under the HTTPS section. This is the *Hostname *parameter for the AWS connector. 
6. Click **Secure > Policies**.
   The *Policies *pane appears.
7. Click **Thing\[#]-Policy**.
   The *Thing\[#]-Policy *dialog box appears.
8. Scroll to the bottom and copy SDK resource to your clipboard. For this use case, the SDK resource is **sdk-golang**. This is the *Client ID* parameter for the AWS connector. 
   ::Image[]{src="https://api.archbee.com/api/optimize/SSUUxKZUk9bFTEPNn_6Zo/cobC0-16iXGjmwvUbVR0X_aws-iot-things-sdk.png" size="80" width="927" height="647" caption="The SDK resource value" position="center" showCaption="true"}
9. Copy the first topic value. In this use case, the topic is **topic\_1**. This the *Integration Topic* value. 
   ::Image[]{src="https://api.archbee.com/api/optimize/SSUUxKZUk9bFTEPNn_6Zo/et2d9FRdGwyIfg82wBQcF_aws-iot-things-topic.png" size="80" width="951" height="606" caption="The topic value" position="center" showCaption="true"}

## Step 8: Add AWS IoT Core Connector

Follow the steps to [Add a Connector](docId\:ytsWGWeU6H6oEUnHj5hW3) and select the **MQTT - Amazon AWS IoT Core over SSL **provider.

Configure the following parameters. 

- **Name**: Enter a name for the connector. 
- **Hostname**: Paste the *REST API Endpoint* value copied in Step 6. 
- **Port**: Enter the MQTT broker port. The default value is **8883**. 
- **Certificate**: Paste the downloaded certificate in Step 3.  
- **Private key**: Paste the downloaded private key in Step 3. 
- **Client ID**: Paste the *SDK resource* copied in Step 6. 
- **QoS**: Confirm that the default value **0** is entered. The Quality of Service (QoS) level is an agreement between the sender of a message and the receiver of a message that defines the guarantee of delivery for a specific message.
- **Parallel Publish Count**: The number of messages being published simultaneously. Once the defined limit has been reached, subsequent messages are silently dropped. The default value is **100**.
- **Integration Topic**: Paste the topic value copied in Step 6. 
- **LWT topic**: The topic for Last Will and Testament feature of MQTT.
- **LWT payload**: The payload for Last Will and Testament feature of MQTT. 
- **LWT payload type**: The payload type for MQTT's Last Will and Testament feature. The options are *string *and *base64*. 
- **LWT QoS**: The Quality of Service value for MQTT's Last Will and Testament feature.
- **LWT retained**: Select this check box to retain the value for MQTT's Last Will and Testament feature. 
- **Throttling limit**: 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 9: Enable the Connector

After adding the connector, click the toggle in the connector tile to enable it. 

::Image[]{src="https://api.archbee.com/api/optimize/SSUUxKZUk9bFTEPNn_6Zo/3Zn4dsoTADVWs5tUSHlfM_awsiot.png" size="60" width="369" height="345" position="center" showCaption="false"}

If you see a *Failed *status, you can review the [Connector Logs](docId\:BEQQ0sSzwsv9v9rIF3rhk) and relevant error messages. 

## Step 10: Create Topics for Connector

You will now need to create topics for the connector. To create outbound topics, you have the option of importing the tag created in Step 6. To create inbound topics, you will have to manually create the topic.

## Create Outbound Topics

**To create outbound topics:**

1. Click the connector tile.
   The connector *Dashboard *appears. 
2. Click the **Topics **tab. 
3. Click the **Import from DeviceHub** tags icon.
   The *DeviceHub Import* dialog box appears.
   ![](https://api.main.archbee.co/api/optimize/SSUUxKZUk9bFTEPNn_6Zo/P4DmkIncgndRZM-a6izhV_nexzwy7zvifut6sw3syxy-importtagsicon.png)
4. Select all the tags to import and click **Import**. 

## Create Inbound Topics

Before creating inbound topics, copy the *Raw Topic* for tags that you want used for topics. See [Manage Tags](docId\:G9ROOmPC3XZ4Zq6CbNONc) for more information.

**To create inbound topics:**

1. Click the connector tile. 
2. Click the **Topics **tab. 
3. Click the **Add a new subscription** icon.
   The *Data Integration* dialog box appears.
   ![](https://api.main.archbee.co/api/optimize/SSUUxKZUk9bFTEPNn_6Zo/KTv6nD5K9Qg0a7QYZKzEx_aj9ttx4bumgxzesvkwk3l-addnewsubicon.png)
4. Configure the following parameters. 
   - **Data Direction**: Select **Remote to Local - Inbound**.
   - **Local Data Topic**: Paste the *Raw Topic *copied for the device tag.
   - **Remote Data Topic**: Confirm the topic where the data is pushed. 
   - **Enable**: Select the toggle to enable the topic. 
5. Click **Yes **to add the topic. 

## Step 11: Enable Topics

Ensure the topics you imported are enabled by returning to the *Topics *tab and clicking the **Enable all topics** icon. 

![](https://api.main.archbee.co/api/optimize/SSUUxKZUk9bFTEPNn_6Zo/HtkW-nbWXeAvOV8ru8B1U_image.png)

## Step 12: Verify Outbound Messages

You will need to log in to your AWS account to verify that outbound messages are being sent. 

**To verify outbound messages: **

1. Log in to your AWS account. 
2. Navigate to the *AWS Things* pane and click **Monitor**.
   The *Monitor *pane appears. 
3. Select **Hour **from the **Time range **drop-down list.
   The charts change to reflect your selection.
4. Click the browser **Refresh **to refresh the page.
   The *Successful connections* chart shows a connection.
5. Scroll down to the Messages published chart.
   The *Messages published* chart shows messages arriving.

## Step 13: View Outbound Messages in Litmus Edge Flow

You can create a flow in Litmus Edge to view the outbound messages. 

**To create a flow:**

1. Follow the steps to [Create a Flow](docId\:wh4ZihWF0PwMRYRbAZbco) and add the following nodes.
   - **DataHub Subscribe **
   - **Debug**
2. Double-click the **DataHub Subscribe **node.
   The *Edit DataHub Subscribe node* dialog box appears.
3. Paste the local topic you created in Step 9.  
4. If needed, configure the *Datahub Subscribe* connection. See the "Step 3: Configure Connector Nodes" section in [Create a Flow](docId\:wh4ZihWF0PwMRYRbAZbco) to learn more. 
5. Click **Done**, and then click **Deploy**.
6. Click the **debug **tab. See the *Additional Options* section in [Manage the Flow Canvas](docId\:Fd9Bu5dD1Nbv3Xvy-0xxn) for more details. 
7. Verify that *Test Message* appears in the debug results. 

You can return to *AWS Monitor* browser tab and view the *Messages published *chart to see the outbound messages are being sent.