ExAws v1.0.0-beta1

See the readme for general changenotes.

This release updates the documentation and examples to use the new 1.0 style, and fixes a number of bugs along the way.

ExAws v0.4.13

Relaxed version requirements on SweetXML, and some tweaks for elixir 1.2

ExAws v0.4.9

This release adds support for the SQS service, many thanks to @adamkittelson.

It also includes additional S3 functionality.

Bug Fixes:

• Paths containing spaces no longer produce auth errors in S3
• 500 errors from AWS will be retried instead of erroring immediately

ExAws v0.4.6

BugFix: Dynamo secondary indices work properly now.

ExAws v0.4.3

[Bugfix] Reserved chars like : @ and so on now don't cause signing errors when uploading objects to S3 that have such characters in their path.
[DocFix] S3 and Dynamo now properly show configuration process for association with an OTP app.

ExAws v0.4.2

Removed Timex as a dependency.

ExAws v0.4.1

Breaking changes: Substantial S3 work

Bug fix: ExAws.Request.HTTPoison adapter written to ensure that the recv_timeout is set at a finite time.

ExAws v0.3.1

Updates

• Internalized authentication code for more consistent signing with s3 related urls
• Fix code authentication issue with instance roles
• Fix outdated convention of having "S" => "TRUE" from dynamo decode to true
• Update documentation.

ExAws v0.2.0

Features:

• Override configuration on a per request basis.
• AWS standard default config. No mix config required at all now. Defaults covered below.
• Use instance roles to pull credentials.
• Enable configuration options such as {:system, "AWS_SECRET_KEY"} that pull the specified environment variable at runtime.

v0.2.0 adds the ability to use the IAM role associated with an instance to obtain AWS keys. It will automatically refresh them as they expire. Below is the now default configuration for obtaining AWS keys. Note that it checks the environment first, and then the instance roles.

config :ex_aws,
  access_key_id: [{:system, "AWS_ACCESS_KEY_ID"}, :instance_role],
  secret_access_key: [{:system, "AWS_SECRET_ACCESS_KEY"}, :instance_role]

v0.2.0 also adds the ability to alter the configuration used on a per request basis. For example, to use AWS keys determined at the time of request do:

{access_key, secret_key} = determine_aws_auth # do whatever you do

ExAws.Dynamo.new(access_key_id: access_key, secret_access_key: secret_key)
|> ExAws.Dynamo.Impl.list_tables

BREAKING CHANGE:
Any clients that override the request function will need to note the changes to the request's arguments. Previously it was request(data, action) and it is now request(client, action, data). The client argument should be passed along to the Request.request function instead of MODULE as it currently is. Here's an example with Lambda: f4eca68#diff-c6a980311c2578661d17a86172da2b7dL193

ExAws v0.1.2

-[BugFix] basic S3.get_object works. Even though S3 isn't officially finished yet a few of the key functions do in fact work, and will be fixed when regressions occur.