Skip to content
More support
Contact us
  • There are no suggestions because the search field is empty.

Connecting Mimir to Impossible Cloud Storage

This article explains how to configure Impossible Cloud Storage as an S3 storage location in Mimir, using access keys for authentication.

Mimir is a cloud-based media asset management and collaboration platform from Mjoll, used by broadcasters, media houses, and production companies for ingest, archiving, and production asset management. It uses AI services for automatic metadata logging, transcription, and translation, and integrates with editing tools such as Adobe Premiere Pro.

Mimir stores media assets in S3 buckets, which can be hosted on Impossible Cloud Storage.

Prerequisites

  • An Impossible Cloud Storage account with access to the Storage Console
  • A Mimir account with administrator-level permission

Mimir supports connecting to Impossible Cloud Storage as an Upload Location (where assets land after upload through Mimir) or as an Ingest Storage Location (where Mimir scans for existing files to bring into the system). This article covers both, with the Upload Location as the primary path.

Step 1: Create a bucket in the Impossible Cloud Storage Console

  1. Log in to the Impossible Cloud Storage Console.
  2. Create a new bucket and select a region. Choosing a region close to your Mimir deployment reduces latency.
  3. Optionally, enable Versioning on the bucket.

Versioning is not required for the integration, but Mimir recommends it because it results in a more comprehensive backup: objects Mimir deletes remain recoverable as previous versions. Note that retained versions continue to count towards your stored capacity until you remove them.

Step 2: Start the upload location setup in Mimir

Mimir generates the permission policy inside the location dialog, using the bucket name you enter. Start the location setup first so you can copy the policy, then leave the dialog open while you create the credentials.

  1. In Mimir, go to Mimir System Settings > Storages and create a new upload location.
  2. Select AWS S3 Bucket as the location type.
  3. Enter your bucket name from Step 1, and a path prefix if you want to keep Mimir's uploads inside a specific folder. Mimir inserts these into the generated policy; until you enter them it shows a placeholder such as your-upload-bucket.
  4. Open the Permission policy tab and copy the policy. It lists the S3 actions Mimir needs on your bucket.

Step 3: Create a dedicated IAM user and access key

Mimir connects to Impossible Cloud Storage using an access key and secret key rather than an assumed IAM role. Create a dedicated IAM user for Mimir and grant it only the permissions from the copied policy, rather than reusing an existing user or key.

  1. In the Impossible Cloud Storage Console, create a new IAM user for Mimir.
  2. Assign the policy you copied in Step 2 to that user, so its permissions are limited to the bucket and actions Mimir requires.
  3. Create an access key and secret key for the user.

Step 4: Complete the location setup in Mimir

  1. Return to the location dialog in Mimir.
  2. Enter the endpoint for your bucket's region, for example https://eu-central-2.storage.impossibleapi.net for eu-central-2.
  3. Enter the access key and secret key from Step 3.
  4. Save the storage location.

Mimir displays a set of CORS rules for browser-based uploads. CORS configuration on Impossible Cloud Storage buckets cannot be set from the Storage Console. If your setup requires the CORS rules from Mimir, copy them and apply them to your bucket with the AWS CLI. See Using Impossible Cloud with AWS CLI for setting up the CLI profile and endpoint.

Step 4: Configuring an Ingest Storage Location instead

If you want Mimir to ingest files from an existing bucket rather than store newly uploaded assets, configure an Ingest Storage Location instead:

  1. In Mimir, go to Mimir System Settings > Ingest Config.
  2. Create a new ingest configuration and select AWS S3 as the storage provider.
  3. Enter the same bucket name, endpoint, path prefix, and access key / secret key as described in Step 3.
  4. Run a scan to verify the connection and confirm Mimir can list and read objects in the bucket.

Files in an ingest location are not removed from the bucket when Mimir ingests them.

Impossible Cloud Storage does not currently support S3 bucket notifications. Mimir's notification-based ingest trigger, which relies on the bucket sending an event when a new file arrives, is not available for Impossible Cloud Storage locations. Configure Mimir to scan the ingest location on a schedule, or trigger scans manually, instead of relying on automatic notification-based ingest.

Related documentation