MediaLab supports integration with S3-compatible storage and Azure Blob storage. Most problems arise from misconfigured cloud connections, incorrect credentials, or conflicts with the archiving add-on.

Cloud Connection Misconfiguration

• Go to Settings → Cloud Storage → Cloud Connections.
• Verify the protocol is correct (S3 vs. Azure).
• Check the hostname or endpoint URL matches your storage provider.
• Ensure the cloud connection is linked to the correct Pull/Push profile or Cloud Container.

Wrong Keys, Buckets, or Containers

• For S3 storage, confirm:
  • Bucket name is correct and matches your storage account.
  • Account key and secret are valid.
• For Azure Blob storage, confirm:
  • Storage account name and container name are correct.
  • Access key is valid and has the right permissions.
• Typos in these fields are one of the most common causes of failed uploads or missing files.

Archiving Add-On Behavior

• When the Archiving add-on is enabled, files moved to the Archive folder may be redirected to special archive-tier storage.
• This can cause files to appear unavailable in their original container.
• If your Lab uses archiving, check whether the file has been moved to archive storage instead of the active container.

Best Practices

• Always test connection credentials before linking them to production workflows.
• Keep API keys secure and rotate them regularly.
• Document which containers/buckets are assigned to which formats to avoid confusion.
• Contact MediaLab support if you suspect archiving behavior is overriding your storage settings.