This guide describes the geographic availability of the Transcoder API. Google Cloud uses independent regions to define the geographic location of physical computing resources. Each region is divided into multiple zones. For more information, see Regions and zones on the Geography, regions, and zones page.

This guide also describes issues to consider when planning how to manage the locations of your media assets, jobs, and job templates.

Before you begin

Make sure you are familiar with the introductory concepts and terminology in the Transcoder API. For more information, see the technical Overview.

Managing media asset location

To submit media assets for a transcoding job, you first upload them to Cloud Storage. After a job completes, the Transcoder API saves the results back to Cloud Storage. For the best performance results, make sure you create Transcoder API jobs as close as possible to the location where the data is stored in Cloud Storage. For more information on optimizing the location of data stored in Cloud Storage and a list of available locations, see Bucket locations.

To configure the location of media in Cloud Storage, you specify the uri field for the input assets and output destination fields when configuring a job for the Transcoder API.

To learn how to move data stored in Cloud Storage between bucket locations, see Copying, renaming, and moving objects.

Managing job location

When you create a job, you specify a regional location to process it with the Transcoder API. A regional location is a specific geographic place, such as Tokyo. For more information, see Regional resources on the Geography, regions, and zones page.

After you create a job, you can't change its location.

Managing job template location

Optionally, when you create a job, you can specify a job template to populate the configuration settings for the job. The Transcoder API provides preset job templates in all the regions that the API is available in. You can also create user-defined job templates for each region the Transcoder API is available in.

To specify a user-defined job template for a job in a region, make sure it is available in that region. To verify the existence of a template in a region, you can list all the templates in a location or send a request to get the details of a specific template.

Available regions

The Transcoder API supports a subset of the full list of Google Cloud locations.

The Transcoder API is available in the following regions:

Regional locations

Region name Region description
us-central1 Iowa, USA
us-west1 Oregon, USA
us-east1 South Carolina, USA
southamerica-east1 São Paulo, Brazil
asia-east1 Taiwan
europe-west1 Belgium

Location considerations

When you choose a location to create jobs, you might want to consider factors such as the following:

  • Latency
  • Cost
  • Resiliency
  • Co-location with other Google Cloud services, such as Cloud Storage

When choosing a location for your jobs and media assets, consider doing the following:

  • When importing data to Cloud Storage, co-locate the bucket for your media assets and your external data source.

  • Co-locate your source media assets in Cloud Storage with the location of Transcoder API jobs.

  • When choosing the output destination for a job, co-locate your output media assets in Cloud Storage and your external clients.

What's next