Export Audit Logs to ADLS
Public preview: This feature is public preview and available to all accounts.
Create an ADLS shared access signature token for the export
Before Immuta can export audit events to your Azure Data Lake Storage (ADLS) Gen2 storage account, you need to create a shared access signature (SAS) token that allows the Immuta audit service to add audit logs to your specified ADLS storage account and file system.
Follow the Azure documentation to create the following in Azure:
An ADLS Gen2 storage account with the following settings required for audit export:
Enable hierarchical namespace
Standard performance is adequate, but premium may be used
A shared access signature (SAS) for your dedicated container with at least the following permissions at the storage account or container level:
Create
Write
Save the SAS token to use in the next steps. Do not navigate away from the SAS page unless you have saved the token.
Configure the audit export to ADLS
You can configure your audit export destination using one of two methods:
Using the Immuta CLI
Install the Immuta CLI
Download the binary in a tab below that corresponds to your operating system:
Linux x86_64 (amd64)
Linux ARMv8 (arm64)
Configure the Immuta CLI
For descriptions of the commands used below, see the Immuta audit export configuration CLI reference guide.
The SHA 256 checksum is available to verify the file at https://immuta-platform-artifacts.s3.amazonaws.com/cli/latest/immuta_cli_SHA256SUMS.
Run
immuta configure
in your terminal.Enter the URL of your Immuta tenant in the interactive prompt.
Enter your Immuta API Key.
Configure Immuta to export audit logs to ADLS
Set the following parameters in a JSON or YAML file:
interval: The interval at which audit logs will be exported to your ADLS storage. They can be sent at 2-, 4-, 6-, 12-, or 24-hour intervals.
storage account: The name of the storage account you created that your audit logs will be sent to.
file system: The name of the file system (or container) you created that your audit logs will be written to.
path: The name of the path in the file system. This will be a new folder or directory in the container where Immuta will send your audit logs for storage.
SAS token: The previously-generated SAS token.
Create an export configuration in Immuta by running the following command:
List all configurations
To view all of the export configurations created for your Immuta tenant, run the following command:
View a configuration
To review a specific export configuration, run the get command with the export configuration ID as the argument:
Disable a configuration
To disable a configuration, run the following command with the export configuration ID as the argument:
Enable a configuration
To enable a disabled configuration, run the following command with the export configuration ID as the argument:
Delete a configuration
To delete an export configuration, run the following command with the export configuration ID as the argument:
Using the audit service GraphQL API
Configure Immuta to export audit logs to ADLS Gen2
Pass the following fields into the $data variable used in the mutation in the next step:
interval: The interval at which audit logs will be exported to your ADLS storage. They can be sent at 2-, 4-, 6-, 12-, or 24-hour intervals.
storage account: The name of the storage account you created that your audit logs will be sent to.
file system: The name of the file system (or container) you created that your audit logs will be written to.
path: The name of the path in the file system. This will be a new folder or directory in the container where Immuta will send your audit logs for storage.
SAS token: The previously-generated SAS token.
Configure these settings in Immuta using the
createAdlsExportConfiguration
mutation:
Disable a configuration
To disable a configuration, use the disableExportConfiguration
mutation:
Enable a configuration
To enable a disabled configuration, use the enableExportConfiguration
mutation:
Last updated