If a tool or app gets "access denied" or authentication errors talking to Object Storage, check these.
- Right keys. Object storage uses S3 access keys, not your console password or an Application Credential. Create a pair with the S3/EC2 credentials option and use the access key and secret exactly, with no extra spaces.
- Right endpoint. Point your tool at the region's endpoint, for example
https://s3.nbo.gewapecloud.comfor Nairobi. Using the wrong region's endpoint gives permission or not-found errors. - Right bucket and permissions. Confirm the container (bucket) name is correct and that your keys belong to the same project that owns it. To serve a file publicly, the object must be set to public read; otherwise anonymous requests are denied.
- Path style. Some older S3 tools need "path-style" addressing. If bucket-in-hostname requests fail, switch the tool to path-style.
For the developer-level detail and code examples, see the developer documentation at developers.gewape.cloud.