Skip to content

Releases: cloudyr/aws.signature

v0.5.0

08 May 15:43
Compare
Choose a tag to compare
  • New Maintainer: @jon-mago
  • Fix use of file system credentials (Thanks to @lgjohnson)
  • Fix use of ECS metadata (Requires aws.ec2metadata >= 0.1.6)
  • Rewrite some internals and tests
  • Removed locate_credentials() call from internal signature_v4() function. (#33)
  • signature_v4_auth() and signature_v2_auth() gain a force_credentials argument. If force_credentials = TRUE, user-supplied values are used and no call to locate_credentials() is made. (#33)

Minor feature additions

27 Jul 10:30
Compare
Choose a tag to compare

User-visible changes

  • Allow use of ECS metadata where available, using new functionality in aws.ec2metadata (>0.1.5). (h/t @jon-mago #23, #30)
  • Incorporated standard environment variables AWS_SHARED_CREDENTIALS_FILE and AWS_PROFILE into code as appropriate and tweaked locate_credentials() accordingly.
  • signature_v4_auth() and signature_v2_auth() now returns all inputs to facilitate using the return value in constructing an HTTP request.
  • Updated documentation.

Bug fixes

  • Fixed a bug in the default datetime argument in several functions. (#28, h/t @yansonz)
  • Removed some tests from execution on CRAN.

Improved Consistency with Other Clients

03 Apr 09:20
Compare
Choose a tag to compare

This is a minor release that includes some important changes to the behavior of locate_credentials() and also includes the default use of an AWS credentials file if present, making the behavior of this (and all other cloudyr packages) more consistent with clients for other languages and the AWS CLI.

Changes to user-visible behavior

  • On namespace load, the package now checks for the presence of environment variables and, if absent, attempts to call use_credentials() (with defaults) to that behavior is more similar to other AWS client libraries. (cloudyr/aws.s3#184, h/t Dan Tenenbaum)
  • The profile argument of use_credentials() now defaults to Sys.getenv("AWS_PROFILE", "default") for consistency with other AWS client libraries.
  • locate_credentials() returns region = default_region even when no other credentials are found.
  • locate_credentials() now attempts to look in instance metadata for a region, when called from an EC2 instance. Updated documentation to describe the need for aws.ec2metadata on EC2 instances. (see cloudyr/aws.s3#151)
  • The set of fall backs for values of region have been standardized and documented for locate_credentials().

Bug fixes

  • read_credentials() now trims excess whitespace from profile names. (#22, h/t Paul Ingles)

Bug fixes in locate_credentials()

01 Jul 07:50
Compare
Choose a tag to compare

This release includes a number of bug fixes and improvements to the behavior of locate_credentials() (added in v0.3.2), including better checks on EC2 instances.

Maintenance Release

28 Apr 13:18
Compare
Choose a tag to compare

This is a patch release with a few bug fixes:

  • Modified read_credentials() to allow key-value pairs of any form: KEY=VALUE, KEY = VALUE, KEY= VALUE, KEY =VALUE. (#15, h/t David Severski)
  • Corrected the default timestamp format in signature_v2_auth().
  • read_credentials() now looks for the credentials file in a more reasonable location on Windows (#12/#13, h/t user:kadrach)
  • roxygenized the documentation (and reorganized the source files slightly). (#9)

v0.2.6

06 Dec 15:45
Compare
Choose a tag to compare

This is a patch release that provides provisional support for temporary security tokens ("session tokens"), thus broadening support for IAM and STS credentials. Existing code will continue to work, but support for session tokens will be cascaded through other cloudyr API clients accordingly (meaning it is not widely supported yet).

There are also some minor changes to some default arguments to correct unintended behavior. These should not affect any previously correct signing code.