This document explains how to set up Bitmovin Encoding on Google Cloud Platform (GCP) infrastructure so that the Bitmovin platform can run encoders using the Google Compute Engine (GCE) API.

The instructions in this document for the REST API Services apply to live encoding and file-based encoding. For a complete list of formats and input types, see the Bitmovin website.

Prerequisites

🚧

Activation required

This feature requires a commercial agreement and needs to be specifically activated for a Bitmovin account, it is not available by default. You will not be able to complete the configuration below without this activation.

• A Bitmovin account enabled for usage of Cloud Connect
  • If you want to use Cloud Connect with a sub organization, this sub organization must be enabled for usage of Cloud Connect
• A Google Cloud account
• A Google Cloud project with enabled Compute Engine API
  • It is recommended to have a dedicated project for encoding with Bitmovin

Configure your GCP account

In this section, you will create a separate resource group that will be used by the Bitmovin platform when interacting with your GCP infrastructure. Also, we will create the appropriate infrastructure setup to enable Encoding jobs.

📘

Optional: Configure with Terraform

If you prefer infrastructure-as-code, Bitmovin AWS Cloud Connect is also configurable using Terraform scripts: Bitmovin Terraform Cloud Connect

Create a service account

The service account is used by the Bitmovin platform to get access to your GCP account and create compute resources to run parts of the the encoding service within it, including starting and stopping GCE instances.

1. Open the "IAM & Admin > Service Accounts" settings in the Google Cloud console: https://console.cloud.google.com/iam-admin/serviceaccounts
2. Select the project you want to use for encoding with Bitmovin, then click the "Create service account" button
3. In "Service account details" (Step 1), provide a "Service account ID", then click the "Create and continue" button

4. In "Grant this service account access to project" (Step 2), select the "Compute Instance Admin (v1)" role, then click the "Continue" button

📘

Optional: Additional Permissions for reserving Static IP Addresses

If you are planning to use the Static IP Addresses Feature of the Encoder you also need to add the "Compute Network Admin" role.

5. In "Grant users access to this service account" (Step 3), click the "Done" button
6. Click on the "Email" or your newly created service account
7. In the "Keys" tab, select "Add key" and click "Create new key"
8. Select "JSON" and click the "Create" button
   1. This will download a JSON private key file containing your private key and other information, required in later steps

Configure a VPC (optional)

By default, the Bitmovin platform assumes that you are running instances in an auto mode VPC named "default".

If you prefer creating a specific custom mode VPC for your project, make a note of the VPC name and subnet(s) that you create. Follow the Google "Create and manage VPC networks" docs for your custom configuration.

• Custom VPCs are supported from Encoder v2.51.0 and above

Configure and create firewall rules

Firewall rules enable network access into your VPC and to the GCP infrastructure in particular.

1. Open the "Network Security > Firewall policies" settings in the Google Cloud console: https://console.cloud.google.com/networking/firewalls/list
2. Under the "VPC firewall rules" section, make sure the existing firewall rules are configured according to the following tables by clicking on the respective role, then click the "Edit" button:

3. Additionally, create new rules for each of the following tables by clicking the "Create firewall rule" button:

📘

Live encodings

Additional firewall rules are required if you are encoding live streams transported over RTMP, SRT or Zixi.

Additional inbound rules for RTMP live streams

Additional inbound rules for SRT live streams

Additional inbound rules for Zixi live streams

Configure your Bitmovin account

Before you continue, make sure you have collected the following information from your GCP account:

• From the JSON private key file
  • Project ID
  • Client email
  • Private key
• From your (custom) VPC: https://console.cloud.google.com/networking/networks/list
  • Network ID- requires the full GCP network path e.g. /global/networks/your-custom-vpc
  • Subnet ID - requires the full GCP subnet path e.g. /regions/your-region/subnetworks/your-custom-subnet

Link your GCP project

To enable your Bitmovin account to run encodings in your GCP project, you need to link it with Infrastructure and Region Settings objects.

1. Open the Bitmovin Dashboard: https://dashboard.bitmovin.com/
2. Go to "VOD/LIVE Encoding > Cloud Connect"
3. Click the "Add infrastructure account" button, select the "Google Cloud Platform" option, click the "Next" button
4. Provide a "Name" of your choice for your project, fill in the Service Account Email, Project ID and Private Key, click the "Next" button
   1. Note: You can also upload/select the JSON private key file, which you created earlier via the GCP console or the Terraform script.
5. Select the appropriate "Cloud Region", fill in the Network ID and Subnet ID, click the "Next" button

Getting access to MIs

The Bitmovin platform uses private machine images (MIs) from which to create encoder instances in GCE. After you have created all infrastructure objects in the account (or accounts) that you need, ask your Bitmovin technical contact to whitelist access to the MIs for your specific GCP service account.

You will need to provide:

• the Client email of your GCP service account, and
• the Organization ID of your Bitmovin account (or email address)

Run encoding jobs in GCP

After configuration has been completed, you will be able to run encoding jobs in your own GCP project. To do so, use the Bitmovin API client SDKs to submit encoding jobs, in the same way as you would do for encodings running in the Bitmovin Managed Cloud service. The only difference is that you need to specify the new infrastructure instead of public cloud regions.

Here is a Python snippet demonstrating how to link your encoding to your infrastructure.

    # ID of the Infrastructure object
    infra_id = ‘<infrastructure_id>’ 
    
    # GCP region of the GCP-connect setup
    infra_region = CloudRegion.GOOGLE_EUROPE_WEST_1
    infrastructure = InfrastructureSettings(infrastructure_id=infra_id, 
                            cloud_region=infra_region)
    
    encoding = Encoding(name='gcp connect encoding',
        cloud_region=CloudRegion.EXTERNAL,
        infrastructure=infrastructure,
        encoder_version='STABLE')

Sub Organizations

If you have set up your infrastructure in a sub organization, you must tell the Bitmovin API that you want to run the encoding in that sub organization. Thus, in addition to the code snippet above, make sure to set the tenant_org_id alongside the api_key in the bitmovin_api object:

    # ID of the sub organisation you added the infrastructure to
    organisation_id = '<sub_organisation_id>'

    bitmovin_api = BitmovinApi(api_key=config_provider.get_bitmovin_api_key(), 
                       tenant_org_id=organisation_id,
                       logger=BitmovinApiLogger())

Resource Quotas

If you want to run several encodings in parallel, then the default quota limits may not be sufficient. In that case, you will have to request limit increases for the following quotas in your regions, through the Quotas page in the Cloud Console.

For the limits to request we will be using these variables:

Using the variables above, please request the following limits:

The values above assume 8-core instances. If you believe that your use case requires instances with a different number of cores, this number may need to be increased after discussion with your Bitmovin team.

The maximum number of instances needed depends on the maximum number of parallel encodings multiplied by the maximum number of instances for one encoding. The number of instances used by one encoding varies depending on the input file size and the number and data rate of the encoder representations.

Generally, it is a good idea to multiply the expected limit calculated for your current situation by 2, to have some margin in case you need to ramp up.