How AWS Elemental MediaConvert interacts with your Nielsen SID/TIC server in the Amazon Cloud - MediaConvert
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China.

How AWS Elemental MediaConvert interacts with your Nielsen SID/TIC server in the Amazon Cloud

There are four major parts of the system that you set up by following instructions from Nielsen:

  • Transfer your Nielsen metadata .zip file. MediaConvert writes this file to the Amazon S3 bucket that you create. You provide this bucket URL for the setting Metadata destination (metadataDestination) when you set up your job.

    Note

    This bucket is different from the one that you set up for the media asset outputs of your job. For information about that bucket, see Step 2: Create storage for files, which is a sub-topic of the Getting started chapter of this guide.

  • Set up an Amazon EC2 instance and an Amazon Lambda proxy in an Amazon VPC. Then install the SID/TIC server software and licence from Nielsen.

  • Use Amazon API Gateway to set up a gateway to manage requests and responses between MediaConvert and your Nielsen SID/TIC server.

    This should result in a REST endpoint that you provide for the setting TIC server REST endpoint (ticServerUrl) when you set up your job.

  • Use Amazon Identity and Access Management (IAM) to manage access and authentication between MediaConvert, your API gateway, and your SID/TIC server.

    Note

    The roles and access you set up for this data sharing is different from the IAM permissions you set up to allow MediaConvert to access your input and output Amazon S3 buckets. For information about that setup, see Step 5: Set up IAM permissions , which is a sub-topic of the Getting started chapter of this guide.