S3(n)

📦
version 2.0 · 2 versions
, in fedora 43, fedora 44, nixos 26.05, nixpkgs unstable

✨ S3 — Amazon S3 Web Service Interface ✨

okay bestie, sit down, hydrate, because we're about to read the manual page for the S3 package 💖 — it's the Tcl interface to Amazon's Simple Storage Solution web service, and it is so much. Manual name: S3(n), section n. Let's go 🦋

🌸 SYNOPSIS 🌸

package require Tcl 8.5 9

package require S3 ?1.0.5?

package require sha1 1.1

package require md5 2.1

package require base64 2.4

package require xsxp 1.1

S3::Configure ?-reset boolean? ?-retries integer? ?-accesskeyid idstring? ?-secretaccesskey idstring? ?-service-access-point FQDN? ?-use-tls boolean? ?-default-compare always|never|exists|missing|newer|date|checksum|different? ?-default-separator string? ?-default-acl private|public-read|public-read-write|authenticated-read|keep|calc? ?-default-bucket bucketname?

S3::SuggestBucket ?name?

S3::REST dict

S3::ListAllMyBuckets ?-blocking boolean? ?-parse-xml xmlstring? ?-result-type REST|xml|pxml|dict|names|owner?

S3::PutBucket ?-bucket bucketname? ?-blocking boolean? ?-acl {}|private|public-read|public-read-write|authenticated-read?

S3::DeleteBucket ?-bucket bucketname? ?-blocking boolean?

S3::GetBucket ?-bucket bucketname? ?-blocking boolean? ?-parse-xml xmlstring? ?-max-count integer? ?-prefix prefixstring? ?-delimiter delimiterstring? ?-result-type REST|xml|pxml|names|dict?

S3::Put ?-bucket bucketname? -resource resourcename ?-blocking boolean? ?-file filename? ?-content contentstring? ?-acl private|public-read|public-read-write|authenticated-read|calc|keep? ?-content-type contenttypestring? ?-x-amz-meta-* metadatatext? ?-compare comparemode?

S3::Get ?-bucket bucketname? -resource resourcename ?-blocking boolean? ?-compare comparemode? ?-file filename? ?-content contentvarname? ?-timestamp aws|now? ?-headers headervarname?

S3::Head ?-bucket bucketname? -resource resourcename ?-blocking boolean? ?-dict dictvarname? ?-headers headersvarname? ?-status statusvarname?

S3::GetAcl ?-blocking boolean? ?-bucket bucketname? -resource resourcename ?-result-type REST|xml|pxml?

S3::PutAcl ?-blocking boolean? ?-bucket bucketname? -resource resourcename ?-acl new-acl?

S3::Delete ?-bucket bucketname? -resource resourcename ?-blocking boolean? ?-status statusvar?

S3::Push ?-bucket bucketname? -directory directoryname ?-prefix prefixstring? ?-compare comparemode? ?-x-amz-meta-* metastring? ?-acl aclcode? ?-delete boolean? ?-error throw|break|continue? ?-progress scriptprefix?

S3::Pull ?-bucket bucketname? -directory directoryname ?-prefix prefixstring? ?-blocking boolean? ?-compare comparemode? ?-delete boolean? ?-timestamp aws|now? ?-error throw|break|continue? ?-progress scriptprefix?

S3::Toss ?-bucket bucketname? -prefix prefixstring ?-blocking boolean? ?-error throw|break|continue? ?-progress scriptprefix?

look at all those options, she's serving range 😌

💅 DESCRIPTION 💅

So this package gives you access to Amazon's Simple Storage Solution web service. ✨

Quick summary bestie: Amazon Simple Storage Solution is a for-fee web service that lets you store arbitrary data as "resources" inside "buckets" online. Head to http://www.amazonaws.com/ if you want the deets on that whole system. You reach the service over HTTP, either SOAP or REST. And like — real talk — a whole lot of this documentation is gonna be giving nothing if you're not already familiar with the terms and functionality of the Amazon S3 service. 🫶

This package provides the services for reading and writing the data items via the REST interface. It also hooks you up with some higher-level operations. Other packages in the same distribution provide even more functionality. 💖

Copyright 2006 Darren New. All Rights Reserved. NO WARRANTIES OF ANY TYPE ARE PROVIDED. COPYING OR USE INDEMNIFIES THE AUTHOR IN ALL WAYS. This software is licensed under essentially the same terms as Tcl. See LICENSE.txt for the terms.

not me putting the legal bit in pink, but seriously bestie, no warranties of any type, periodt 💀

😭 ERROR REPORTING 😭

The error reporting from this package makes use of $errorCode to spill more details on what happened than just throwing an error would. Any error caught by the S3 package (and we try to catch them all) comes back with an $errorCode that's a list having at least three elements. In all cases, the first element will be "S3". The second element takes on one of six values, and that element defines the value of the third and subsequent elements. S3::REST does not throw an error, it just returns a dictionary with the keys "error", "errorInfo", and "errorCode" set. That's what lets it be used reliably in the background. ✨

