Vantage Cloud Support

Silver Support is included with Vantage Cloud.
Please see the Enterprise Support Service Guide for coverage details.

Frequently Asked Questions

Vantage natively supports media transport with AWS S3, FTP, SFTP, HTTP, and Aspera protocols. Vantage will monitor S3 buckets and FTP locations as watch folders.

The native Vantage S3 bucket interface is optimized for moving media files in and out of S3 object storage. Unlike many third party interfaces, Vantage has configurable retry and timeout limits and validates transfers for completeness, assuring that files are ingested in their entirety. Therefore, Vantage is ideally suited for processing content libraries that are stored at S3.

Vantage Cloud Subscriptions are implemented with Vantage 6.3. All native Vantage capability and functionality is identical. Your transcode and analysis settings can run unchanged and produce identical results. Optional third party integrations are not accessible at AWS if AMIs are not provided by the manufacturer. Where AMIs do exist, they can be launched manually into the Virtual Private Cloud that protects your Vantage Virtual Domain.

Amazon implements GPU acceleration with Nvidia Kepler GK104 GPUs. The GK104 has 1536 GPU cores and is rated at 3 Tera flops. The GPU servers at AWS have less CPU power than the Telestream Lightspeed K80 Servers in the Lightspeed servers and therefore, may require modifications to Lightspeed GPU accelerated workflows. GPUs are available in all AWS regions.

Yes, AWS reserved instance pricing is fully supported with Vantage Cloud Manager. This is an agreement between you and AWS. The AWS instance types that are accessible with Vantage Cloud Manager are identified within the GUI. AWS will bill you for your usage at the price that you have negotiated. There is nothing that you need to change within your Vantage Cloud Subscription or Vantage Cloud Manager.

The Vantage API is accessible on port 8677 (TCP) and 8676 (HTTP) of the public IP address of the Virtual Domain Server. Access to the API must be from the public IP address that was used in the creation of the Vantage Virtual Domain.

Vantage Virtual Domain security is maintained at three levels:

  • The Vantage Cloud Manager service is hosted on a server that is running within a secure environment within your enterprise. Standard best practice for protecting against intrusions and attacks of your enterprise network, also protect the Vantage Cloud Manager.
  • AWS account credentials protect access to your account at AWS. Sharing of exported Virtual Domain definitions must be done securely and never shared with anyone outside of your enterprise.
  • Only the system that creates a Vantage Virtual Domain can connect to it. Vantage Virtual Domains enforce a one-to-one relationship between Vantage Virtual Domains and the IP address of the Vantage Cloud Manager system that created them. Virtual Domains reject connection attempts of unrecognized IP address. Therefore, Vantage Cloud Management system should be configured with secure remote access if remote accessibility to the virtual domains is desired or required.

Our support team will access your Vantage Virtual Domains through your Vantage Cloud Manager Server. They will need access through a remote control program to do so. Permission must be granted by a member of your organization who is directly involved with the support case.

Comparisons are difficult to generalize because performance is dependent upon the selection of server, communication and storage networks both on premise and at AWS and whether media is originating from on-premise storage or currently resides with S3.

Comparison testing has been provided between an on-premise Lightspeed Server and the GPU AWS instance.


  • Nine ProRes sources submitted simultaneously.
  • Multiscreen transcode of 5 layers
  • File size ranged from 1.7 to 3.1 GB
  • Files are stored in S3 and localized to both servers

The results

  • Transcode time = 1.3X longer at AWS
  • Transfer time = 7X longer to on-premise location
  • Total time = 1.2X longer on-premise


  • On-premise transcoding is faster
  • On-premise GPUs have more capacity and therefore less queueing time
  • Best performance is achieved by placing the CPUs near the data store.

Yes, the AMIs can be launched manually through the AWS console and integrated into functioning Vantage networks at AWS. Of course, this will take much longer and the automated integration and features of the Vantage Cloud Manager will not be accessible.

  • Snapshots can be taken from local Vantage systems or systems at AWS and imported into new Vantage Virtual Domains.
  • An image of the workflows of running Vantage Domains can be captured and saved as Snapshots in the Vantage Cloud Manager console. Snapshots are referenced when starting a new Vantage Virtual Domain to enable efficient stopping and restarting of Vantage Virtual domains for cost management.