amazonka

amazonka copied to clipboard

Currently, when creating a new S3 Bucket via `CreateBucket`, if no locaiton constraint or configuration is specified, then an empty XML element is sent. This results in a validation error,...

brendanhay

S3 throttling causes transport errors not service errors

4

S3 throttles differently to other services, in that (unless there is special code to handle 100 CONTINUE) it tends to accept connections then terminate them at some random point for...

nhibberd

possible to extract response status generically?

5

One currently needs to extract status code in the following fashion: ``` r

ababkin

Nullary response types don't get assigned a status code

5

brendanhay

Apparent leak when sending repeated requests to Glacier

6

To be able to upload arbitrarily large archives to AWS Glacier, I wrapped its multipart upload in a Conduit of ByteStrings. However, it still uses more memory at once than...

LeifW

Exponential backoff for DynamoDB BatchGet and BatchWrite

4

BatchGet and BatchWrite both return an UnprocessedItems (see http://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_BatchWriteItem.html). The documentation states that if DynamoDB returns any unprocessed items, the request should be retried with just the unprocessed items using...

wuzzeb

endOfInput error when calling ListObjects against localstack/moto mock of S3 service

3

I don't know if this is a bug in amazonka or a bug in the emulation of S3 by [localstack](https://github.com/localstack/localstack)/[moto](https://github.com/spulec/moto), so I apologize in advance if this bug is going...

rcook

S3 PutObjectACL is not correctly serializing the Grantee xmlns/xsi type

1

The correct form for serialised `Grantee` should be: ``

brendanhay

Should `Network.AWS.Internal.HTTP.retrier` log an error each time a request fails?

1

This is the current behavior, but it seems a bit severe. I usually try to reserve error-level logging for issues that someone needs to take a look at (generally with...

gridaphobe

amazonka-cloudwatch-logs: GetLogEvents is not paginated

3

The GetLogEvents (https://docs.aws.amazon.com/AmazonCloudWatchLogs/latest/APIReference/API_GetLogEvents.html) API call can take nextToken as usual, but the response is a bit unusual in that it returns both a nextBackwardToken and nextForwardToken. I think that's what...

phyrex1an