S3 backend should handle rate limiting #82
Description
If a rate-limiting message is received from an AWS API, handle it gracefully by waiting and queueing/retrying requests.
Additionally, potentially introduce artificial waits between API calls and/or batch requests to help avoid throttling. CloudFront invalidations especially should be debounced and sent as batched requests rather than occurring after every S3 modification.