S3 issues

The following information describes some of the S3 issues that you might encountered when you are using IBM Storage Scale.

I/O upload fails with "Could not connect to the endpoint URL."
I/O upload fails because it could not connect to an endpoint URL.
I/O upload fails with “We encountered an internal error. Please try again”.
I/O upload fails because of invalid ID or the multipart upload aborted or completed
I/O upload fails with “The specified key does not exist”.
The CES shared root path is not mounted or unavailable
The CES shared root path is not mounted or unavailable on the CES node or cluster.
Inaccessibility of the CES shared root path
The CES shared root path is rarely changed, except for scenarios where there is no other option, such as disk failure, which makes the CES shared root path inaccessible.
Cannot locate a config.json file
The mms3 config list command could not locate an S3 configuration file.
S3 backup fails
S3 backup fails because of some ongoing configuration file updates.
The S3 configuration is not restored
The S3 configuration cannot be restored, if the S3 configuration is being restored or backup is in progress.
Cannot find the mms3-config.json file in the CES shared root path
The mms3 commands are not run, if the mms3-config.json file is not available.
Cannot recover secret keys if encryption master keys are regenerated
If the master keys get regenerated, then the secret keys cannot be recovered.
Cron job synchronization issue
The CES shared root path is not mounted or unavailable on the CES node or node is unavailable or S3 is not running.
Cronjob setting for bucket notification interval
You can set cronjob timer to receive notifications in the range 1 through 59 minutes.
Cannot recover passwords for connections if encryption master keys are regenerated
If a master key is regenerated, you cannot recover the passwords.
S3 backup does not include certificates
NoSuchKeyExists
If you upload a file with the same name as an existing file in the directory, this error occurs.
AccessDenied
This issue occurs because of wrong ID mappings.
S3 notification events missed
Events missed when node suspends or webhook not reachable.
Duplicate S3 notification events
Duplicate events are generated when webhook is not reachable or crontab is reinitiated from a new node.

Parent topic: Protocol issues