The tables below defines all of the current available global processing regions. We suggest processing your media in the region closest to your source content to ensure fastest transit times. The region parameters are expressed as <region /> in your request. If the region parameter is not specified and the source media location is an Amazon S3 bucket we will process in the same AWS region. (See Automatic Select section below)
<?xml version="1.0"?>
<query>
<userid>[UserID]</userid> <!-- required-->
<userkey>[UserKey]</userkey> <!-- required-->
<action>[Action]</action> <!-- required-->
<source>[FileURL]</source>
<region>[Region]</region>
<format>
<output>[OutputFormat]</output>
<!-- format params -->
</format>
</query>
{
"query": {
"userid": "[UserID]", // required
"userkey": "[UserKey]", // required
"action": "[Action]", // required
"source": "[FileURL]", // required
"region": "[Region]",
"format": {
"output": "[OutputFormat]" // required
// format params
}
}
}
Amazon EC2 Regions
Region | Name |
---|---|
us-east-1 | US (Northern Virginia) |
us-east-2 | US (Ohio) |
us-west-1 | US (Northern California) |
us-west-2 | US (Oregon) |
eu-west-1 | EU (Ireland) |
eu-central-1 | EU (Frankfurt) |
ap-southeast-1 | Asia Pacific (Singapore) |
ap-southeast-2 | Asia Pacific (Sydney) |
sa-east-1 | South America (Sao Paulo) |
ca-central-1 | Canada (Central) |
eu-west-2 | EU (London) |
eu-west-3 | EU (Paris) |
ap-northeast-1 | Asia Pacific (Tokyo) |
ap-northeast-2 | Asia Pacific (Seoul) |
ap-south-1 | Asia Pacific (Mumbai) |
af-south-1 | Africa (Cape Town) |
Azure Regions
Region | Name |
---|---|
az-us-east | Azure US East (Northern Virginia) |
az-us-east-2 | Azure US East 2 (Virginia) |
az-eu-west | Azure Europe (Netherlands) |