Forge Home


Cloud File Module


7,983 latest version

3.1 quality score

We run a couple of automated
scans to help you access a
module's quality. Each module is
given a score based on how well
the author has formatted their
code and documentation and
modules are also checked for
malware using VirusTotal.

Please note, the information below
is for guidance only and neither of
these methods should be considered
an endorsement by Puppet.

Version information

  • 0.1.8 (latest)
  • 0.0.7
  • 0.0.6
  • 0.0.5
  • 0.0.4
  • 0.0.3
  • 0.0.2
  • 0.0.1
released Mar 27th 2016
This version is compatible with:
  • Puppet 3.x

Start using this module

  • r10k or Code Manager
  • Bolt
  • Manual installation
  • Direct download

Add this module to your Puppetfile:

mod 'jbussdieker-cloud_file', '0.1.8'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add jbussdieker-cloud_file
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install jbussdieker-cloud_file --version 0.1.8

Direct download is not typically how you would use a Puppet module to manage your infrastructure, but you may want to download the module in order to inspect the code.

Tags: file, cloud, s3


jbussdieker/cloud_file — version 0.1.8 Mar 27th 2016

Cloud File Module

Puppet Forge Build Status

This module manages files hosted on cloud providers. Currently only S3 is supported.


  • ensure: present, absent, latest. default: present.
  • path: The local path for the destination file.
  • source: Specify the source url of the cloud file ex (bucket_name/path/to/file).
  • access_key_id: The AWS access key to connect to S3. (optional)
  • secret_access_key: The AWS secret access key to connect to S3. (optional)

Please note: This module requires the aws-sdk gem to be installed prior to use.


file { '/opt/scripts':
  ensure => directory,
  owner  => root,
  group  => root

cloud_file {'/opt/scripts/':
  ensure            => present,
  source            => 'bucket/path/to/',
  access_key_id     => 'EXAMPLE_ACCESS_KEY_ID',
  secret_access_key => 'EXAMPLE_SECRET_ACCESS_KEY',

# If you omit the access_key_id and secret_access_key, the S3 client will
# attempt to authenticate automatically by one of the methods described
# here: