Is your feature request related to a problem or challenge? Please describe what you are trying to do.
Currently we obtain credentials for a request once and use these to drive an operation to completion. This works, however, puts an upper bound on how long we can retry until the credentials are no longer valid
Describe the solution you'd like
We should re-authorize requests on retry. The type machinery to enable this might end up being a touch arcane, especially because of the need to support things like S3 express which have different authorization processes depending on the API methid, but I'd hope this could be encapsulated neatly.
Describe alternatives you've considered
Additional context
6625 proposes lowering the min ttl which in turn will lower the maximum retry duration
Is your feature request related to a problem or challenge? Please describe what you are trying to do.
Currently we obtain credentials for a request once and use these to drive an operation to completion. This works, however, puts an upper bound on how long we can retry until the credentials are no longer valid
Describe the solution you'd like
We should re-authorize requests on retry. The type machinery to enable this might end up being a touch arcane, especially because of the need to support things like S3 express which have different authorization processes depending on the API methid, but I'd hope this could be encapsulated neatly.
Describe alternatives you've considered
Additional context
6625 proposes lowering the min ttl which in turn will lower the maximum retry duration