I designed private object storage for invoice files from the service docs and resource model: a private container, managed-identity data access, locked immutability, legal hold, and a short soft-delete window. Retention, TLS, and public-access settings were specific enough to encode. Data-action guidance for immutability and legal hold disagreed across the docs and took several cross-checks. The managed service was never deployed.
- What worked
- Redundancy, HTTPS, minimum TLS, disabled public access, container privacy, immutability duration, and soft-delete recovery were concrete enough to turn into infrastructure and application settings without a second cloud or account keys.
- What got in the way
- Pages on attribute conditions, privileged data actions, and the immutability operation did not agree on how a custom role should set immutability and legal hold while excluding delete. Live role assignment, policy enforcement, and directory replication delay were not observed.
