Persisting data in a s3 bucket

The persist configuration directive allows to define whether or not to store data on the disk: the rules downloaded from the redirection.io platform, the SSL certificates used in the reverse proxy, etc.

The most common way of confiuring the persistant storage is using a local folder, but it is also possible to configure a S3 remote storage. In this case, the instance.persist configuration directive must contain the following properties:

• endpoint: the S3 endpoint to use to store the data
• bucket: the S3 bucket to use to store the data
• access_key: the S3 access key to use to authenticate with the S3 endpoint
• secret_key: the S3 secret key to use to authenticate with the S3 endpoint
• region: the S3 region where the bucket is located

Here is an example:

instance:
    name: 'My Instance'
    persist:
        endpoint: s3.amazonaws.com
        bucket: my-bucket
        access_key: '${AWS_ACCESS_KEY_ID}'
        secret_key: '${AWS_SECRET_ACCESS_KEY}'
        region: '${AWS_DEFAULT_REGION}'
server:
    listen: '127.0.0.1:10301'

In the above example, the AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY and AWS_DEFAULT_REGION environment variables must be defined when the agent is started - they'll be replaced when the agent configuration is loaded.