---
updatedAt: 2026-08-26T22:54:37.000Z
agentTools:
  projectIndex: https://docs.nebulock.io/llms.txt
---

# Jamf

In this document we will go through the process of adding a JAMF integration in the Nebulock Platform.&#x20;

## Step 1: Obtain the Dedicated resources from Nebulock:

Reach out to your dedicated Nebulock Support or Customer Success representative to set up a dedicated S3 path, Role ARN, SQS Queue URL and IAM Role.&#x20;

* Must provide the external ID that JAMF defaults to in the Administrative → Data → Amazon S3

## Step 2: Set Up Telemetry in JAMF

In the Jamf Protect console, navigate to Telemetry. If a Telemetry Configuration does not exist yet, select `+ Create Telemetry`.

<Callout icon="📘" theme="info">
  Requirements: Jamf Protect ‘Telemetry’ must be configured within Jamf Protect’s Plans, Actions, and Telemetry before Nebulock can collect Endpoint Security logs via Jamf Protect.
</Callout>

<Image src="https://files.readme.io/7b9af7448f1f301c78013c5e44544d4d836bbdd294a8b597fa144973e504d595-Jamf-1.png" align="center" width="750px" border={true} />

Give the Telemetry Configuration a name, e.g., `nebulock-jamf-telemetry`, and a brief description. Then select ALL Logging options and Save.

<Image src="https://files.readme.io/72d691cdc475a4a3d20968cbfa04c88686e184f24bffd2f1e9d03ddc79c163c8-Jamf-2.png" align="center" width="750px" border={true} />

If an **Action Configuration** does not yet exist to collect alert and log data for Jamf Protect Cloud storage, select **Create Action** and configure the following:

1. **Name**
2. **Description**
3. **Jamf Protect Cloud:**
   1. **Collect alerts:** High to Informational
   2. **Collect logs:** Select *Telemetry* and *Unified logs* (Please note: Nebulock does not have a core set of Unified Logging Predicates, but may request adding some in the future.)
4. **Alert Data Collection Options**: Minimal or Everything *(preferred)*

<Image src="https://files.readme.io/69b68fdfae80ee99b39ba61c3d0fb1a1f76c81e18bb1d098b8abd76aedfb7a7a-Jamf-3.png" align="center" width="750px" border={true} />

Next, an existing Plan will need to be added (or a new one configured) so that endpoints with the Jamf Protect agent will forward the telemetry to S3/Nebulock via Jamf Protect Cloud.

1. Select **Plans** from the side-menu
2. Create a new plan or edit existing plan
3. **Ensure Telemetry is configured by selecting the correct configurations in the drop-down list**

<br />

## Step 3: Connect Jamf Protect telemetry to Nebulock

In Jamf, navigate to Administrative → Data → Amazon S3:

![](https://files.readme.io/b82b6855262ed3e403828953070708ed540cbd099bc2fd56b09007257601ee6c-image.png)

Fill out the details with the information below:

* **Bucket Name:&#x20;**&#x6E;ebulock-logs-sink
* **Prefix:** \<org\_id>/jamf/ (e.g. organization-live-1234/jamf)
* **IAM role:** Provided in step 1

## Step 4: Set Up Nebulock Integration

In Nebulock, navigate to **Integrations** > **Available Integrations**, select "Jamf" and fill out the fields with the data from Step 1

<Callout icon="📘" theme="info">
  Host ID can be found in the JAMF portal in the url. Usually is \<company_name>.protect&#x20;
</Callout>

![](https://files.readme.io/90da8277b9a26b8d3771e7ed66f2d04ace8b0bf2821d60a9fa48229e301265c4-image.png)