---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Amazon Data Firehose (MID-less)

# Set up an Amazon Data Firehose (MID-less) integration for Health Log Analytics {#ariaid-title1}

* Release version: Yokohama
* 
* Updated July 31, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read

Set up an integration to stream log data from Amazon Data Firehose directly to the ServiceNow datacenter, where it's queued for Health Log Analytics processing. There's no need to store AWS keys on your ServiceNow instance.

## Before you begin

This integration doesn't run on a MID Server.

Role required: evt_mgmt_admin

## About this task

You set up integrations through the Integrations Launchpad in Service Operations Workspace, which you access from the ITOM AIOps configuration center. The AIOps configuration center is a centralized workspace for configuring and managing AIOps features from a single
place. The integrations setup process reduces implementation time compared to manual data input setup in the classic interface in Health Log Analytics. For more information, see [Integrations Launchpad in Service Operations Workspace for ITOM](https://www.servicenow.com/docs/Uerz_nc8Z9osqGgNu7LISQ "The Integrations Launchpad showcases all Event Management connector integrations, allowing users to pull or push events from external or internal devices. This centralized hub simplifies Event Management by consolidating integration options in one place.").

## Procedure

1. Navigate to WorkspacesService Operations Workspace.
2. From the bottom of the navigation pane, select the AIOps configuration center icon ![ITOM AIOps configuration center icon]().  
   The ITOM AIOps configuration center page appears. The configuration center is a centralized workspace. Use it to configure and manage AIOps features from a single place.
3. From the Integrate section, under Integrations, select Add integration.  
   The Integrations Launchpad appears.
4. In the Browse integrations tab, enter <kbd class="ph userinput">Firehose</kbd> in the search field.
5. Select the Amazon Data Firehose (MID-less) integration tile.  
   Note:  
   If you start an integration setup before meeting all prerequisites, a message appears. You can cancel the setup and complete the prior requirements first. Alternatively, you can continue in draft mode and complete the requirements later. Note that you can't activate the integration until you have completed all the prerequisites.
6. On the Provide details form, fill in the fields.  
   For a description of the fields, see [Amazon Data Firehose integration configuration fields](https://www.servicenow.com/docs/96XCpXha5RQJu1TcisUL9A "Description of the fields on the Amazon Data Firehose integration configuration forms for Health Log Analytics.").
7. Select Next.
8. Follow one of the procedures provided on the Set-up instruction screen to install the integration in AWS.  
   You can perform the installation procedure using either AWS CloudFormation or the AWS Management Console. Both methods require the same input. The appropriate choice depends on your requirements and the size of your deployment:
   * Use AWS CloudFormation when you need automation, repeatability, and infrastructure-as-code benefits. It's best for deploying standardized configurations across multiple environments. AWS CloudFormation prompts for input automatically.
   * Use the AWS Management Console when you need manual setups or quick configurations without automation.

   {#il-connector-hla-firehose__ul_tnq_lgf_52c}Before you perform either of these procedures, copy the access token, the ServiceNow endpoint URL, and the integration ID to the clipboard. You need these values during the installation process.
9. Do one of the following:
   * If you completed all the prerequisites before starting the configuration, activate the integration either with or without AI-powered capabilities. Select the appropriate option:
     * Activate with AI enables AI-powered automatic mapping of log data. When the integration is activated successfully, the Overview tab is displayed and ServiceNow Otto collects and analyzes log data. An AI icon indicates that ServiceNow Otto auto-maps log data to service instances and components for contextual alert generation.
     * Activate activates the integration without AI-powered mapping. The integration is activated and the Overview tab is displayed.
     {#il-connector-hla-firehose__ul_bgh_wdg_g3c}
   * If you didn't complete all the prior requirements, select Save draft.

     The system saves the integration as a draft in the Integrations Launchpad
     Installed integrations tab, under Waiting for your action. You can complete the prerequisites and activate the installation later. For more information, see [Activate a draft integration in Health Log Analytics](https://www.servicenow.com/docs/JOHisk8K5~FoYHdLYY8Bgg "Activate an integration that was configured and saved as a draft in Health Log Analytics (HLA).").
   {#il-connector-hla-firehose__choices_wsz_tdg_g3c}
{#il-connector-hla-firehose__steps_ntf_1d4_cfc}

## What to do next

On the Overview tab, do the following:

* Use the displayed information to refine how Health Log Analytics reads the log data. For more information, see [Review log data streaming status for an integration](https://www.servicenow.com/docs/dLK~lbQI1jwzDxj9wJ0N5g "Review the log data streaming status and streaming sources of an active integration for Health Log Analytics on the integration's Overview screen. From this tab, you can investigate streaming issues and refine the integration settings. Leverage the displayed data to refine how HLA reads the log data by adjusting the integration's configuration.").
* Use the More options menu (![More options menu icon.]()) to open the Data Input Mapping, Source Type Structures, or Log Sources pages with context from the integration. If your log data is not properly mapped, structured, or sourced, go back and adjust the configuration. If the Service Operations Workspace Log Analytics application is installed, the More options menu also provides direct access to the Log Viewer. Use the Log Viewer to review raw log messages ingested by the integration. For more information, see:
  * [Log data auto-mapping and mapping](https://www.servicenow.com/docs/mf0bznHQxZJFB0M_~kSg~A "By default, the Health Log Analytics AI engine tries to auto-map every incoming log line to the correct tags. You can change automatic mapping results manually by defining a JavaScript function.")
  * [Source type structure adjustment](https://www.servicenow.com/docs/QrL5WXM7uUk9ET5jegVJAw "Health Log Analytics enables you to reclassify auto-classified properties and change auto-mapped labels. These adjustments help Health Log Analytics machine learning to better understand your priorities.")
  * [Review logs on the Log Viewer](https://www.servicenow.com/docs/Hh7qEnJebE7N2HDaFk_Log "The Log viewer tab lets you browse the logs for an alert by timestamp or time range, and visualize anomaly frequency within a specific time period. Customizing the displayed data and adjusting time filters enables you to better understand the framework in which the anomaly occurred, helping you find the root cause faster.")
  {#il-connector-hla-firehose__ul_lxn_qr5_l3c}
{#il-connector-hla-firehose__ul_ggk_nr5_l3c}

If you activated the integration with AI, verify that AI correctly auto-mapped log data to service instances and components. To do this, select View mapping under
Log context mapping. You can override the AI mapping by selecting a different log field from each list. For more information, see [Map logs to service instances, components, source types](https://www.servicenow.com/docs/l2KweYyeD6_33LgGJUQMFQ "Map your logs to service instances, components, and source types so that Health Log Analytics (HLA) can generate contextual alerts.").

*[\>]: and then