Skip to main content

ckanext-s3filestore

Use Amazon S3 or Minio<https://minio.io/> as a filestore for resources.

Requirements

Requires CKAN 2.10+

GitHub Actions tested: 2.10, 2.11

Installation

To install ckanext-s3filestore:

  1. Activate your CKAN virtual environment, for example:

     . /usr/lib/ckan/default/bin/activate
    
  2. Install the ckanext-s3filestore Python package into your virtual environment:

2.1 From PyPI (NB This repository does not currently push versions to PyPI):

     pip install ckanext-s3filestore

2.2 Alternatively, install from source:

     pip install -e 'git+https://github.com/qld-gov-au/ckanext-s3filestore.git#egg=ckanext-s3filestore'
  1. Add s3filestore to the ckan.plugins setting in your CKAN config file (by default the config file is located at /etc/ckan/default/production.ini).

  2. Restart CKAN. For example if you've deployed CKAN with Apache on Ubuntu:

     ```sudo service apache2 reload```
    

Config Settings

Required:

ckanext.s3filestore.aws_bucket_name = a-bucket-to-store-your-stuff
ckanext.s3filestore.region_name = region-name
ckanext.s3filestore.signature_version = s3v4

Conditional:

ckanext.s3filestore.aws_access_key_id = Your-Access-Key-ID
ckanext.s3filestore.aws_secret_access_key = Your-Secret-Access-Key

Or:

ckanext.s3filestore.aws_use_ami_role = true

Optional:

# An optional path to prepend to keys
ckanext.s3filestore.aws_storage_path = my-site-name

# An optional setting to fallback to filesystem for downloads
ckanext.s3filestore.filesystem_download_fallback = true
# The ckan storage path option must also be set correctly for the fallback to work
ckan.storage_path = path/to/storage/directory

# An optional setting to change the ACL of the uploaded files.
# Default 'public-read'.
ckanext.s3filestore.acl = private

# An optional setting to change the ACL of files previously uploaded
# for the resource under different names.
# 'auto' means use the same visibility as the current version.
# Default 'private'.
ckanext.s3filestore.non_current_acl = auto

# An optional setting to control whether the ACLs of uploaded files
# are updated immediately when the dataset is updated, or queued
# for asynchronous processing. Defaults to True (ie asynchronous).
# NB Inline updates occur during the same transaction as the dataset update,
# and may cause significant overhead for datasets with many resources.
ckanext.s3filestore.acl.async_update = False

# An optional setting to specify which addressing style to use.
# This controls whether the bucket name is in the hostname or is
# part of the URL path. Options are 'path', 'virtual', and 'auto';
# default is 'auto'.
ckanext.s3filestore.addressing_style = path

# Set this parameter only if you want to use a provider like Minio
# as a filestore service instead of S3.
# Ignored when using virtual addressing.
ckanext.s3filestore.host_name = http://minio-service.com

# To use user provided filepath and not use internal url basename
# on download. This affects behaviour when using a URL that points
# to an earlier version of a resource, with a different file name.
# If True, the older file will be served.
# If False, the newest file will be served (similarly to the default
# CKAN filestore behaviour), but the older file will be available at
# /dataset/{id}/resource/{resource_id}/orig_download/{filename}
# Defaults to False.
ckanext.s3filestore.use_filename = True

# To mask the S3 endpoint with your own domain/endpoint when serving URLs to end users.
# This endpoint should be capable of serving S3 objects as if it were an actual bucket.
# The real S3 endpoint will still be used for uploading files.
ckanext.s3filestore.download_proxy = https://example.com/my-bucket/

# Cache control for signed URLs. Values are in seconds.
# 'signed_url_expiry': How long a URL is valid (default 1 hour).
# 'signed_url_cache_window': How long a URL will be reused,
# if the resource is not updated in the meantime (default 30 min).
# The expiry should be longer than the window (not equal);
# otherwise, a URL may expire before a new one is available.
# If either value is zero or negative, then URL caching is disabled.
# 'public_url_cache_window': How long a public (unsigned) URL will be reused.
ckanext.s3filestore.signed_url_expiry = 3600
ckanext.s3filestore.signed_url_cache_window = 1800
ckanext.s3filestore.public_url_cache_window = 86400

# Control how long the ACL of an S3 object will be held in cache.
# Uploading a new file overrides this. Default is 604800 (1 week).
ckanext.s3filestore.acl_cache_window = 2592000

# If set, then prior objects uploaded not matching current filename for a
#  resource may be deleted after the specified number of days from uploaded date.
# If less than zero, nothing is deleted. Defaults to -1.
#
# I.e. delete_non_current_days is set to 90 days
#  If resource was uploaded 91 days ago, it will be marked for deletion
#  If resource was uploaded 10 days ago, it will be deleted after 80 days time
#    until next job on dataset/resource is run.
#
# Note: If S3 Versioning is enabled, then file can be recovered per external policy.
#          Similar to same filename being used.
#       If S3 Versioning is not enabled, then file is not recoverable.
ckanext.s3filestore.delete_non_current_days = 90