The possible second elements are these:

  • usage — The usage of the package is incorrect. For example, a command has been invoked which requires the library to be configured before the library has been configured, or an invalid combination of options has been specified. The third element of $errorCode supplies the name of the parameter that was wrong. The fourth usually provides the arguments that were actually supplied to the throwing proc, unless the usage error isn't confined to a single proc.
  • local — Something happened on the local system which threw an error. For example, a request to upload or download a file was made and the file permissions denied that sort of access. The third element of $errorCode is the original $errorCode.
  • socket — Something happened with the socket. It closed prematurely, or some other condition of failure-to-communicate-with-Amazon was detected. The third element of $errorCode is the original $errorCode, or sometimes the message from fcopy, or ...? (the "or ...?" is canon, I'm not making that up bestie 💀)
  • remote — The Amazon web service returned an error code outside the 2xx range in the HTTP header. In other words, everything went as documented, except this particular case was documented not to work. The third element is the dictionary returned from ::S3::REST. Note that S3::REST itself never throws this error, but just returns the dictionary. Most of the higher-level commands throw for convenience, unless an argument indicates they should not. If something is documented as "not throwing an S3 remote error", it means a status return is set rather than throwing an error if Amazon returns a non-2XX HTTP result code.
  • notyet — The user obeyed the documentation, but the author has not yet gotten around to implementing this feature. (Right now, only TLS support and sophisticated permissions fall into this category, as well as the S3::Acl command.)
  • xml — The service has returned invalid XML, or XML whose schema is unexpected. For the high-level commands that accept service XML as input for parsing, this may also be thrown.

👑 COMMANDS 👑

This package provides several separate levels of complexity. a whole hierarchy, she contains multitudes 🦋

  • The lowest level simply takes arguments to be sent to the service, sends them, retrieves the result, and provides it to the caller. Note: This layer allows both synchronous and event-driven processing. It depends on the MD5 and SHA1 and base64 packages from Tcllib (available at http://core.tcl.tk/tcllib/). Note that S3::Configure is required for S3::REST to work due to the authentication portion, so we put that in the "lowest level."
  • The next layer parses the results of calls, allowing for functionality such as uploading only changed files, synchronizing directories, and so on. This layer depends on the TclXML package as well as the included xsxp package. These packages are package required when these more-sophisticated routines are called, so nothing breaks if they are not correctly installed.
  • Also included is a separate program that uses the library. It provides code to parse $argv0 and $argv from the command line, allowing invocation as a tclkit, etc. (Not yet implmented.) — yes that typo is verbatim, I'm preserving the artifacts, it's part of the vibe ✨
  • Another separate program provides a GUI interface allowing drag-and-drop and other such functionality. (Not yet implemented.)
  • Also built on this package is the OddJob program. It is a separate program designed to allow distribution of computational work units over Amazon's Elastic Compute Cloud web service.

The goal is to have at least the bottom-most layers implemented in pure Tcl using only that which comes from widely-available sources, such as Tcllib. 💖

🧚 LOW LEVEL COMMANDS 🧚

These commands do not require any packages not listed above. They talk directly to the service, or they are utility or configuration routines. Note that the xsxp package was written to support this package, so it should be available wherever you got this package. 🎀

S3::Configure ?-reset boolean? ?-retries integer? ?-accesskeyid idstring? ?-secretaccesskey idstring? ?-service-access-point FQDN? ?-use-tls boolean? ?-default-compare always|never|exists|missing|newer|date|checksum|different? ?-default-separator string? ?-default-acl private|public-read|public-read-write|authenticated-read|keep|calc? ?-default-bucket bucketname?

There is one command for configuration, and that is S3::Configure. Here's the tea:

  • Called with no arguments, it returns a dictionary of key/value pairs listing all current settings. 👑
  • Called with one argument, it returns the value of that single argument.
  • Called with two or more arguments, it must be called with pairs of arguments, and it applies the changes in order.

There is only one set of configuration information per interpreter. 🦋

The following options are accepted:

  • -reset boolean — By default, false. If true, any previous changes and any changes on the same call before the reset option will be returned to default values. it's giving factory reset but for your config 💅
  • -retries integer — Default value is 3. If Amazon returns a 500 error, a retry after an exponential backoff delay will be tried this many times before finally throwing the 500 error. This applies to each call to S3::REST from the higher-level commands, but not to S3::REST itself. That is, S3::REST will always return httpstatus 500 if that's what it receives. Functions like S3::Put will retry the PUT call, and will also retry the GET and HEAD calls used to do content comparison. Changing this to 0 will prevent retries and their associated delays. In addition, socket errors (i.e., errors whose errorCode starts with "S3 socket") will be similarly retried after backoffs. 🔥
  • -accesskeyid idstring
  • -secretaccesskey idstring — both of these default to an empty string, and bestie you have to set them before you make literally any calls. This is your S3 ID 💳. Once you sign up for an account, go to http://www.amazonaws.com/, sign in, hit the "Your Web Services Account" button, pick "AWS Access Identifiers", and boom — your access key ID and secret access key are right there. Every single S3::REST call is authenticated. Blame Amazon for the poor choice of names, not me 🙈.
  • -service-access-point FQDN — defaults to "s3.amazonaws.com". This is the fully-qualified domain name of the server to contact for S3::REST calls. You should probably never need to touch this, unless someone else implements a compatible service, or you wanna test something by pointing the library at your own service 👀.
  • -slop-seconds integer — when comparing dates between Amazon and the local machine, two dates within this many seconds of each other are considered the same. So useful for clock drift correction, processing overhead time, and so on ⏰.
  • -use-tls boolean — defaults to false. This is not yet implemented 💀. If true, S3::REST will negotiate a TLS connection to Amazon. If false, unencrypted connections are used.
  • -bucket-prefix string — defaults to "TclS3". This string is used by S3::SuggestBucketName if that command is passed an empty string as an argument. It's how you tell different applications using the Amazon service apart. Your application should always set this, fr fr, to keep from interfering with the buckets of other users of Amazon S3 or with other buckets of the same user 🫶.
  • -default-compare always|never|exists|missing|newer|date|checksum|different — defaults to "always." If no -compare is specified on S3::Put, S3::Get, or S3::Delete, this comparison is used. Go see those commands for what the meanings actually are 👑
  • -default-separator string — defaults to "/". This is currently unused. It might make sense to use this for S3::Push and S3::Pull, but allowing resources to have slashes in their names that aren't marking directories would be problematic. Hence, this currently does absolutely nothing 💅.
  • -default-acl private|public-read|public-read-write|authenticated-read|keep|calc — defaults to an empty string. If no -acl argument is provided to S3::Put or S3::Push, this string is used (given as the x-amz-acl header if not keep or calc). If this is also empty, no x-amz-acl header is generated. This is not used by S3::REST 🚫.
  • -default-bucket bucketname — if no bucket is given to S3::GetBucket, S3::PutBucket, S3::Get, S3::Put, S3::Head, S3::Acl, S3::Delete, S3::Push, S3::Pull, or S3::Toss, and if this configuration variable is not an empty string (and not simply "/"), then this value will be used for the bucket. Super handy if one program does a large amount of resource manipulation within a single bucket 🪣✨.

🌈 S3::SuggestBucket ?name? 🌈

The S3::SuggestBucket command accepts an optional string as a prefix and returns a valid bucket containing the name argument and the Access Key ID. This makes the name unique to the owner and to the application (assuming the application picks a good name argument) 🔥.

If no name is provided, the name from S3::Configure -bucket-prefix is used. If that too is empty (which is not the default), an error is thrown 💀.

✨ S3::REST dict ✨

The S3::REST command takes as an argument a dictionary and returns a dictionary 📦. The return dictionary has the same keys as the input dictionary, and includes additional keys as the result. The presence or absence of keys in the input dictionary can control the behavior of the routine. It never throws an error directly, but includes keys "error", "errorInfo", and "errorCode" if necessary. Some keys are required, some optional. The routine can run either in blocking or non-blocking mode, based on the presence of resultvar in the input dictionary. This requires the -accesskeyid and -secretaccesskey to be configured via S3::Configure before being called 👈 don't forget that part.

The possible input keys are these:

  • verb GET|PUT|DELETE|HEAD — this required item indicates the verb to be used 🏃‍♀️.
  • resource string — this required item indicates the resource to be accessed. A leading / is added if not there already. It will be URL-encoded for you if necessary. Do not supply a resource name that is already URL-encoded. 🚨
  • ?rtype torrent|acl? — this indicates a torrent or acl resource is being manipulated. Do not include this in the resource key, or the "?" separator will get URL-encoded 😭.
  • ?parameters dict? — this optional dictionary provides parameters added to the URL for the transaction. The keys must be in the correct case (which is confusing in the Amazon documentation) and the values must be valid. This can be an empty dictionary or omitted entirely if no parameters are desired. No other error checking on parameters is performed.
  • ?headers dict? — this optional dictionary provides headers to be added to the HTTP request. The keys must be in lower case for the authentication to work. The values must not contain embedded newlines or carriage returns. This is primarily useful for adding x-amz-* headers. Since authentication is calculated by S3::REST, do not add that header here. Since content-type gets its own key, also do not add that header here 🙅‍♀️.
  • ?inbody contentstring? — this optional item, if provided, gives the content that will be sent. It is sent with a transfer encoding of binary, and only the low bytes are used, so use [encoding convertto utf-8] if the string is a utf-8 string. This is written all in one blast, so if you are using non-blocking mode and the inbody is especially large, you may wind up blocking on the write socket 😬.
  • ?infile filename? — this optional item, if provided, and if inbody is not provided, names the file from which the body of the HTTP message will be constructed. The file is opened for reading and sent progressively by [fcopy], so it should not block in non-blocking mode even if the file is very large 🦋. The file is transferred in binary mode, so the bytes on your disk will match the bytes in your resource. Due to HTTP restrictions, it must be possible to use [file size] on this file to determine the size at the start of the transaction.
  • ?S3chan channel? — this optional item, if provided, indicates the already-open socket over which the transaction should be conducted. If not provided, a connection is made to the service access point specified via S3::Configure, which is normally s3.amazonaws.com. If this is provided, the channel is not closed at the end of the transaction 🔌.
  • ?outchan channel? — this optional item, if provided, indicates the already-open channel to which the body returned from S3 should be written. That is, to retrieve a large resource, open a file, set the translation mode, and pass the channel as the value of the key outchan. Output will be written to the channel in pieces so memory does not fill up unnecessarily 🧠✨. The channel is not closed at the end of the transaction.
  • ?resultvar varname? — this optional item, if provided, indicates that S3::REST should run in non-blocking mode. The varname should be fully qualified with respect to namespaces and cannot be local to a proc. If provided, the result of the S3::REST call is assigned to this variable once everything has completed; use trace or vwait to know when this has happened 👀. If this key is not provided, the result is simply returned from the call to S3::REST and no calls to the eventloop are invoked from within this call.
  • ?throwsocket throw|return? — this optional item, if provided, indicates that S3::REST should throw an error if throwmode is throw and a socket error is encountered. It indicates that S3::REST should return the error code in the returned dictionary if a socket error is encountered and this is set to return. If throwsocket is set to return or if the call is not blocking, then a socket error (i.e., an error whose error code starts with "S3 socket") will be returned in the dictionary as error, errorInfo, and errorCode. If a foreground call is made (i.e., resultvar is not provided), and this option is not provided or is set to throw, then error will be invoked instead 💥.

Once the call to S3::REST completes, a new dict is returned, either in the resultvar or as the result of execution. This dict is a copy of the original dict with the results added as new keys 🎁. The possible new keys are these:

  • error errorstring
  • errorInfo errorstring
  • errorCode errorstring

If an error is caught, these three keys will be set in the result 💀. Note that S3::REST does not consider a non-2XX HTTP return code as an error 👑. The errorCode value will be formatted according to the ERROR REPORTING description. If these are present, other keys described here might not be 🫠.

  • httpstatus threedigits — the three-digit code that came back from the HTTP transaction, bestie. 2XX means good, 5XX means server error, etc. etc. 💅
  • httpmessage text — the little text blurb that trails after the status code. Like "OK" or "Forbidden" or whatever the vibe was. ✨
  • outbody contentstring — if outchan wasn't specified, this key holds a reference to the (unencoded) contents of the body that came back. And if Amazon handed you an error (as in, httpstatus is not a 2XX value, we hate that for us), the error message lives in outbody or gets written to outchan as appropriate. 🙈
  • outheaders dict — a whole dictionary of headers that Amazon sent back. The keys are always lower case. It's mostly there so you can hunt down the x-amz-meta-* headers if there are any, though stuff like last-modified and content-type is lowkey useful too. The keys of this dictionary are always lower case (yes, we said it twice, it's that serious). Both keys and values come trimmed of extraneous whitespace. 🧼

🌈 HIGH LEVEL COMMANDS 🌈

Okay so the routines in this section? They all make use of one or more calls to S3::REST to do their thing, and then they parse and manage the data in a way that's actually convenient. All of these commands throw errors as described in ERROR REPORTING unless it says otherwise. No cap. 🫶

In all these commands, all arguments are presented as name/value pairs, in any order. Every single argument name starts with a hyphen.

There are a few options that are common to many of the commands, and those common options get documented right here. 💖

  • -blocking boolean — if this is provided and it's false, then any calls to S3:REST will be non-blocking, and internally these routines will call [vwait] to get the results. Translation: these routines still return the same value, but they'll have event loops running while they wait for Amazon to get back to them. multitasking queen 👑
  • -parse-xml xmlstring — if you provide this, the routine skips actually communicating with Amazon and instead behaves as if the XML string you handed over was returned as the body of the call. Since several of these routines let you get data back in various formats, this argument is how you parse existing XML to extract the bits of info you need. Also super helpful for testing. 🧪
  • -bucket bucketname — almost every high-level command needs to know which bucket the resources live in, and this is how you tell it. (The only command that does not require this parameter is the one that lists available buckets.) You do not need to URL-encode this, even if it's got special or non-ASCII characters in it. It may or may not have leading or trailing spaces — commands normalize the bucket, we got you. If this isn't supplied, the value is taken from S3::Configure -default-bucket if that string isn't empty. Note that spaces and slashes are always trimmed from both ends and the rest must leave a valid bucket. ✂️
  • -resource resourcename — this specifies the resource of interest within the bucket. It may or may not start with a slash, both cases are handled, don't stress. This does not need to be URL-encoded either, even if it's got special or non-ASCII characters. 🌸
  • -compare always|never|exists|missing|newer|date|checksum|different — when commands copy resources to files or files to resources, the caller can specify that the copy should be skipped if the contents are the same. This argument says under what conditions the files should actually get copied. If you don't pass it, the result of S3::Configure -default-compare is used, which in turn defaults to "always." Here's what each value means, bestie:
    • always — always copy the data. This is the default. 💅
    • never — never copy the data. This is basically a no-op, except in S3::Push and S3::Pull where the -delete flag might make a difference.
    • exists — copy the data only if the destination already exists.
    • missing — copy the data only if the destination does not already exist.
    • newer — copy the data if the destination is missing, or if the date on the source is newer than the date on the destination by at least S3::Configure -slop-seconds seconds. If the source is Amazon, the date is taken from the Last-Modified header. If the source is local, it's taken as the mtime of the file. If the source data was specified as a string rather than a file, it's taken as right now, via [clock seconds]. ⏰
    • date — like newer, except copy if the date is newer or older.
    • checksum — calculate the MD5 checksum on the local file or string, ask Amazon for the eTag of the resource, and copy the data if they're different. Also copy the data if the destination is missing. Heads up: this can be slow with big local files unless the C version of the MD5 support is available. 🐌
    • different — copy the data if the destination does not exist. If the destination does exist and an actual file name was specified (rather than a content string), and the date on the file differs from the date on the resource, copy the data. If the data is provided as a content string, the "date" is treated as "right now", so it'll likely always differ unless slop-seconds is large. If the dates are the same, the MD5 checksums get compared, and the data gets copied if the checksums differ.
Note that "newer" and "date" don't care about the contents, and "checksum" doesn't care about the dates, but "different" checks both. 🎯

🎀 S3::ListAllMyBuckets 🎀

S3::ListAllMyBuckets ?-blocking boolean? ?-parse-xml xmlstring?
?-result-type REST|xml|pxml|dict|names|owner?

This routine performs a GET on the Amazon S3 service, which is defined to return a list of buckets owned by the account identified by the authorization header. (Blame Amazon for the dumb names, not us. 😭)

  • -blocking boolean — see above for the standard definition.
  • -parse-xml xmlstring — see above for the standard definition.
  • -result-type REST — the dictionary returned by S3::REST is the return value of S3::ListAllMyBuckets. In this case, a non-2XX httpstatus will not throw an error. You may not combine this with -parse-xml. 🚫
  • -result-type xml — the raw XML of the body is returned as the result (with no encoding applied).
  • -result-type pxml — the XML of the body as parsed by xsxp::parse is returned.
  • -result-type dict — a dictionary of the interesting portions of the XML is returned. That dictionary contains these keys:
    • Owner/ID — the Amazon AWS ID (in hex) of the owner of the bucket.
    • Owner/DisplayName — the Amazon AWS ID's Display Name.
    • Bucket/Name — a list of names, one for each bucket.
    • Bucket/CreationDate — a list of dates, one for each bucket, in the same order as Bucket/Name, in ISO format (as returned by Amazon).
  • -result-type names — a list of bucket names is returned with all other information stripped out. This is the default result type for this command. ✨
  • -result-type owner — a list containing two elements is returned. The first element is the owner's ID, and the second is the owner's display name.

🦋 S3::PutBucket 🦋

S3::PutBucket ?-bucket bucketname? ?-blocking boolean? ?-acl
{}|private|public-read|public-read-write|authenticated-read?

This command creates a bucket if it doesn't already exist. Bucket names are globally unique, so you may get a "Forbidden" error from Amazon even if you can't see the bucket in S3::ListAllMyBuckets. See S3::SuggestBucket for ways to minimize this risk. The x-amz-acl header comes from the -acl option, or from S3::Configure -default-acl if it wasn't specified. 💖

🍓 S3::DeleteBucket 🍓

S3::DeleteBucket ?-bucket bucketname? ?-blocking boolean?

This command deletes a bucket if it's empty and you have such permission. Note that Amazon's list of buckets is a global resource, requiring far-flung synchronization. So if you delete a bucket, it may be quite a few minutes (or hours 😭) before you can recreate it, and you'll be getting "Conflict" errors until then. The way that this is giving "you did this to yourself"... but also, slay, we respect the ambition. 💀

💜 S3::GetBucket 💜

S3::GetBucket ?-bucket bucketname? ?-blocking boolean? ?-parse-xml
xmlstring? ?-max-count integer? ?-prefix prefixstring? ?-delimiter
delimiterstring? ?-result-type REST|xml|pxml|names|dict?

This lists the contents of a bucket. That is, it returns a directory listing of resources within a bucket, rather than transferring any user data. It's the "window shopping" of S3 calls, honestly. 🛍️

  • -bucket bucketname — the standard bucket argument.
  • -blocking boolean — the standard blocking argument.
  • -parse-xml xmlstring — the standard parse-xml argument.
  • -max-count integer — if supplied, this is the most number of records to be returned. If not supplied, the code will iterate until all records have been found. Not compatible with -parse-xml. Note that if this is supplied, only one call to S3::REST will be made. Otherwise, enough calls will be made to exhaust the listing, buffering results in memory — so take care if you might have huge buckets. 🫣
  • -prefix prefixstring — if present, restricts the listing to resources with a particular prefix. One leading / is stripped if present.
  • -delimiter delimiterstring — if present, specifies a delimiter for the listing. The presence of this will summarize multiple resources into one entry, as if S3 supported directories. See the Amazon documentation for details. 🗂️
  • -result-type REST|xml|pxml|names|dict — this indicates the format of the return result of the command.

okay so the return flavors all hit different, here's the breakdown bestie 💅

  • REST — if -max-count is specified, you get back the dictionary that S3::REST returned. if -max-count is not specified, you get a list of all the dictionaries returned from the one or more calls to S3::REST. the whole haul. 💖
  • xml — if -max-count is specified, you get the body returned from S3::REST. if -max-count is not specified, you get a list of all the bodies returned from the one or more calls to S3::REST.
  • pxml — if -max-count is specified, the body returned from S3::REST gets passed through xsxp::parse and then returned. if -max-count is not specified, it's a list of all the bodies returned from the one or more calls to S3::REST, each one passed through xsxp::parse, and then returned. ✨
  • names — returns a list of every single name found in either the Contents/Key fields or the CommonPrefixes/Prefix fields. and if you didn't specify -delimiter and you didn't specify -max-count, this hands you a list of all the resources with the -prefix you gave it. slay.
  • dict — returns a dictionary. (and yes, only one dictionary even if -max-count wasn't specified. it's giving one-and-done.) the keys of that dictionary are, in order:
    • Name — the name of the bucket, from the final call to S3::REST.
    • Prefix — from the final call to S3::REST.
    • Marker — from the final call to S3::REST.
    • MaxKeys — from the final call to S3::REST.
    • IsTruncated — from the final call to S3::REST, so it's always false if -max-count is not specified.
    • NextMarker — always provided if IsTruncated is true, and calculated if Amazon doesn't provide it. may be empty if IsTruncated is false.
    • Key — a list of names of resources in the bucket matching the -prefix and -delimiter restrictions.
    • LastModified — a list of times of resources in the bucket, in the same order as Key, in the format returned by Amazon. (i.e., it is not parsed into a seconds-from-epoch.)
    • ETag — a list of entity tags (a.k.a. MD5 checksums) in the same order as Key.
    • Size — a list of sizes in bytes of the resources, in the same order as Key.
    • Owner/ID — a list of owners of the resources in the bucket, in the same order as Key.
    • Owner/DisplayName — a list of owners of the resources in the bucket, in the same order as Key. these are the display names.
    • CommonPrefixes/Prefix — a list of prefixes common to multiple entities. this one's only present if -delimiter was supplied. 👑

🎀 S3::Put 🎀

S3::Put ?-bucket bucketname? -resource resourcename ?-blocking boolean?
?-file filename? ?-content contentstring? ?-acl private|public-
read|public-read-write|authenticated-read|calc|keep? ?-content-type
contenttypestring? ?-x-amz-meta-* metadatatext? ?-compare comparemode?

this one sends data to a resource on Amazon's servers for storage, using the HTTP PUT command. the return? it hands back 0 if the -compare mode prevented the transfer, 1 if the transfer actually worked, or it throws an error if the transfer was attempted but failed. server 5XX errors and S3 socket errors get retried according to the S3:Configure -retries settings before it throws an error; other errors throw immediately, no waiting around. 😤

  • -bucket — this specifies the bucket the resource gets written into. leading and/or trailing slashes are removed for you, and spaces too. we handle that, you're welcome 💅
  • -resource — this is the full name of the resource within the bucket. a single leading slash gets removed, but not a trailing slash. spaces are not trimmed. note it. 📝
  • -blocking — the standard blocking flag.
  • -file — if you specify this, the filename must exist, must be readable, and must not be a special file or a directory file. [file size] must apply to it and must not change for the lifetime of the call. the default content-type is calculated based on the name and/or contents of the file. specifying this is an error if -content is also specified, but at least one of -file or -content must be specified. (the file is allowed to not exist or not be readable if -compare never is specified. just saying.)
  • -content — if you specify this, the contentstring gets sent as the body of the resource. the content-type defaults to "application/octet-string". only the low bytes are sent, so non-ASCII should use the appropriate encoding (such as [encoding convertto utf-8]) before you pass it to this routine, if necessary. specifying this is an error if -file is also specified, but at least one of -file or -content must be specified.
  • -acl — defaults to S3::Configure -default-acl if you don't specify it. it sets the x-amz-acl header on the PUT operation. if the value you give is calc, the x-amz-acl header is calculated based on the I/O permissions of the file to be uploaded; it is an error to specify calc and -content together. if the value is keep, the acl of the resource is read before the PUT (or the default is used if the resource doesn't exist), then set back to what it was after the PUT (if it existed). an error will occur if the resource is successfully written but the kept ACL can't then be applied. this should never happen. 👀
