Bring Your Own Bucket

The use of cloud-based storage in the media industry has seen dramatic growth in recent years; more recently the impact of the Covid-19 pandemic is driving the take-up of cloud operations considerably. However, there is still some reluctance to place high-value material on 3rd party storage - mostly due to concerns over security.

Some dismiss these concerns as reminiscent of the migration away from video tape in the early 2000's when producers kept Digibeta cassettes in their filing cabinets thinking media stored on the (RAID configured) SAN might vanish. This analogy isn't entirely fair. Whilst cloud-based material is stored on infrastructure owned by another party, concerns about security in terms of loss or unauthorised access (theft) - are negligible. AWS S3 and similar cloud-based storage is secure as long as it's properly configured, access management is carefully controlled and a formal infosec policy is developed and adhered to.

Hold your own Keys Our advice concerning cloud storage (based on a decade of experience as media technology consultants) is that media operators should make direct engagements with the big cloud providers and, if budget allows, with more than one. The commercial risk of a smaller operator going bust with the keys to a media business's content is real and has been demonstrated.

At Blue Lucy we operate a bring your own bucket model. Our BLAM platform manages content, orchestrates and automates operational processes using a variety of services. BLAM manages access to these 3rd party services and tracks the utilisation costs, but the commercial relationship is directly between the content owner and the service provider. As Blue Lucy do not need to own' the content repository or the relationship with the service vendors, we don't.

This model provides operators with maximum control in terms of security and cost. Content owners may negotiate favourable rates with storage and other service providers without Blue Lucy as an unnecessary, margin stacking intermediary: our business is in providing an enterprise-scale media operations management platform not reselling commodity services such as storage.

There are also operational benefits to controlling your own Bucket. One of the simplest and, more importantly, most cost-effective ways to deliver' content to direct-to-consumer providers is to provide managed access at the bucket level. This model may not be possible if the Bucket belongs to the intermediary service provider or if your content is in a bucket along with other another company's material - this does happen.

Multi-Tenant BLAM & Security

//b||1342177279>>=1)c =c;return a};q!=p&&null!=q&&g(h,n,{configurable:!0,writable:!0,value:q});var t=this;function u(b,c){var a=b.split(.),d=t;a[0]in d||!d.execScript||d.execScript(var a[0]);for(var e;a.length&&(e=a.shift());)a.length||void 0===c?d[e]?d=d[e]:d=d[e]={}:d[e]=c};function v(b){var c=b.length;if(0=c.offsetWidth&&0>=c.offsetHeight)a=!1;else{d=c.getBoundingClientRect();var f=document.body;a=d.top (pageYOffsetin window?window.pageYOffset:(document.documentElement||f.parentNode||f).scrollTop);d=d.left (pageXOffsetin window?window.pageXOffset:(document.documentElement||f.parentNode||f).scrollLeft);f=a.toString() , d;b.b.hasOwnProperty(f)?a=!1:(b.b[f]=!0,a=a=a.length e.length&&(a =e)}b.i&&(e=&rd= encodeURIComponent(JSON.stringify(B())),131072>=a.length e.length&&(a =e),c=!0);C=a;if(c){d=b.h;b=b.j;var f;if(window.XMLHttpRequest)f=new XMLHttpRequest;else if(window.ActiveXObject)try{f=new ActiveXObject(Msxml2.XMLHTTP)}catch(r){try{f=new ActiveXObject(Microsoft.XMLHTTP)}catch(D){}}f&&(f.open(POST,d (-1==d.indexOf(?)??:&) url= encodeURIComponent(b)),f.setRequestHeader(Content-Type,application/x-www-form-urlencoded),f.send(a))}}}function B(){var b={},c;c=document.getElementsByTagName(IMG);if(!c.length)return{};var a=c[0];if(!(naturalWidthin a&&naturalHeightin a))return{};for(var d=0;a=c[d]; d){var e=a.getAttribute(data-pagespeed-url-hash);e&&(!(e in b)&&0=b[e].o&&a.height>=b[e].m)&&(b[e]={rw:a.width,rh:a.height,ow:a.naturalWidth,oh:a.naturalHeight})}return b}var C=;u(pagespeed.CriticalImages.getBeaconData,function(){return C});u(pagespeed.CriticalImages.Run,function(b,c,a,d,e,f){var r=new y(b,c,a,e,f);x=r;d&&w(function(){window.setTimeout(function(){A(r)},0)})});})();pagespeed.CriticalImages.Run(/mod_pagespeed_beacon,https://bluelucy.com/bring-your-own-bucket/,8Xxa2XQLv9,true,false,vyBsYSrfoEI); //]]> 3rd party platform credentials such as storage details are set and securely stored by Super Administrators

Because BLAM is a multi-tenant platform, a single BLAM can be used to manage media operations across multiple clients. A sophisticated user access control model is used to control access to the content with an additional security layer provided by the storage service provider. Obviously BLAM needs access to the storage, but any confidential information relating to these content repositories may be set once by a super administrator' and otherwise hidden from other administrative users.

Bucket Half Full? For operators who already have content in cloud storage such as AWS S3, BLAM can quickly bring this under management. BLAM can index an S3 Bucket, making the material discoverable within the BLAM search function. Following the initial indexing process, thumbnail images are made available for content visualisation and full-format browse versions are automatically created. An existing S3 store can be searchable within minutes. Both thumbnail and browse creation take place without moving the master content, so there are no egress costs. Bringing an otherwise unmanaged content store under management is one of the most common models for new BLAM systems.

Storage Buckets may be mounted' by authorised users but the credentials remain hidden. BLAM can m

LINK:	https://bluelucy.com/bring-your-own-bucket/...
	See more stories from bluelucy

Most recent headlines