# Queue used by s3 plugin, if not set, `default` queue is used
ckanext.s3filestore.queue = bulk

CLI

To upload all local resources located in ckan.storage_path location dir to the configured S3 bucket use:

ckan -c /etc/ckan/default/production.ini s3 upload all

Development Installation

To install ckanext-s3filestore for development, activate your CKAN virtualenv and do:

git clone https://github.com/qld-gov-au/ckanext-s3filestore.git
cd ckanext-s3filestore
pip install -e '.[dev]'

or

pip install -e 'git+https://github.com/qld-gov-au/ckanext-s3filestore.git#egg=ckanext-s3filestore[dev]'

Running the Tests

To run the tests, do:

pytest --ckan-ini=test.ini

To run the tests and produce a coverage report, first make sure you have coverage installed in your virtualenv (pip install coverage) then run:

pytest --ckan-ini=test.ini --cov=ckanext.s3filestore

Docker environment setup

docker start up

docker run -it -v "pwd":/build ubuntu:bionic /bin/bash

commands before travis setup cd /build apt-get update apt-get install sudo systemd postgresql-10 git python python-pip

export PGVERSION=10 && export CKAN_BRANCH=qgov-master && export CKAN_GIT_REPO=qld-gov-au/ckan cd /build bash bin/travis-build.bash pytest --ckan-ini=test.ini --cov=ckanext.s3filestore

Releasing a New Version of ckanext-s3filestore

ckanext-s3filestore is available on PyPI as https://pypi.python.org/pypi/ckanext-s3filestore. To publish a new version to PyPI follow these steps:

  1. Update the version number in the project.toml file. See PEP 440 for how to choose version numbers.

  2. Push to repo qld-gov-au/ckanext-s3filestore

  3. Create a signed version and push to repo qld-gov-au/ckanext-s3filestore

    git tag 0.0.2
    git push 0.0.2
    

This will trigger the github actions auto deploy system.

Change Log

0.3.0 Update from boto to boto3 Update to Ckan version 2.8+

0.2.0 Support for AMI Roles ACL for uploaded file can be configured don't assume that error codes are numeric fix filesystem fallback, resolves #28 set explicit ContentType on boto Put command and store the mimetype in CKAN resource table

0.1.1 Support for Flask-based requests

0.1.0 Fix downloading large files

0.0.9 Add populating of resources' last_modified field

0.0.8 Add option for fallback to local filesytem from s3

0.0.7 redirect always get string intead of unicode

0.0.6 Allow minio s3 like datastore

0.0.5 Add boto to install requires

0.0.4 Avoid exception when resources marked for clearing but not yet exist New, not yet created resources can be marked for deletion (with clear_upload) if the user cancels an upload and enters a URL instead. Check if resources have an id or if an old name is provided before trying to clear a file.

0.0.3 Requires CKAN 2.5+ as IUploader now in CKAN2.5

0.0.2 Change the resource file names to lower case

0.0.1 Alpha release of plugin

Metadata

Release files for ckanext-s3filestore 0.11.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for ckanext-s3filestore 0.11.1
File Size Uploaded Provenance Actions
ckanext_s3filestore-0.11.1.tar.gz 44.8 kB With provenance Details for ckanext_s3filestore-0.11.1.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for ckanext-s3filestore 0.11.1
File Interpreter ABI Platform Actions
ckanext_s3filestore-0.11.1-py3-none-any.whl Python 3 none any Details for ckanext_s3filestore-0.11.1-py3-none-any.whl

Total release size: 91.3 kB

Release files / ckanext_s3filestore-0.11.1.tar.gz

Download URL ckanext_s3filestore-0.11.1.tar.gz
Size 44.8 kB
Tags Source
SHA-256 checksum
How to use checksums
c943cca3acf9638da87af87227cdfdd0422553d46bf54fada11bc65831177992
BLAKE2b-256 checksum
How to use checksums
62004c2f70cfbab19bff33b4b8d5ab94b2a5f8ffd2a94223aad5d16c49b840e0
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 29, 2026.

Transparency log

Release files / ckanext_s3filestore-0.11.1-py3-none-any.whl

Download URL ckanext_s3filestore-0.11.1-py3-none-any.whl
Size 46.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
435a458a660b23a6e985cb6878092958df55c9e5cf92f141bb4f6805d9132987
BLAKE2b-256 checksum
How to use checksums
f81a49e66cf07579bbc95accf9015d2f77fe0a9b3228093f95344cd2f77ef3c1
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 29, 2026.

Transparency log

Security for ckanext-s3filestore 0.11.1

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for ckanext_s3filestore-0.11.1.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 29, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page