The problem was in defining the profile as "default". When I removed the profile parameter, the error disappeared.
When using the latest version, 3.67.8, the following error occurred:
AWS HTTP error: Client error: `PUT https: // some-url` resulted in a` 403 Forbidden`
Anyway, in my case, and in both versions, omitting the profile parameter was the solution.