Join fellow LogicMonitor users at the Elevate Community Conference and get hands-on with our latest product innovations.

Register Now

Resources

Explore our blogs, guides, case studies, eBooks, and more actionable insights to enhance your IT monitoring and observability.

View Resources

About us

Get to know LogicMonitor and our team.

About us

Documentation

Read through our documentation, check out our latest release notes, or submit a ticket to our world-class customer service team.

View Resources

Okta Log Ingestion with AWS Overview

Last updated on 24 June, 2025

If your organization uses Okta to securely manage user authentication across multiple applications and devices, you can use LogicMonitor to ingest logs from Okta. LogicMonitor leverages an AWS CloudFormation stack to automate the log collection, processing, and forwarding from Okta. For more information, see What is AWS CloudFormation? from AWS. 

Use the GitHub repository containing the Okta log integration to enter the relevant parameters and create the CloudFormation stack. For more information, see Okta Log Collector for LM Logs GitHub repository. Once the stack is created, the Okta logs will be ingested and forwarded based on your configuration. 

Review the following to see how Okta log ingestion works when integrated with AWS using CloudFormation stacks:

Okta Log Ingestion with AWS

For a step-by-step procedure on ingesting Okta logs with AWS, see Okta Log Collection with AWS

General Requirements for Ingesting Logs from Okta with AWS

To ingest Okta logs into LM, you need the following:

  • An AWS account with permissions to deploy and manage AWS CloudFormation stacks. For more information see, Lambda documentation from AWS.
  • An Okta account with access to the administrative console.

In This Article

Start Your Trial

Full access to the LogicMonitor platform.
Comprehensive monitoring and alerting for unlimited devices.