The names of procedures and structs generally do not have special prefixes to “group” them. Instead, use the prefix-in option for require if you prefer a prefix (or need one to avoid a name collision).
For example if you want the aws/sns procedures to have an sns- prefix, so that create-topic is renamed to sns-create-topic:
|(require aws/keys)||package: aws|
file : path? = (build-path(find-system-path 'home-dir) ".aws-keys")
By default this file is ~/.aws-keys. You probably want to chmod the permissions of this file carefully.
If your code will run on an EC2 instance, instead consider using use-iam-ec2-credentials!.
Added in version 1.10 of package aws.
When your code is running on an EC2 instance, instead of you supplying credentials in a configuration file (like ~/.aws-keys) or in environment variables, it is possible to obtain credentials from EC2 instance meta-data. This simplifies configuration and is more secure.
For more information how to configure this, see
IAM Roles for Amazon EC2. Step five of those instructions —
Credentials are initially obtained —
|(require aws/sigv4)||package: aws|
Added in version 1.12 of package aws.
Given a dict? of HTTP request headers, add one or more headers required by AWS for authorization:
Authorization: The value is calculated using AWS version 4 request signing.
X-Amz-Security-Token: The value is the token returned along with temporary credentials from EC2 instance data (this applies only if you are using use-iam-ec2-credentials!).
Various functions in this library that make requests, use this
function. As a result, you will probably not need to use it directly
|(require aws/exn)||package: aws|
(struct exn:fail:aws (http-code http-message aws-code aws-message) #:extra-constructor-name make-exn:fail:aws) http-code : exact-positive-integer? http-message : string? aws-code : string? aws-message : string?
(header&response->exn:fail:aws headers body ccm) → exn:fail:aws? headers : string? body : (or/c bytes? xexpr?) ccm : continuation-mark-set?
(check-response in headers)
→ (or/c string? (raise/c exn:fail:aws?)) in : input-port? headers : string?
Otherwise, read the XML response body from in and use the information to construct and raise exn:fail:aws.
Note: This does not close the input port in before raising an
exception. It assumes you are using call/requests,
call/input-request, or call/output-request from the
http/request library (or using dynamic-wind or other
exception handling, or a custodian—
This can be faster, especially for many small requests in a row.
In the following example, the first list-buckets request will leave the connection open for 30 seconds. As a result, the second list-buckets request will reuse the same connection. After another 30 seconds, the connection will be closed automatically.
(require http/request aws/s3) (parameterize ([current-pool-timeout 30]) (list-buckets) (list-buckets))