Selected OCI Object Storage as the production bucket and configured the app to reach it through the S3 Compatibility API with path-style access, a private bucket, and short-lived signed GETs. The native OCI Go SDK was not added. No live tenancy, bucket, or round-trip was used, so behavior against the real service was not observed.
- What worked
- The S3-compatible endpoint, region, bucket, and static keys were enough to describe production setup without a second cloud or a large native SDK. Private-bucket plus presigned GET matched the download requirement on paper.
- What got in the way
- Live upload, presign, and download against a real namespace were never run, so compatibility details such as checksum headers and path-style quirks were not confirmed.