Create CDN configurations

You can create a CDN configuration to define upload and delivery settings for your video on demand content, live stream content or for mid-rolls. Once you complete your CDN configurations, you can associate them with your content source.

You can create multiple CDN configurations and associate with a single content source, but only one CDN configuration can be associated with a mid-roll source.

Create a CDN configuration for video on demand content

  1. Sign in to Google Ad Manager.
  2. Click Video and then Content sources and then CDN configurations and then NEW CONFIGURATION

  3. Enter a descriptive name. This name is only displayed in Ad Manager, not externally.
  4. Ensure that "Video on demand content" is selected as the configuration type.
  5. Describe the CDN from which the content will be ingested:

    • Ingest URL prefix: The prefix of the URL of the CDN. This is used to determine which CDN settings should be used for a piece of content.
    • CDN authentication: If you have not configured your CDN to require authentication, select None.


      If your external CDN requires authentication, select the CDN and enter the authentication details:

      • Token authentication: Enable if your CDN requires an authentication key. You also have the option of enabling cookie protection.
      • Media encryption: Enable to define an asset URL.
  6. Configure the details for the default CDN from which the content will be delivered:

    • Name: Upon saving your CDN configuration, Ad Manager assigns a unique name to each delivery setting. This becomes visible only after you save.

    • Delivery URL prefix: The URL prefix for the CDN that will be used to host the content.
    • Security settings: Select Use ingest security settings to apply the same settings as ingest.

      If your CDN is Akamai, token authentication on delivery will not work if cookie protection is disabled.

    • CDN authentication: If you have not configured your CDN to require authentication, select None.


      If your external CDN requires authentication, select the CDN and enter the authentication details:

      • Token authentication: Enable if your CDN requires an authentication key. You also have the option of disabling server-side URL signing and enabling cookie protection.
      • Disable server-side URL signing: If you are using Akamai token authentication, disable server-side URL signing to force the client to generate the authentication signature.
  7. (Optional) Click ADD DELIVERY SETTING (Beta) if you plan to serve the content from more than one CDN, and configure the details for the additional CDN, as outlined in step 6. Learn more
  8. Click SAVE.

Create a CDN configuration for live stream content

  1. Sign in to Google Ad Manager.
  2. Click Video and then Live streams and then CDN configurations and then NEW CONFIGURATION

  3. Enter a descriptive name. This name is only displayed in Ad Manager, not externally.
  4. Ensure that "Live stream content" is selected as the configuration type.
  5. Describe the CDN from which the content will be ingested:

    • Ingest URL prefix: The prefix of the URL of the CDN. This is used to determine which CDN settings should be used for a piece of content.
    • CDN authentication: If you have not configured your CDN to require authentication, select None.


      If your external CDN requires authentication, select the CDN and enter the authentication details:

      • Token authentication: Enable if your CDN requires an authentication key. You also have the option of enabling cookie protection.
  6. Describe the CDN from which the content will be delivered:

    • Delivery URL prefix: The prefix of the URL of the CDN that will be used to host the content that will be delivered.

    • Delivery security settings: Select Use ingest security settings to apply the same settings as ingest.

      If your CDN is Akamai, token authentication on delivery will not work if cookie protection is disabled.

    • CDN authentication: If you have not configured your CDN to require authentication, select None.


      If your external CDN requires authentication, select the CDN and enter the authentication details:

      • Token authentication: Enable if your CDN requires an authentication key. You also have the option of disabling server-side URL signing and enabling cookie protection.
      • Disable server-side URL signing: If you are using Akamai token authentication, disable server-side URL signing to force the client to generate the authentication signature.
  7. Click SAVE.

Create a mid-roll CDN configuration

If your content requires mid-roll ad breaks and you need Ad Manager to condition your content, you must provide SFTP access to your CDN so that Ad Manager can upload video segments after they are split at the ad break points. Create a mid-roll CDN configuration to allow Ad Manager access your content.

  1. Sign in to Google Ad Manager.
  2. Click Video and then Content sources and then CDN configurations and then NEW CONFIGURATION.
  3. Enter a descriptive name. This name is only displayed in Ad Manager, not externally.
  4. Select Mid-roll as the configuration type.
  5. Complete the following mid-roll settings:

    • Upload protocol: Protocol for the uploaded conditioned content. Ad Manager only allows secure (SFTP) connections.
    • Username, private key, and password: Ad Manager only accepts SFTP credentials that use a private key for authentication (either RSA or DSA). You can optionally supply a private key that uses a password.

      Ad Manager cannot use an insecure FTP location and does not support SFTP authentication using a username and password.

      Before you enter your private key, you should test it using an independent SSH or SFTP client. Some examples of these clients are PuTTy or CyberDuck.

      Requirements for entering SSH keys


      • Depending on the type of private key, it needs to begin with the following text:

           -----BEGIN RSA PRIVATE KEY----- or -----BEGIN DSA PRIVATE KEY-----

      • Depending on the type of private key, it needs to end with the following text:

           -----END RSA PRIVATE KEY----- or -----END DSA PRIVATE KEY-----

      • There must be a new line character (\n) where line breaks exist.
       

      Sample key

      -----BEGIN DSA PRIVATE KEY-----\nProc-Type: 4,ENCRYPTED\nDEK-Info: DES-EDE3-CBC,BFF8B97CEFE81031\n\n\nZcYWZ5Sq12m8bFxCGc1f3GYjcJSmrwyLMUzqryPGnbmnURULC19+WVddHzzcJ2D5\ncc/wYKzE5eRO2ZupeGRcaMwG1UYx171ucwfvoE5VfbD6fBAn7bkW+Qik0QdL3/M4\nN2l0LlqiZxBLEQ8bwZvfN9aeOfbpgFufbQw8X9jVk5gNzOucRC2B0Ul9DxfLSvWU\nvgnrlrqijvpLMRDtuGt7X8X1vb/gSIIsdWYl5kny0ULL1sK+ZLUHT6YCLPNxjJsE\nrgPxKRV6Z8TrygbfipZckd0LSEAJltwoIM/1iSeZt9mn4lrz1GF/jO5XeUcFwQWr\nu8emTMvXFbeTXOKmsjhhUsZgNxvMfUd+S2Bus66jb1jTm2jMGbKAtWola98e8C0h\nh4hh8OJU4ZhFyb2/xOqR7P7DKjWIYDTlb1t0EZv4xUE1UFTo4MwCZaOFBJs172ax\nFBWZLYoYF3gBDy2C6/dP5IJfa4G27NHeqU9WYPq5wTct0mqHhzrR2cj6pmRwwjq9\nmME3mDH8X0oMz5I6XHbJ0n5pc49YRXCrq4tP/GXevXh0z/wfzwt3x94oQuH9JwoD\npOT5xNOngA2pKJLuMc+D/g==\n-----END DSA PRIVATE KEY-----\n
    • Hostname: Hostname for the uploaded conditioned content files.
    • Path prefix: Directory to which the conditioned content will be uploaded.
    • Delivery URL prefix: Prefix of the CDN URL that is used to host the content segments.
  6. Click SAVE.
Was this helpful?
How can we improve it?