Content Management

Check the following:

• Verify your storage account connection is active in MK.IO
• Ensure the SAS token has read permissions and hasn't expired
• Confirm the container or bucket name matches exactly (case-sensitive)
• Check that files are in a supported format (MP4, MXF, etc.)
• Try refreshing the asset indexing manually from the asset details page

To update storage keys safely:

1. Generate a new SAS token in your Azure Storage or S3 console
2. Navigate to Manage Storage Tokens in MK.IO
3. Update the token for your storage account
4. Test connectivity by uploading a test file
5. Once verified, revoke the old token from your storage provider

💡 Tip: Set up monitoring alerts 30 days before SAS expiration.

Yes, MK.IO supports AWS S3 and S3-compatible storage providers (MinIO, DigitalOcean Spaces, etc.). When configuring, ensure:

• Your credentials have appropriate read/write permissions
• You configure the correct endpoint URL if using non-AWS S3
• Bucket naming follows S3 conventions (lowercase, no special chars)

If your SAS token expires, MK.IO will lose access to your storage and you'll see authentication errors. Existing streaming URLs will continue to work if the storage is publicly accessible, but you won't be able to:

• Upload new files
• Import new assets
• Generate new streaming locators

Update the token immediately in Manage Storage Tokens to restore full functionality.

For large-scale migrations (500+ assets), use the Bulk Import from AMS tool:

• It processes multiple assets in parallel for faster migration
• Generates a detailed import report showing success/failure status
• Preserves all existing streaming locators and policies
• No re-encoding required - references files in place

For even faster migration, contact support about the MK.IO AMS Explorer integration for enterprise customers.