Skip to content
Contact Support

Configuring s3cmd

To use Freezer and to configure s3cmd, you will need a current Freezer allocation. To apply for an allocation please go to MyNeSI.

Currently Freezer is only available via specific access points, HPC3 and Mahuika. We are currently completing security hardening prior to opening Freezer to wider access.

Configure s3cmd

You will need to configure the s3cmd tool before you use it for the first time. Configuring the s3cmd allows for user credentials and default buckets to be remembered. This will only need to be done once.

s3cmd --configure --multipart-chunk-size-mb=1024

Enter the following details when prompted in the terminal:

Access Key: Your username

Secret Key: This is the code from the 1-time link in your Freezer allocation email. Please let us know if you need to reset this key.

Please copy and paste the sections in blue.

Enter new values or accept defaults in brackets with Enter.
Refer to user manual for detailed description of all options.
Access key and Secret key are your identifiers for AWS S3. Leave them empty for using the env variables.
Access Key: Your username
Secret Key: Your Freezer Secret Key
Default Region: akl-1
Use "s3.amazonaws.com" for S3 Endpoint and not modify it to the target Amazon S3.
S3 Endpoint: freezer.nesi.org.nz:7070

Use "%(bucket)s.s3.amazonaws.com" to the target AWS S3. "%(bucket)s" and "%(location)s" vars can be used
if the target S3 system supports dns based buckets.
DNS-style bucket+hostname:port template for accessing a bucket:  freezer.nesi.org.nz:7070
Encryption password is used to protect your files from reading
by unauthorized persons while in transfer to S3
Encryption password: Leave blank, press <Enter>
Path to GPG program [/usr/bin/gpg]: Leave blank, press <Enter>

When using secure HTTPS protocol all communication with AWS S3
servers is protected from 3rd party eavesdropping. This method is
slower than plain HTTP, and can only be proxied with Python 2.7 or newer
Use HTTPS protocol: Yes
On some networks all internet access must go through a HTTP proxy.
Try setting it here if you can't connect to S3 directly
HTTP Proxy server name: Leave blank, press <Enter>

You will then be presented with a summary.

New settings:
  Access Key: User ID
  Secret Key: Your Freezer Secret Key
  Default Region: akl-1
  S3 Endpoint: freezer.nesi.org.nz:7070
  DNS-style bucket+hostname:port template for accessing a bucket: freezer.nesi.org.nz:7070
  Encryption password:
  Path to GPG program: /usr/bin/gpg
  Use HTTPS protocol: True
  HTTP Proxy server name:
  HTTP Proxy server port: 0

Press Y to confirm.

Test access with supplied credentials? [Y/n] Y
Please wait, attempting to list all buckets...
Success. Your access key and secret key worked fine :-)

Now verifying that encryption works...
Not configured. Never mind.

Save settings? [y/N] y
Configuration saved to '/home/<user_id>/.s3cfg'