Put the campaign assets in the bucket yourself
Upload to production storage from the browser. No cloud console, no access keys, no ticket.
“Hi! Sorry to bother you again — could you upload these 6 hero images to the CDN bucket? The campaign goes live at 9am tomorrow”
What the wait costs
A launch that depends on an engineer being online, and an engineer whose afternoon depends on a launch they are not part of.
In Fenwave
Object Storage›marketing-assets›campaigns/2026-q3›Upload
Capability
Object StorageThis is the use case that shows what an internal developer platform is actually for. A marketing manager needs six images in an S3 bucket. It is not a technical task — it is a permission task, and the only tool available for it was an AWS console with a hundred other services in it. Fenwave gives them a file browser: folders, drag, upload, done. They never see a bucket policy, never receive an access key, and cannot reach any other storage connection. The upload appears in the audit log under their name, which is a stronger control than the shared IAM user the engineer would otherwise have used on their behalf.
How it works
- 01An administrator registers the bucket as a storage connection, once.
- 02Marketing is granted read and create on that connection — not delete.
- 03They sign in to Fenwave with their normal work account.
- 04Open Object Storage, navigate the folders, drag the files in.
- 05The upload is recorded in the audit log under their own name.