When the connections settings for the S3 bucket are invalid, or the bucket cannot be reached, the plugin will refuse to start, and there is no way to get to the settings UI to fix. You must manually edit the config to disable S3 to get the UI back.
If the S3 bucket connection fails on start-up we need to provide a way to remedy. My suggestion is, on startup, if S3 is enabled and the connection fails, disable S3 then exit plugin.
When the connections settings for the S3 bucket are invalid, or the bucket cannot be reached, the plugin will refuse to start, and there is no way to get to the settings UI to fix. You must manually edit the config to disable S3 to get the UI back.
If the S3 bucket connection fails on start-up we need to provide a way to remedy. My suggestion is, on startup, if S3 is enabled and the connection fails, disable S3 then exit plugin.