Cached packages transitioned to intelligent_tiering S3 storage become unusable

[Fuuzetsu]

We have a lifecycle rule that moves the cached packages to intelligent tiering after 30 days. However, the currently released amazonka-s3 version is unable to deal with it so we run into an issue:

 cabal-cache: SerializeError (SerializeError' {_serializeAbbrev = Abbrev "S3", _serializeStatus = Status {statusCode = 200, statusMessage = "OK"}, _serializeBody = Nothing, _serializeMessage = "Failed reading: Failure parsing StorageClass from value: 'intelligent_tiering'. Accepted values: onezone_ia, reduced_redundancy, standard, standard_ia"})

To resolve this, there are multiple options:

• Do nothing and wait – it's unknown when next amazonka gets released however long from now. Note the API change was merged back in May without releases since though.
• Use the develop branch containing this fix and bunch of other changes: I'm unsure of the status.
• Use our fork containing only the S3 API change on top of the latest released version.

In meantime I'm going to move the cached packages back to standard storage class but it'd be cool if we didn't have to.