The severity of a log message, in rising order.

The interface for any logging function. Takes log level and a log message, and can perform an arbitrary IO action.

The default logger defaultLog minLevel, which prints log messages above level minLevel to stderr.

The configuration for an AWS request. You can use multiple configurations in parallel, even over the same HTTP connection manager.

The default configuration, with credentials loaded from environment variable or configuration file (see loadCredentialsDefault).

Debug configuration, which logs much more verbosely.

Run an AWS transaction, with HTTP manager and metadata wrapped in a Response.

All errors are caught and wrapped in the Response value.

Metadata is logged at level Info.

Usage (with existing Manager): resp <- aws cfg serviceCfg manager request

Run an AWS transaction, with HTTP manager and metadata returned in an IORef.

Errors are not caught, and need to be handled with exception handlers.

Metadata is not logged.

Usage (with existing Manager): ref <- newIORef mempty; resp <- awsRef cfg serviceCfg manager request

Run an AWS transaction, with HTTP manager and without metadata.

Metadata is logged at level Info.

Usage (with existing Manager): resp <- aws cfg serviceCfg manager request

Run an AWS transaction, without HTTP manager and without metadata.

Metadata is logged at level Info.

Note that this is potentially less efficient than using aws, because HTTP connections cannot be re-used.

Usage: resp <- simpleAws cfg serviceCfg request

Run an AWS transaction, without enforcing that response and request type form a valid transaction pair.

This is especially useful for debugging and development, you should not have to use it in production.

All errors are caught and wrapped in the Response value.

Metadata is wrapped in the Response, and also logged at level Info.

Run an AWS transaction, without enforcing that response and request type form a valid transaction pair.

This is especially useful for debugging and development, you should not have to use it in production.

Errors are not caught, and need to be handled with exception handlers.

Metadata is put in the IORef, but not logged.

Run a URI-only AWS transaction. Returns a URI that can be sent anywhere. Does not work with all requests.

Usage: uri <- awsUri cfg request

A full HTTP response parser. Takes HTTP status, response headers, and response body.

A response with metadata. Can also contain an error response, or an internal error, via Attempt.

Response forms a Writer-like monad.

Read a response result (if it's a success response, fail otherwise).

Read a response result (if it's a success response, fail otherwise). In MonadIO.

Metadata associated with a response. Typically there is one metadata type for each AWS service.

Class for responses that are fully loaded into memory

An error that occurred during XML parsing / validation.

An error that occurred during header parsing / validation.

An error that occurred during form parsing / validation.

Additional information, like API endpoints and service-specific preferences.

Default configuration for a specific service.

Tag type for normal queries.

Tag type for URI-only queries.

Whether to restrict the signature validity with a plain timestamp, or with explicit expiration (absolute or relative).

Associates a request type and a response type in a bi-directional way.

This allows the type-checker to infer the response type when given the request type and vice versa.

Note that the actual request generation and response parsing resides in SignQuery and ResponseConsumer respectively.