## TL;DR

Generate customer secret keys under Identity and Security, Users, Customer Secret Keys, and use those as the S3 credentials. Build the endpoint with your tenancy namespace and the bucket's exact region.

## Steps

1. Generate customer secret keys under Identity and Security, Users, Customer Secret Keys, and use those as the S3 credentials. Build the endpoint with your tenancy namespace and the bucket's exact region. When auth fails, check the key type first and the namespace second, before suspecting IAM policies.

## When to use

You are seeing this: Build the endpoint with your tenancy namespace and the bucket's exact region. Use this skill when you run into "Oracle Object Storage S3 needs customer secret keys and a namespace endpoint".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
