Skip to main content

Configure S3 or Minio for Storing Execution Logs

Configure S3 or Minio for Storing Execution Logs

Rundeck execution logs are a set of files generated after each job execution. By default, Rundeck stores them on the local filesystem. Another way to store these logs is on a dedicated file storage service like AWS S3open in new window.

By delegating this storage to AWS S3 (or any other S3-compatible bucket system like Minioopen in new window) it’s possible to use some featuresopen in new window like S3 replication, security management, data persistence, and saving space on the local filesystem.

In PagerDuty Process Automation (formerly “Rundeck Enterprise”) clusteropen in new window, S3-compatible storage should be the default configuration to ensure access to logs from any cluster member.

This article explains how to configure Rundeck so that these execution logs are stored on services such as Amazon S3 or Minio.

Steps to configure S3 execution logs on Rundeck OSS / Process Automation for Global Config

  1. Stop the Rundeck service

    systemctl stop rundeckd
  2. S3 Log Storage Plugin

    Add the S3 log storage pluginopen in new window on the libext directory (at $RDECK_BASE/libext directory).

    wget -P $RDECK_BASE/libext

    @tab PagerDuty Process Automation Process Automation includes its own plugin for this out of the box

    ::: ::::

  3. To enable the S3 / Minio log storage plugin, add the following line on the file

    @tab PagerDuty Process Automation

    ::: ::::

  4. Then open the file and add the S3 / Minio bucket info as follow:${job.project}/${job.execid}.log


  • endpoint: A custom S3 compatible endpoint to use, such as
  • pathStyle: Optional, boolean, default=False, set to True if you need to define the bucket in your S3 like endpoint URL. e.g: https://<s3_like_end_point_url\>/<your_bucket_name\>
  • AWSAccessKeyId: AWS access key, required if using AWSSecretKey.
  • AWSSecretKey: AWS secret key, required if using AWSAccessKeyId.
  • AWSCredentialsFile: Properties file which contains accessKey and secretKey entries. The alternative to specifying the AWSAccessKeyId and AWSSecretKey
  • bucket: The name of the S3 bucket to use. This is the shorthand name, eg test-rundeck-logs
  • region: The Region your Instance is located, eg us-east-1

Test basic setup

  1. Start the Rundeck service.
  2. Create a new project.
  3. Create a new job and then execute it, now the execution log is stored in the S3/Minio bucket.

  4. From Rundeck click on the Gear Icon and then to the Log Storage option, now you can see the Log Storage Activity.

PagerDuty Process Automation (formerly “Rundeck Enterprise”) System Configuration

  1. As admin rights users click on the Gear Icon and then click on “System Configuration”.

  2. Then click on the “+ Add Config” button.

  3. Add the following property rundeck.execution.logs.fileStoragePlugin with the following value

  4. Add the following custom properties:

  5. Restart the PagerDuty Process Automation service.

Steps to configure S3 execution logs on Rundeck OSS / Process Automation for individual projects

  1. As admin rights users click on Project Settings then Edit Configuration and then Edit Configuration File

  2. Then add these lines with your information:${job.project}/${job.execid}.log
  1. Then click Save button.
  2. Restart the PagerDuty Process Automation service.

Docker Config

Extending the image

The S3 Log Storage Plugin isn’t bundled out of the box with Rundeck. To use it on a Docker image it is necessary to extend the image using Remco. Remcoopen in new window is used to generate the Rundeck configuration files from templates. This allows storing parts of the configuration space in different backends. The default configuration uses environment variables.

The Remco documentation is available hereopen in new window.

Full Docker Minio / Rundeck example

This is the example file structure of a custom Rundeck image with the S3 Log Storage Plugin.

The Dockerfile file content (inside docker project base directory)

FROM rundeck/rundeck:4.5.0

# root user tasks
USER root

# install python
RUN apt-get -y update && \
   apt-get -y install python3-pip && \
   pip install --upgrade pip

# rundeck user tasks
USER rundeck

ADD --chown=rundeck:root libext/
COPY --chown=rundeck:root remco /etc/remco
COPY --chown=rundeck:root plugins/* ./libext/

The docker-compose.yml file content (inside docker project base directory):

version: '3'
     context: .
       IMAGE: rundeck/rundeck:4.5.0
   - 4440:4440
     RUNDECK_GRAILS_URL: 'http://localhost:4440'
   image: minio/minio:latest
     - 9000:9000
     - 9001:9001
   entrypoint: sh
   command: -c 'mkdir /rundeck && /opt/bin/minio server /rundeck --console-address ":9001"'
       MINIO_ACCESS_KEY: minioadmin
       MINIO_SECRET_KEY: minioadmin
    image: minio/mc:latest
      - minio
    entrypoint: >
      /bin/sh -c "
      /usr/bin/mc config host add myminio http://minio:9000 minioadmin minioadmin;
      /usr/bin/mc mb myminio/rundeck;
      /usr/bin/mc policy download myminio/rundeck;

The file content (inside myrundeck/remco/resources.d/directory):

	src     	= "${REMCO_TEMPLATE_DIR}/"
	dst     	= "${REMCO_TMP_DIR}/framework/"
	mode    	= "0644"

The file (inside myrundeck/remco/resources.d/directory):

	src     	= "${REMCO_TEMPLATE_DIR}/"
	dst     	= "${REMCO_TMP_DIR}/rundeck-config/"
	mode    	= "0644"

The file (inside myrundeck/remco/templates/directory)${job.project}/${job.execid}.log{{ getv("/rundeck/plugin/executionfilestorage/s3/accesskey") }}{{ getv("/rundeck/plugin/executionfilestorage/s3/secretkey") }}{{  getv("/rundeck/plugin/executionfilestorage/s3/endpoint") }}{{ getv("/rundeck/plugin/executionfilestorage/s3/pathstyle") }} (inside myrundeck/remco/templates/ directory):


Building and Running

  1. With all environment set, build the image doing: docker-compose build
  2. After that, run the project using the following command: docker-compose up
  3. Enter the Rundeck instance in the following URL: http://localhost:4000, user: admin, password: admin.
  4. Create a new Project.
  5. Go to the “Commands” Section and dispatch any command against the local node.
  6. Check the Minio web interface (http://localhost:9001open in new window, user: minioadmin, password: minioadmin), now all Rundeck executions are stored on the “rundeck” bucket.