Details
-
Improvement
-
Resolution: Done
-
Major
-
None
-
6.6.0
-
None
Description
When we are interfacing with AWS S3 cbbackupmgr should gracefully terminate with a useful error message describing why the backup failed. Some example cases we should handle correctly are:
1) The S3 bucket doesn't exist
2) The user doesn't have permissions to read/write to the specified bucket
3) We failed to download an object e.g. if it has been deleted by the time we try to download it
4) We fail to upload an object because of connection/permission issues