Open navigation

Introduction to the Media Delivery Cloud (MDC)


Introduction

If you are using the Canto DAM system and want to publish images worldwide or use them in another integration such as a CMS or PIM then Canto's Media Deliver Cloud (MDC) is offering great scalability by employing a Content Delivery Network (CDN) with delivery nodes in all parts of the world. It also allows you to easily modify images on the fly simply by using different parameters in the URL (learn more about this topic). Since the base URL always remains the same when embedding MDC links, no cross-site forwarding is used which makes it a great fit for e-Commerce systems and Google shops


How does it work

MDC creates a so-called Master Image from the original asset in Canto. The size of the Master
Image can be configured when setting up MDC, by default, it's 2048 pixels.
Using this Master Image, all desired renditions are created as per requested operation parameter.
In other words, the original asset will not be used anymore once the Master Image has been
created. For MDC purposes, the Master Image is the new source for all renditions.
The great advantage of the MDC is that modifying an image is easy and quick and only requires
some minor change in the URL that is used to call the rendition. You don't need to log in to Canto,
everything can be achieved by simply changing the URL.
As an input format, the MDC supports all assets that are supported within Canto.


Requirements for Canto MDC setup

The following aspects are required before using Canto MDC:

  1. You need own an Amazon Web Services (AWS) account.
  2. For the one-time setup of MDC, Canto needs temporary access to your AWS account. This can be done in two ways:
    1. Either you provides Canto with the login credentials of your AWS root user
    2. Or you set up an online meeting where we guide you – using his AWS root user – through the setup process.
  3. You need to create an API key in Canto’s backend with the option Support Client Credentials Mode enabled.
    Furthermore, Canto needs the App ID as well as the App Secret from that API key. Alternatively, Canto can take over this task if we have admin access to your Canto account.
  4. Decide on the size of the Master Image.
    Note: The larger the Master Image size, the longer it takes to generate. To increase speed and performance, try to keep the Master Image size as little as possible.
  5. You have to decide which asset within your Canto account should be used as a fallback image. Canto needs the asset’s content ID when configuring the fallback image in AWS.

When all requirements are met, it typically takes three working days to set up Canto MDC.

 

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.