Automatic backup of compressed log files to any S3 compatible backend

When configured, logga rotates log files into compressed zip files. The helper looks for these zip files being created and uploads them to an S3 compatible storage.

The repository is a work in progress, not fully supported yet. Use it with caution.

Add the following lines to your logga configuration yaml:

s3:
  bucket: [string | bucket to upload zips to]
  endpoint: [string | s3 storage endpoint]
  region: [string | bucket region]
  keychainAuthentication: [bool | read S3 credentials from keychain]

You are free to save this config as a separate file, just don't forget to point the helper to the correct config file location.

Read more

You can use the following keys to configure the helper via Profiles:

<key>S3Bucket</key>
<string>testbucket</string>
<key>S3Endpoint</key>
<string>http://test2</string>
<key>S3Region</key>
<string>us-test-3</string>
<key>S3KeychainAuthentication</key>
<true/>

Configuration Profile take precedence over the yaml configuration. If (for some reason) the helper fails to use the Profile, it falls back to yaml configuration.

config-path: where to find the config.yaml (default: /Library/Application Support/Logga/config.yaml)
profile-path: Configuring the helper via MDM Configuration Profiles is supported. If your Profile uses the com.logga.client Bundle ID, then you don't ever need to override this flag. (default: /Library/Managed Preferences/com.logga.client.plist)
bundle-id: Only override, if your Configuration Profile uses a different Bundle ID. (default: com.logga.client)
watch-dir: Points to the directory to watch for zip creation events. (default: /Library/Application Support/Logga)

Don't be afraid of the AWS wording, the binary will upload to any S3 compatible storage backends.

When keychainAuthentication is set to false, the binary will expect these good old AWS env vars to connect to the S3 storage:

AWS_ACCESS_KEY_ID
AWS_SECRET_ACCESS_KEY
AWS_DEFAULT_REGION

When keychainAuthentication is set to true, the binary will try to read S3 credentials from the Keychain.

Prior using the binary, create two Keychain password entires for the current user (that runs the helper). The service names should be respectively:

com.logga.aws-access-key-id
com.logga.aws-secret-access-key

sudo logga-helper --config-path config.yaml --profile-path /tmp --bundle-id com.test.service --watch-dir /Users

First, move the binary to /usr/local/bin

Second, add your S3 credentials to the System Keychain:

sudo security add-generic-password -a root -s com.logga.aws-access-key-id -w $AWS_ACCESS_KEY_ID -T /usr/local/bin/logga-helper /Library/Keychains/System.keychain

sudo security add-generic-password -a root -s com.logga.aws-secret-access-key -w $AWS_SECRET_ACCESS_KEY -T /usr/local/bin/logga-helper /Library/Keychains/System.keychain

Third, copy the com.logga.helper.plist to /Library/LaunchDaemons.

Load the daemon:
sudo launchctl load /Library/LaunchDaemons/com.logga.helper.plist

Of course if you need want to use different flags (than default), modify the plist.