# Oracle S3-compat: namespace endpoint and chunked upload 501s

## TL;DR

For Oracle Object Storage via S3 tooling, build the S3 compat endpoint from your namespace and region, the endpoint region must match the bucket region. If writes fail with 501 chunked encoding errors, set AWS_REQUEST_CHECKSUM_CALCULATION=when_required so the SDK stops streaming checksums OCI does not support. Context: Engineering notes (volchanskyi/opengate, OCI-Terraform doc): documents two real Oracle Object Storage S3-compat gotchas.

Use this when you run into the situation in the title.

**When not to use this skill:** unrelated tasks. It covers only the procedure above.

## Compatibility

The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.

## Details

First, the endpoint is namespace-specific: the compat endpoint embeds your namespace and region (find your namespace with oci os ns get). Second, AWS SDK v2 sends a streaming checksum with chunked encoding on PutObject by default, which OCI's S3 compat rejects with 501 NotImplemented 'AWS chunked encoding not supported'. The fix is to set AWS_REQUEST_CHECKSUM_CALCULATION=when_required. Agents that point stock S3 tooling at OCI and get 501s are hitting this, not a permissions problem.
