aws package:aws

Amazon Web Services (AWS) for Haskell Bindings for Amazon Web Services (AWS), with the aim of supporting all AWS services. To see a high level overview of the library, see the README at https://github.com/aristidb/aws/blob/master/README.md.
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 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 more flexible version of awsIteratedList that uses a user-supplied run function. Useful for embedding AWS functionality within application specific monadic contexts.
A more flexible version of awsIteratedSource that uses a user-supplied run function. Useful for embedding AWS functionality within application specific monadic contexts.
A "true"/"false" boolean as requested by some services.
"false"
"true"
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 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