tech.v3.io.s3 — techascent/tech.io.aws 4.08-2

Access to s3 resources via the io provider abstraction

byte-array-to-md5 clj

(byte-array-to-md5 byte-data)

create-default-s3-provider clj

(create-default-s3-provider)

default-s3-provider* clj

delete-object! clj

(delete-object! bucket k options)

empty-file-md5 clj

get-content-type clj

(get-content-type fname)

get-object clj

(get-object bucket k options)

get-object-metadata clj

(get-object-metadata bucket key options)

lazy-object-list-seq clj

(lazy-object-list-seq bucket prefix options)

list-objects clj

(list-objects
  bucket
  prefix
  {:keys [:tech.v3.io.s3/delimiter] :or {delimiter "/"} :as options})

list-some-objects clj

(list-some-objects bucket
                   prefix
                   {:keys [:tech.v3.io.s3/marker :tech.v3.io.s3/delimiter]
                    :or {delimiter "/"}
                    :as options})

List objects given a bucket and prefix

put-object! clj

(put-object! bucket
             k
             v
             {:keys [:tech.v3.io.s3/metadata :tech.v3.io.s3/verify-md5?]
              :or {metadata {}}
              :as options})

Lots of smarts around put-object to ensure the entire object is written correctly or the write fails. We check md5 hash if possible and we attempt to set the content type in order to ensure that if, for instance, you write a jpeg to an open bucket that jpeg is accessible via the browser using a normal https request.

s3-bucket-and-key->https-url clj

(s3-bucket-and-key->https-url
  s3-bucket
  s3-key
  &
  {:keys [:tech.v3.io.s3/endpoint] :or {endpoint "us-west-2"} :as options})

s3-bucket-key->url clj

(s3-bucket-key->url bucket key)

s3-provider clj

(s3-provider default-options)

s3-url->https-url clj

(s3-url->https-url
  s3-url
  &
  {:keys [:tech.v3.io.s3/endpoint] :or {endpoint "us-west-2"} :as options})

S3Provider clj

url-parts->bucket clj

(url-parts->bucket {:keys [path]})

url-parts->key clj

(url-parts->key {:keys [path]})