Changelog
Source:NEWS.md
aws.signature 0.6.2
CRAN release: 2026-07-21
- New package maintainer, changes to the aws.signature-package.R function, and updated roxygen2 version
aws.signature 0.6.1
- Add support for assuming roles from web identities (#62)
aws.signature 0.6.0
CRAN release: 2020-06-01
- Allow connection to empty regions (h/t @namelessjon, @lawremi)
- Prioritize the
profileargument over env vars inlocate_credentials() - Add argument for computing signed body as part of the signature (#59)
aws.signature 0.5.2
CRAN release: 2019-08-08
- Fix failure to install package with partial credentials file (h/t @stelsemeyer, #39)
- Improve parsing of config files
aws.signature 0.5.1
- Fix additional output when multiple profiles exist (@muschellij2, #42)
aws.signature 0.5.0
CRAN release: 2019-05-08
- 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 internalsignature_v4()function. (#33) -
signature_v4_auth()andsignature_v2_auth()gain aforce_credentialsargument. Ifforce_credentials = TRUE, user-supplied values are used and no call tolocate_credentials()is made. (#33)
aws.signature 0.4.3
- Incorporated standard environment variables
AWS_SHARED_CREDENTIALS_FILEandAWS_PROFILEinto code as appropriate and tweakedlocate_credentials()accordingly. -
signature_v4_auth()andsignature_v2_auth()now returns all inputs to facilitate using the return value in constructing an HTTP request. - Updated documentation.
aws.signature 0.4.0
-
read_credentials()now trims excess whitespace from profile names. (#22, h/t Paul Ingles) -
locate_credentials()returnsregion = default_regioneven when no other credentials are found. -
canonical_request()now correctly trims whitespace. - The test suite was updated substantially, though not all tests run on CRAN.
aws.signature 0.3.7
- 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. (https://github.com/cloudyr/aws.s3/pull/184, h/t Dan Tenenbaum) - The
profileargument ofuse_credentials()now defaults toSys.getenv("AWS_PROFILE", "default")for consistency with other AWS client libraries.
aws.signature 0.3.6
-
locate_credentials()now attempts to look in instance metadata for a region, when called from an EC2 instance. (see https://github.com/cloudyr/aws.s3/issues/151) - The set of fall backs for values of
regionhave been standardized and documented forlocate_credentials(). - Updated documentation to describe the need for aws.ec2metadata on EC2 instances.
aws.signature 0.3.5
CRAN release: 2017-07-01
-
signature_v4_auth()andsignature_v2_auth()now both return aRegionvalue in their response list, as identified bylocate_credentials().
aws.signature 0.3.4
- Fixed a bug related to extracting credentials from environment variables. (https://github.com/cloudyr/aws.s3/issues/142, https://github.com/cloudyr/aws.s3/issues/143)
- Fixed a bug related to extracting credentials from EC2 instance metadata (https://github.com/cloudyr/aws.s3/issues/144, h/t Daniele Rapati, Will Bowditch)
- Bumped aws.ec2metadata suggestion to 0.1.2.
aws.signature 0.3.3
- Fixed a bug in
locate_credentials()caused by trying to retrieve EC2 instance metadata from a non-EC2 machine on which the aws.ec2metadata package was installed. - Expanded test suite to cover more of
locate_credentials()behavior.
aws.signature 0.3.1
- Changed the precedence of credential sources to: user-supplied values, EC2 instance metadata, environment variables, local credentials file, and global credentials file. (#11)
aws.signature 0.3.0
- Added a
locate_credentials()function to walk through a hierarchy of possible credential locations, beginning with user-supplied values, then environment variables, local then global credentials “.aws/credentials” files, and finally (if applicable) an EC2 role for the currently running instance. (#11)
aws.signature 0.2.9
CRAN release: 2017-04-28
- Modified
read_credentials()to allow key-value pairs of any form:KEY=VALUE,KEY = VALUE,KEY= VALUE,KEY =VALUE. (#15, h/t David Severski)
aws.signature 0.2.8
- Corrected the default timestamp format in
signature_v2_auth().
aws.signature 0.2.7
-
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)
aws.signature 0.2.6
CRAN release: 2016-12-07
- Added support for signing requests (using V4 signatures) with temporary security tokens.
- Modified some default arguments to correct unintended behavior. These should not affect any previously correct signing code.
aws.signature 0.2.5
CRAN release: 2016-08-09
- Added functions
read_credentials()anduse_credentials()to access AWS access credentials stored in.aws/credentialsfiles.
aws.signature 0.2.1
-
canonical_request()now sets C collate order to properly order query argument and header names across platforms.
aws.signature 0.1.4
- Coerce query string arguments to character before passing to
URLencode(). (#5)
aws.signature 0.1.3
- Add standard AWS test suite: http://docs.aws.amazon.com/general/latest/gr/signature-v4-test-suite.html. (#2)
- Expose and set default key, secret, and region values in
signature_v4_auth.
aws.signature 0.1.2
- Fix bug in request body hashing for non-character request bodies (#3).
aws.signature 0.1.0
- Include patched version of
utils::URLencodethat correctly encodes URLs per RFC 3986. - Initial release.