Note: calc is not currently fully implemented. so like… heads up bestie.
  • -x-amz-meta-* — if any header starts with -x-amz-meta-, its contents get added to the PUT command to be stored as metadata with the resource. again, no encoding is performed, and the metadata should not contain characters like newlines, carriage returns, and so on. it's best to stick with simple ASCII strings, or to fix the library in several places. your call. 🫶
  • -content-type — this overrides the content-type calculated by -file, or sets the content-type for -content.
  • -compare — this is the standard compare mode argument. S3::Put returns 1 if the data was copied, or 0 if the data was skipped because the comparison mode said it should be skipped.

💅 S3::Get 💅

S3::Get ?-bucket bucketname? -resource resourcename ?-blocking boolean?
?-compare comparemode? ?-file filename? ?-content contentvarname?
?-timestamp aws|now? ?-headers headervarname?

this one retrieves data from a resource on Amazon's S3 servers, using the HTTP GET command. it returns 0 if the -compare mode prevented the transfer, 1 if the transfer worked, or throws an error if the transfer was attempted but failed. server 5XX errors and S3 socket errors are retried according to the S3:Configure settings before throwing an error; other errors throw immediately. also, note that this is always authenticated as the user configured via S3::Configure -accesskeyid. want an unauthenticated GET? use the Tcllib http for that. 🔥

  • -bucket — this specifies the bucket the resource gets read from. leading and/or trailing slashes are removed for you, and spaces too. 💖
  • -resource — this is the full name of the resource within the bucket. a single leading slash gets removed, but not a trailing slash. spaces are not trimmed.
  • -blocking — the standard blocking flag.
  • -file — if you specify this, the body of the resource gets read into this file, incrementally, without pulling it entirely into memory first. the parent directory must already exist. if the file already exists, it must be writable. if an error is thrown part-way through the process and the file already existed, it may be clobbered. 💀 if an error is thrown part-way through and the file did not already exist, any partial bits will be deleted. specifying this is an error if -content is also specified, but at least one of -file or -content must be specified.
  • -timestamp — this is only valid in conjunction with -file. it may be specified as now or aws. the default is now. if now, the file's modification date is left up to the system. if aws, the file's mtime is set to match the Last-Modified header on the resource, synchronizing the two appropriately for -compare date or -compare newer. ✨
  • -content — if you specify this, contentvarname is a variable in the caller's scope (not necessarily global) that receives the value of the body of the resource. no encoding is done, so if the resource (for example) represents a UTF-8 byte sequence, use [encoding convertfrom utf-8] to get a valid UTF-8 string. if this is specified, the -compare is ignored unless it is never, in which case no assignment to contentvarname is performed. specifying this is an error if -file is also specified, but at least one of -file or -content must be specified. 🦋
  • -compare — bestie this is THE standard compare mode argument, okay? S3::Get hands you back 1 if the data actually got copied, or 0 if the data was skipped because of the comparison mode — which is its little way of saying "yeah we're good, skip it." 🫶
  • -headers — if you drop this, the headers that came back from the fetch get stashed in the variable you named, as a dictionary. It's giving the full package: content-type and x-amz-meta-* headers, plus the usual HTTP headers, the x-amz-id debugging headers, literally all of it. ⭐ And lowkey important: if no file got fetched (because of -compare or any other error), then no assignment to that variable happens at all. Nothing. Nada. 💅

