We had a triage and said this should be a blocker so it is now but it sounds like s3 is getting disabled/hidden which would remove the need for blocker. I will let dev do that.
Fixes were backported
Verified in 184.108.40.206. I successfully refreshed S3 provider without errors with provided enviroment.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.