Humio supports archiving ingested logs to Amazon S3. The archived logs are then available for further processing in any external system that integrates with S3. The files written by Humio in this format are not searchable by Humio—this is an export meant for other systems to consume.
Archiving works by running a periodic job inside all Humio nodes, which looks for new, unarchived segment files. The segment files are read from disk, streamed to an S3 bucket, and marked as archived in Humio.
An admin user needs to set up archiving per repository. After selecting a repository on the Humio front page, the configuration page is available under Settings.
For slow-moving datasources it can take some time before segment files are completed on disk and then made available for the archiving job. In the worst case, before a segment file is completed, it must contain a gigabyte of uncompressed data or 30 minutes must have passed. The exact thresholds are those configured as the limits on mini segments.
When uploading a segment file, Humio creates the S3 object key based on the tags, start date, and repository name of the segment file. The resulting object key makes the archived data browseable through the S3 management console.
Humio uses the following pattern:
Read more about Tags.
The default archiving format is NDJSON and optionally raw log lines. When using NDJSON, the parsed fields will be available along with the raw log line. This incurs some extra storage cost compared to using raw log lines but gives the benefit of ease of use when processing the logs in an external system.
Enabling Humio Cloud to write to your S3 bucket means setting up AWS cross-account access.
Log in to the AWS console and navigate to your S3 service page.
Click the name of the bucket where archived logs should be written.
Enter the canonical ID for Humio( f2631ff87719416ac74f8d9d9a88b3e3b67dc4e7b1108902199dea13da892780 ) and check Object Access Read and Write Permission, then click Save.
In Humio, go to the repository you want to archive and select. Configure by giving the bucket name, region, and then Save.
If tag grouping is defined for a repository, the segment files will be split by each unique combination of tags present in a file. This results in a file in S3 per each unique combination of tags. The same layout pattern is used as in the normal case. The reason for doing this is to make it easier for a human operator to determine whether a log file is relevant.