Skip to main content

​
What this video covers

This video shows how to go to Settings → Storage, click Add Storage, and register an S3-compatible bucket so a Space has somewhere to store media.

​
Good to know

This screen is admin-only and entitlement-gated — you’ll only see it if your role and organization plan grant access.
The Storage Type list only shows what your deployment supports. For AWS S3, you can authenticate with an IAM Role (Role ARN, using a read-only External ID and Account ID to set up trust) or with an access key and secret key. Generic S3 and Backblaze S3 are configured with an endpoint plus access key and secret key.
Store names need to be 3–63 characters — letters, numbers, spaces, underscores, or hyphens, starting and ending with a letter or number. Once a store is created, its type and name are locked; everything else can still be edited.
After adding (or editing) a store, use Check Permissions — UP will verify the stored credentials and show a toast confirming success or explaining the failure.
A named path inside an existing store — handy for organizing content without registering a whole new bucket. Add one from a store’s row menu with Add Sub Storage; sub-storages can be edited or deleted independently of their parent.
Setting up an AWS S3 connection via IAM Role requires creating a role on the AWS side first — see the related documentation below before you start the video’s IAM Role path.

​
Next step

With storage registered, create the Space that will use it — continue to Adding Spaces.

Storage

Full reference for viewing, adding, editing, and deleting storage locations.

Settings — AWS S3 Roles

How to set up the AWS-side IAM Role that UP’s S3 connection trusts.