---
title: "Creating your own AWS IoT Endpoint for Pressac"
slug: "creating-your-own-aws-iot-endpoint-for-pressac"
updated: 2026-04-21T14:54:01Z
published: 2026-04-21T14:54:01Z
canonical: "help.nexudus.com/creating-your-own-aws-iot-endpoint-for-pressac"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.nexudus.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Creating your own AWS IoT Endpoint for Pressac

These instructions are only intended if your space wants to use its own AWS IoT endpoint and certificates with Pressac integration.

## Why use your own AWS IoT endpoint and certificates

While Nexudus can easily issue an AWS IoT endpoint and certificates for you under our own AWS account.

## Create your AWS IoT Endpoint for Pressac

1. Log in to your AWS IoT console.
2. Create a new policy based on the following JSON:

```
{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": "iot:Connect",
      "Resource": "*"
    },
    {
      "Effect": "Allow",
      "Action": "iot:Publish",
      "Resource": "*"
    },
    {
      "Effect": "Allow",
      "Action": "iot:Subscribe",
      "Resource": "*"
    }
  ]
}
```

Create a new thing, making sure to name it **nexudus_ingest** ![image.png](https://cdn.document360.io/4f9a66c7-3dbb-4052-97d8-5439302e1512/Images/Documentation/image%2810%29.png)

Make sure your thing device shadow is set to **Unnamed shadow** and click **Next**. ![image.png](https://cdn.document360.io/4f9a66c7-3dbb-4052-97d8-5439302e1512/Images/Documentation/image%2811%29.png)

Configure device certificates to automatically renew and click **Next**. ![image.png](https://cdn.document360.io/4f9a66c7-3dbb-4052-97d8-5439302e1512/Images/Documentation/image%2812%29.png)

Click **Create thing**.

The next step is to download the public key, private key, and Root CA1 certificates.

![image.png](https://cdn.document360.io/4f9a66c7-3dbb-4052-97d8-5439302e1512/Images/Documentation/image%2813%29.png)

Following that you can add a new message routing rule named **send_to_nexudus** with the details below.

![image.png](https://cdn.document360.io/4f9a66c7-3dbb-4052-97d8-5439302e1512/Images/Documentation/image%2814%29.png)

![image.png](https://cdn.document360.io/4f9a66c7-3dbb-4052-97d8-5439302e1512/Images/Documentation/image%2815%29.png)

LOCATION_REFERENCE is your location https://dashboard.nexudus.com/settings/0/0/0. If you operate more than one location, use the top-most location in your network.You can also use the **Data connector URL** in https://dashboard.nexudus.com/settings/integrations/pressac as the **HTTP Endpoint ** below.

The token below shown as "XXXXXX" is your Pressac shared secret from https://dashboard.nexudus.com/settings/integrations/pressac.

![image.png](https://cdn.document360.io/4f9a66c7-3dbb-4052-97d8-5439302e1512/Images/Documentation/image%2817%29.png)

Go to the Destinations section and select the new HTTP destination, which should be pending validation. ![image.png](https://cdn.document360.io/4f9a66c7-3dbb-4052-97d8-5439302e1512/Images/Documentation/image%2818%29.png)

Find the validation token in your logs at https://dashboard.nexudus.com/settings/6/2/0 under the heading "Your AWS destination confirmation token is XXX". Make sure you are browsing the correct location based on the "LOCATION_REFERENCE" you used earlier. Use the code to "confirm and activate" the new destination.

Lastly, in your Pressac gateway, enable the AWS IOT service with the following details

**Root Topic** nexudus/{gatewayname}/{devicename}

**Endpoint (if using Nexudus' AWS account)** aj779zceevmur-ats.iot.eu-west-1.amazonaws.com

![image.png](https://cdn.document360.io/4f9a66c7-3dbb-4052-97d8-5439302e1512/Images/Documentation/image%2819%29.png)