🌸 S3::Head 🌸

S3::Head ?-bucket bucketname? -resource resourcename ?-blocking boolean?
?-dict dictvarname? ?-headers headersvarname? ?-status statusvarname?

This one fires a HEAD at the resource, no cap. It tells you whether a 2XX code came back from the request — and it will never throw an S3 remote error at you, it's way too chill for that. ✨ So if it returns 1, the resource exists and you can access it. Periodt. If it returns 0, something went sideways, and you should go check the -status result for the tea. 👑

  • -bucket — names the bucket you're reading the resource from. Leading and/or trailing slashes get removed for you, and so do spaces. It's self-cleaning, we love that. 🧚
  • -resource — the full name of the resource inside the bucket. A single leading slash gets removed, but NOT a trailing slash. And spaces? Not trimmed. Not even a little. 🙈
  • -blocking — the standard blocking flag, same as always.
  • -dict — if you specify it, the resulting dictionary from the S3::REST call gets assigned to the variable you named (and it doesn't have to be global, bestie) in the caller's scope.
  • -headers — if you specify it, the dictionary of headers from the result gets assigned to the variable you named (again, not necessarily global) in the caller's scope.
  • -status — if you specify it, that variable (not necessarily global!) in the caller's scope gets assigned a 2-element list. First element is the 3-digit HTTP status code. Second element is the HTTP message, like "OK" or "Forbidden". Two little pieces of info, chef's kiss. 🎀

💜 S3::GetAcl 💜

S3::GetAcl ?-blocking boolean? ?-bucket bucketname? -resource
resourcename ?-result-type REST|xml|pxml?

This command gets the ACL of the resource you point at, or throws an error if it's just not available. Rude of it, but okay. 😭

  • -blocking boolean — see above for the standard definition, you already know.
  • -bucket — the bucket you're reading the resource from. Leading and/or trailing slashes get removed for you, as do spaces. ✨
  • -resource — the full name of the resource within the bucket. A single leading slash is removed, but not a trailing slash. Spaces are not trimmed. Same deal as always. 💅
  • -parse-xml xml — the XML from a previous GetACL can be passed in here to get parsed into dictionary form. In this case, -result-type must be pxml or dict. iykyk.
  • -result-type REST — the dictionary returned by S3::REST is the return value of S3::GetAcl. And in this case, a non-2XX httpstatus will not throw an error. It's giving forgiving. 🫶
  • -result-type xml — the raw XML of the body is returned as the result, with no encoding applied. Just the raw, untouched tea. 🌸
  • -result-type pxml — the XML of the body as parsed by xsxp::parse is returned. Fancy. ✨
  • -result-type dict — this one fetches the ACL, parses it, and returns a dictionary with two elements. Obsessed.

The first element has the key "owner" whose value is the canonical ID of the owner of the resource. 👑

The second element has the key "acl" whose value is a dictionary. Each key in that dictionary is one of Amazon's permissions, namely "READ", "WRITE", "READ_ACP", "WRITE_ACP", or "FULL_CONTROL". Each value of each key is a list of canonical IDs or group URLs that have that permission. Elements are not in the list in any particular order, and not all keys are necessarily present — so don't come for me about the order. Display names are not returned, because honestly they're not especially useful; use pxml to obtain them if you need them. 💁

🦋 S3::PutAcl 🦋

S3::PutAcl ?-blocking boolean? ?-bucket bucketname? -resource
resourcename ?-acl new-acl?

This sets the ACL on the resource you named. It returns the XML that got written to the ACL, or throws an error if anything went wrong. Simple as that. 💅

  • -blocking boolean — see above for the standard definition.
  • -bucket — the bucket you're reading the resource from. Leading and/or trailing slashes get removed for you, as are spaces. 🧚
  • -resource — the full name of the resource within the bucket. A single leading slash is removed, but not a trailing slash. Spaces are not trimmed.
  • -owner — if you provide this, it's assumed to match the owner of the resource. Otherwise, a GET may need to be issued against the resource to find the owner. If you already have the owner (say, from a call to S3::GetAcl), you can pass the value of the "owner" key as the value of this option, and it'll be used when constructing the XML. Efficient queen. 👑
  • -acl — if you specify this, it provides the ACL the caller wants to write to the resource. If it's not supplied or it's empty, the value is taken from S3::Configure -default-acl. The ACL is written with a PUT to the ?acl resource. Okay so here's how it decides what you mean:
    • If the value passed to this option starts with "<", it's taken to be a body to be PUT to the ACL resource.
    • If the value matches one of the standard Amazon x-amz-acl headers (i.e., a canned access policy), that header is translated to XML and then applied. The canned access policies are private, public-read, public-read-write, and authenticated-read (in lower case).
    • Otherwise, the value is assumed to be a dictionary formatted as the "acl" sub-entry within the dict returned by S3::GetAcl -result-type dict. The proper XML is generated and applied to the resource. Note that a value containing "//" is assumed to be a group, a value containing "@" is assumed to be an AmazonCustomerByEmail, and otherwise the value is assumed to be a canonical Amazon ID. 🎀
Note that you cannot change the owner, so calling GetAcl on a resource owned by one user and applying it via PutAcl on a resource owned by another user may not do exactly what you expect. Fr fr, be careful with that one bestie. 💀

🌈 S3::Delete 🌈

S3::Delete ?-bucket bucketname? -resource resourcename ?-blocking
boolean? ?-status statusvar?

This command deletes the specified resource from the specified bucket. It returns 1 if the resource was deleted successfully, 0 otherwise. And it returns 0 rather than throwing an S3 remote error — no drama, just facts. ✨

  • -bucket — the bucket you're deleting the resource from. Leading and/or trailing slashes get removed for you, as are spaces. 🧚
  • -resource — the full name of the resource within the bucket. A single leading slash is removed, but not a trailing slash. Spaces are not trimmed.
  • -blocking — the standard blocking flag. You know the vibe.
  • -status — if specified, the variable you named (not necessarily global!) in the caller's scope gets set to a two-element list. First element is the 3-digit HTTP status code. Second element is the HTTP message, like "OK" or "Forbidden". And heads up: Amazon's DELETE result is 204 on success, that being the code indicating no content in the returned body. So don't panic when you see 204, it's literally slaying. 💅

👑 S3::Push 👑

S3::Push ?-bucket bucketname? -directory directoryname ?-prefix
prefixstring? ?-compare comparemode? ?-x-amz-meta-* metastring? ?-acl
aclcode? ?-delete boolean? ?-error throw|break|continue? ?-progress
scriptprefix?

This synchronises a local directory with a remote bucket by pushing the differences using S3::Put. 💖

Note that if something has changed in the bucket but not locally, those changes could be lost. Thus, this is not a general two-way synchronization primitive. (See S3::Sync for that, bestie.) 💀

Also note that resource names are case sensitive, so changing the case of a file on a Windows machine may lead to otherwise-unnecessary transfers. And note that only regular files are considered — so devices, pipes, symlinks, and directories are not copied. Sorry to the symlinks, they're just not invited. 🙈

  • -bucket — names the bucket you're pushing data into. 🎀
  • -directory — names the local directory the files get taken from. It must exist, be readable via [glob] and so on. And if only some of the files in there are readable, S3::Push will PUT those files that are readable and return, in its results, the list of files that could not be opened. Transparency queen. ✨
  • -prefix — names the prefix that gets added to all resources. That is, it's the remote equivalent of -directory. If you don't specify it, the root of the bucket gets treated as the remote directory. An example may clarify, so here you go:
S3::Push -bucket test -directory /tmp/xyz -prefix hello/world

In this example, /tmp/xyz/pdq.html will be stored as http://s3.amazonaws.com/test/hello/world/pdq.html in Amazon's servers. Also, /tmp/xyz/abc/def/Hello will be stored as http://s3.amazonaws.com/test/hello/world/abc/def/Hello in Amazon's servers. Without the -prefix option, /tmp/xyz/pdq.html would be stored as http://s3.amazonaws.com/test/pdq.html. See? Slay. 🌸

  • -blocking — this is the standard blocking option. Same as always, you got this. 🫶
  • -compare — if it's there, it gets passed to every single invocation of S3::Put. And obvi, if you don't specify it, S3::Configure -default-compare is what gets used instead. ✨
  • -x-amz-meta-* — if present, this also rides along to every invocation of S3::Put. Heads up: all copied files will have the same metadata. All of them. Same. 💅
  • -acl — if present, passed to each invocation of S3::Put.
  • -delete — defaults to false. If you set it true, resources chillin' in the destination that aren't in the source directory get yeeted with S3::Delete. And here's the tea: since only regular files are considered, the existence of a symlink, pipe, device, or directory in the local source will not stop a remote resource with a matching name from being deleted. 😭
  • -error — this controls how S3::Push acts when S3::Put throws an error. Quick note first: errors on the local file system, or while reading the list of resources in the remote bucket, always throw errors — no negotiating. This option is only about "partial" errors, aka when some files got copied and some didn't. Also, S3::Delete always gets finished up, with its errors just recorded in the return result.
    • throw — the error is rethrown with the same errorCode.
    • break — processing stops without throwing an error, the error is recorded in the return value, and the command returns with a normal return. The calls to S3::Delete are not started.
    • continue — this is the default. Processing keeps going without throwing, the error gets recorded in the return result, and it resumes with the next file in the local directory to be copied.
  • -progress — if you specify this and the indicated script prefix isn't empty, that script prefix gets invoked several times in the caller's context, with extra arguments, at various points in the processing. This lets you report progress without backgrounding anything. 🎀

The prefix gets invoked with additional arguments, where the first extra argument tells you which part of the process is being reported on. Here's the whole sequence, bestie:

  • First, the prefix is invoked with args as the first additional argument, and a dictionary representing the normalized arguments to the S3::Push call as the second additional argument.
  • Then the prefix is invoked with local as the first additional argument, and a list of suffixes of the files to be considered as the second argument.
  • Then the prefix is invoked with remote as the first additional argument, and a list of suffixes existing in the remote bucket as the second argument.
  • Then, for each file in the local list, the prefix is invoked with start as the first additional argument and the common suffix as the second additional argument.
  • When S3::Put returns for that file, the prefix is invoked with copy as the first additional argument, the common suffix as the second, and a third argument that will be "copied" (if S3::Put sent the resource), "skipped" (if S3::Put decided not to based on -compare), or the errorCode that S3::Put threw due to unexpected errors — in which case that third argument is a list that starts with "S3".
  • When all files have been transferred, the prefix may be invoked zero or more times with delete as the first additional argument and the suffix of the resource being deleted as the second, with a third argument that's either an empty string (if the delete worked) or the errorCode from S3::Delete if it failed.
  • Finally, the prefix is invoked with finished as the first additional argument and the return value as the second additional argument. 🦋

The return result from this command is a dictionary. The keys are the suffixes (i.e., the common portion of the path after the -directory and -prefix), while the values are either "copied", "skipped" (if -compare said not to copy the file), or the errorCode thrown by S3::Put, as appropriate. If -delete was true, there may also be entries for suffixes with the value "deleted" or "notdeleted", saying whether the attempted S3::Delete worked or not, respectively. 💖

There's one extra pair in the return result, whose key is the empty string and whose value is a nested dictionary. The keys of that nested dictionary include:

  • "filescopied" — the number of files successfully copied
  • "bytescopied" — the number of data bytes in the files copied, excluding headers, metadata, etc.
  • "compareskipped" — the number of files not copied due to -compare mode
  • "errorskipped" — the number of files not copied due to thrown errors
  • "filesdeleted" — the number of resources deleted due to not having corresponding files locally, or 0 if -delete is false
  • "filesnotdeleted" — the number of resources whose deletion was attempted but failed
Ngl, this is currently implemented somewhat inefficiently. It fetches the bucket listing (including timestamps and eTags), then calls S3::Put, which uses HEAD to find the timestamps and eTags again. Correcting this with no API change is planned for a future upgrade. 🙈

🌸 S3::Pull 🌸

S3::Pull ?-bucket bucketname? -directory directoryname ?-prefix
prefixstring? ?-blocking boolean? ?-compare comparemode? ?-delete
boolean? ?-timestamp aws|now? ?-error throw|break|continue? ?-progress
scriptprefix?

This synchronises a remote bucket with a local directory by pulling the differences using S3::Get. ⚠️ But real talk: if something has been changed locally but not in the bucket, those differences may be lost. This is not a general two-way synchronization mechanism. (See S3::Sync for that, bestie.) It creates directories if needed, and new directories are created with default permissions. ✨

Also note that resource names are case sensitive, so changing the case of a file on a Windows machine may lead to otherwise-unnecessary transfers. And pls try not to store data in resources that end with a slash, or which are prefixes of resources that otherwise would start with a slash — i.e., don't use this if you store data in resources whose names have to be directories locally. 💀

Yeah, this one's also currently implemented somewhat inefficiently. It fetches the bucket listing (including timestamps and eTags), then calls S3::Get, which uses HEAD to find the timestamps and eTags again. Correcting this with no API change is planned for a future upgrade.
  • -bucket — names the bucket from which data will be pulled.
  • -directory — names the local directory into which files will be written. It must exist, be readable via [glob], writable for file creation, and so on. If only some of the files in there are writable, S3::Pull will GET the writable ones and return, in its results, the list of files that couldn't be opened. 🫶
  • -prefix — the prefix of resources that will be considered for retrieval. See S3::Push for more details, examples, etc. (Of course, S3::Pull reads rather than writes, but the prefix is treated similarly.)
  • -blocking — this is the standard blocking option.
  • -compare — passed to each invocation of S3::Get if provided. Naturally, S3::Configure -default-compare is used if this isn't provided.
  • -timestamp — passed to each invocation of S3::Get if provided.
  • -delete — if specified and true, files that exist in the -directory that aren't in the -prefix will be deleted after all resources have been copied. Plus, empty directories (other than the top-level -directory) will be deleted, because Amazon S3 has no concept of an empty directory. 🌈
  • -error — see S3::Push for a description of this option.
  • -progress — see S3::Push for a description of this option. It differs slightly in that local directories may be included with a trailing slash to indicate they're directories. 💅

The return value from this command is a dictionary. It's identical in form and meaning to the description of the return result of S3::Push. It differs only in that directories may be included, with a trailing slash in their name, if they're empty and get deleted.

🎀 S3::Toss 🎀

S3::Toss ?-bucket bucketname? -prefix prefixstring ?-blocking boolean?
?-error throw|break|continue? ?-progress scriptprefix?

This deletes some or all resources within a bucket. It would be considered a "recursive delete" had Amazon implemented actual directories. 💅

  • -bucket — the bucket from which resources will be deleted.
  • -blocking — the standard blocking option.
  • -prefix — the prefix for resources to be deleted. Any resource that starts with this string will be deleted. This is required. To delete everything in the bucket, pass an empty string for the prefix. 🗑️✨
  • -error — if this is "throw", S3::Toss rethrows any errors it encounters. If this is "break", S3::Toss returns with a normal return after the first error, recording that error in the return result. If this is "continue", which is the default, S3::Toss continues on and lists all errors in the return result.
  • -progress — okay so if you set this and it's not an empty string, your script prefix gets called several times in the context of the caller, with extra arguments tacked on the end. Here's the whole lil sequence, bestie, don't skip it: first it's invoked with the first extra arg being args and the second being the processed list of arguments to S3::Toss. Then it's invoked with remote as the first extra arg and the list of suffixes in the bucket to be deleted as the second extra arg. Then it's invoked with the first extra arg being delete, the second being the suffix deleted, and the third being "deleted" or "notdeleted" depending on whether S3::Delete threw an error. And finally 💅 the script prefix gets invoked with a first extra arg of "finished" and a second extra arg of the return value.

The return value is a dictionary. The keys are the suffixes of files that S3::Toss attempted to delete, and their values are either the string "deleted" or "notdeleted". There's also one extra pair in there — its key is the empty string and its value is an embedded dictionary. The keys of that embedded dictionary include "filesdeleted" and "filesnotdeleted", and both of those have integer values. iykyk 📦

💀 LIMITATIONS 💀

  • The pure-Tcl MD5 checking is slow. If you're processing files in the megabyte range, consider making sure binary support is available. fr fr.
  • The commands S3::Pull and S3::Push fetch a directory listing that includes timestamps and MD5 hashes, and then they invoke S3::Get and S3::Put. If a complex -compare mode is specified, S3::Get and S3::Put will invoke a HEAD operation for each file to fetch timestamps and MD5 hashes of each resource <em>again</em>. It's expected that a future release of this package will solve this without any API changes. 🤞
  • The commands S3::Pull and S3::Push fetch a directory listing without using -max-count. The entire directory gets pulled into memory at once. For very large buckets, this could be a performance problem. The author, at this time, does not plan to change this behavior. Welcome to Open Source. 😌
  • S3::Sync is neither designed nor implemented yet. The intention would be to keep changes synchronised, so changes could be made to both the bucket and the local directory and get merged by S3::Sync.
  • Nor is -compare calc fully implemented. This is primarily due to Windows not providing a convenient method for distinguishing between local files that are "public-read" or "public-read-write". Assistance figuring out TWAPI for this would be appreciated. The U**X semantics are difficult to map directly as well. See the source for details. Note that there are not tests for calc, since it isn't done yet.
  • The HTTP processing is implemented within the library, rather than using a "real" HTTP package. Hence, multi-line headers are not (yet) handled correctly. Do not include carriage returns or linefeeds in x-amz-meta-* headers, content-type values, and so on. The author does not at this time expect to improve this.
  • Internally, S3::Push and S3::Pull and S3::Toss are all very similar and should be refactored. (they're giving copy-paste sisters 💀)
  • The idea of using -compare never -delete true to delete files that have been deleted from one place but not the other, yet not copying changed files, is untested.

🌈 USAGE SUGGESTIONS 🌈

To fetch a "directory" out of a bucket, make changes, and store it back:

file mkdir ./tempfiles
S3::Pull -bucket sample -prefix of/interest -directory ./tempfiles \
  -timestamp aws
do_my_process ./tempfiles other arguments
S3::Push -bucket sample -prefix of/interest -directory ./tempfiles \
  -compare newer -delete true

To delete files locally that were deleted off of S3 but not otherwise update files:

S3::Pull -bucket sample -prefix of/interest -directory ./myfiles \
  -compare never -delete true

🔮 FUTURE DEVELOPMENTS 🔮

The author intends to work on several additional projects related to this package, in addition to finishing the unfinished features. 👑

First, a command-line program allowing browsing of buckets and transfer of files from shell scripts and command prompts is useful.

Second, a GUI-based program allowing visual manipulation of bucket and resource trees not unlike Windows Explorer would be useful.

Third, a command-line (and perhaps a GUI-based) program called "OddJob" that will use S3 to synchronize computation amongst multiple servers running OddJob. An S3 bucket will be set up with a number of scripts to run, and the OddJob program can be invoked on multiple machines to run scripts on all the machines, each moving on to the next unstarted task as it finishes each. This is still being designed, and it is intended primarily to be run on Amazon's Elastic Compute Cloud. 🧚

🔒 TLS SECURITY CONSIDERATIONS 🔒

This package uses the TLS package to handle the security for https urls and other socket connections.

Policy decisions like the set of protocols to support and what ciphers to use are not the responsibility of TLS, nor of this package itself however. Such decisions are the responsibility of whichever application is using the package, and are likely influenced by the set of servers the application will talk to as well.

For example, in light of the recent POODLE attack [http://googleonlinesecurity.blogspot.co.uk/2014/10/this-poodle-bites-exploiting-ssl-30.html] discovered by Google, many servers will disable support for the SSLv3 protocol. To handle this change the applications using TLS must be patched, and not this package, nor TLS itself. Such a patch may be as simple as generally activating tls1 support, as shown in the example below.

package require tls
tls::init -tls1 1 ;# forcibly activate support for the TLS1 protocol

... your own application code ...

🐛 BUGS, IDEAS, FEEDBACK 🐛

This document, and the package it describes, will undoubtedly contain bugs and other problems. Please report such in the category amazon-s3 of the Tcllib Trackers [http://core.tcl.tk/tcllib/reportlist]. Please also report any ideas for enhancements you may have for either package and/or documentation. 🫶

When proposing code changes, please provide unified diffs, i.e the output of diff -u.

Note further that attachments are strongly preferred over inlined patches. Attachments can be made by going to the Edit form of the ticket immediately after its creation, and then using the left-most button in the secondary navigation bar.

🔑 KEYWORDS 🔑

amazon, cloud, s3

🎀 CATEGORY 🎀

Networking

2006,2008 Darren New. All Rights Reserved. See LICENSE.TXT for terms.

And that's a wrap on the whole page, bestie! 💖 This one's from tcllib, version 1.0.5, dated S3(n) — slay, go forth and sync your buckets responsibly. ✨🦋

📦 where this page comes from