Managed identity authentication (processor v2)

IMPORTANT: This documentation is no longer updated. Refer to Elastic's version policy and the latest documentation.

Managed identity authentication (processor v2)

Available since 8.19.12.

Example configuration using Azure Managed Identity authentication with processor v2. This is ideal for workloads running on Azure VMs, Azure Container Apps, Azure Kubernetes Service (AKS), or other Azure services that support managed identities.

System-assigned managed identity:

filebeat.inputs:
- type: azure-eventhub
  eventhub: "insights-operational-logs"
  consumer_group: "$Default"
  auth_type: "managed_identity"
  eventhub_namespace: "your-namespace.servicebus.windows.net"
  storage_account: "your-storage-account"
  storage_account_container: "your-storage-container"

User-assigned managed identity:

filebeat.inputs:
- type: azure-eventhub
  eventhub: "insights-operational-logs"
  consumer_group: "$Default"
  auth_type: "managed_identity"
  eventhub_namespace: "your-namespace.servicebus.windows.net"
  managed_identity_client_id: "your-user-assigned-identity-client-id"
  storage_account: "your-storage-account"
  storage_account_container: "your-storage-container"

When using managed_identity authentication, the managed identity must have the appropriate Azure RBAC permissions. Refer to Required permissions for details.

« Client secret authentication (processor v2) Authentication »