Updating Azure SAS Token for Asset Storage
You have created a storage account in MK/IO by linking your Azure blob storage, linked a container and processed assets. However once the SAS token expires to the storage account, these assets will not be accessible until you edit/update the Storage Account with the new SAS Token.
It is important to keep up on your SAS tokens to ensure that you always have a valid one configured in MK/IO. In the MK/IO API documentation this is labeled as a Storage Credential. You will need to create a new storage credential mapped to your storage_id defined and described here: Create Storage Credential (mk.io)
SAS Token management is the responsibility of the user of MK/IO. As a user you will need to make sure to add and remove SAS tokens based on your requirements. It is recommended to delete all expired SAS Tokens as they expire.
Related Articles
How to add storage account in MK.IO
In this article, we will describe the steps to follow when you need to add the storage account, hosting all your AMS assets, in MK.IO. 2 main steps will happen: 1. Get your Storage Account access information: Follow the Step1 instructions of this ...How to use MK.IO APIs - step by step
Update December 2024: Note that https://docs.mk.io/docs/api-tokens describes the steps to manage personal tokens when using MK.IO APIs ...How to migrate from Azure Media Services to MK.IO
How to migrate all your content from AMS into MK.IO using MK.IO bulk migration tool
In this article we will describe in detail the process to migrate all your assets, asset filters, streaming locators, content key policies, streaming endpoints from AMS into MK.IO. The idea is that if today you have a playback URL in the following ...How to use DRM to playback MK.IO assets encrypted
Intro Currently, MK.IO solution supports only MediaKind's DRM solution as the unique provider of DRM encryption keys. External 3PP Key Management System solutions will be considered. In MK.IO there are the following groups of encryptions: 1. ...