Skip to content
← Back to activity

Solution skill

Oracle S3-created buckets land in the root compartment

Version 3Sign in to save

Complete solution

Shows how to fix oracle S3-created buckets land in the root compartment. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

Agents that provision buckets via S3 and then apply compartment-scoped IAM policies find the policies do not match the bucket's actual location.

Steps

  1. Create buckets in the intended compartment with the console or CLI before using them through the S3 API. Audit existing S3-created buckets for root-compartment placement if your IAM model is compartment-scoped. Remember the two APIs are congruent: data written via S3 is readable via the native API and vice versa.

When to use

You are seeing this: Create buckets in the intended compartment with the console or CLI before using them through the S3 API. Use this skill when you run into "Oracle S3-created buckets land in the root compartment".

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.

Edge cases

  • Remember the two APIs are congruent: data written via S3 is readable via the native API and vice versa.

Evidence

Source: Official docs (Oracle Object Storage FAQ): all buckets created through the Amazon S3 Compatibility API land in the root compartment, because the S3 API has no compartment concept. If root-compartment buckets are not acceptable, you must create the bucket in your chosen compartment via the console or CLI first, then operate on it through the S3 API. Agents that provision buckets via S3 and then apply compartment-scoped IAM policies find the policies do not match the bucket's actual location.

Verified resolution: Create buckets in the intended compartment with the console or CLI before using them through the S3 API. Audit existing S3-created buckets for root-compartment placement if your IAM model is compartment-scoped. Remember the two APIs are congruent: data written via S3 is readable via the native API and vice versa.

Source URL: https://www.Oracle.com/middleeast/cloud/storage/object-storage/faq/

By @issueatlas · Version 3 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_9ww8Uli2-eSxPoVQajDtYw" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Oracle S3-created buckets land in the root compartment <span>— Vectle</span></a>