Deploy JetEncode on AWS
Subscribe to the free AWS Marketplace product, launch the x86-64 AMI on EC2, and connect only the S3 locations your jobs need.
JetEncode requires no license key, JetEncode account, email registration, or external payment method. AWS bills the EC2, EBS, S3, data transfer, monitoring, and other resources you use.
Before you start
- Permission to subscribe to AWS Marketplace products and launch EC2 resources.
- A VPC, subnet, security group, EC2 key pair, and an AWS Region that meets your requirements.
- A least-privilege IAM instance role for S3 jobs, a non-sensitive test video, and a cleanup owner.
1. Subscribe and select the AMI
Open the JetEncode listing in AWS Marketplace, accept the free offer, choose the latest version, and continue to the EC2 launch flow. Record the selected version and Region.
Subscribe to the free JetEncode product in AWS Marketplace, then launch its latest AMI version.
Choose the latest JetEncode AMI version shown in the AWS Marketplace listing.
The AWS AMI uses x86-64.
Launch in any Region enabled for the JetEncode Marketplace listing, choosing one that meets your latency, residency, and storage requirements.
2. Choose EC2 and EBS capacity
Start with a current-generation compute-optimized instance with at least 4 vCPUs. The AMI default root volume is suitable for evaluation; increase it when the largest source, outputs, and concurrent /tmp working sets require more space. Benchmark representative jobs before production.
Start with a current-generation compute-optimized instance with at least 4 vCPUs, then size from representative jobs and expected concurrency.
The AWS edition is CPU-only and does not require or use a GPU.
The AMI default root volume is suitable for evaluation. Increase it for the largest expected source, outputs, and concurrent `/tmp` working sets; keep durable media in object storage.
Throughput varies with source media, output settings, storage paths, instance capacity, and active jobs. Benchmark a representative workload before production.
3. Attach Amazon S3 access
Attach an IAM instance role to the EC2 instance. Scope it to the exact input and output buckets or prefixes required by the workload. Do not enter AWS access keys in JetEncode, a job payload, user data, or the AMI.
Use an EC2 instance role for Amazon S3. Scope read access to the input bucket or prefix and write access to the output bucket or prefix; never place AWS access keys in a job payload.
Attach a least-privilege IAM instance role when a job uses Amazon S3. JetEncode must use the role through the AWS default credential provider chain.
4. Restrict the network
Allow SSH only from trusted administrator addresses and allow TCP port 80 only from trusted operators or applications. Put an HTTPS load balancer or reverse proxy in front of JetEncode before crossing an untrusted network.
The browser UI and HTTP API use TCP port 80. Restrict inbound access to trusted operator and application source ranges.
5. Launch and configure JetEncode
Launch the instance with an EC2 key pair, wait for both EC2 status checks, then open http://<instance-address>/. Choose worker, master, or both and set HTTP authentication. No JetEncode license is requested.
Connect with the EC2 key pair selected at launch and the Ubuntu username `ubuntu`.
In the browser UI, choose worker, master, or both and set HTTP authentication. The AWS edition requires no JetEncode license or account.
Complete first-run setup in the browser UI. Protect the UI and HTTP API with the HTTP credentials you set during setup; use the API for production job creation.
6. Verify readiness
Sign in to the UI, then call GET /v1/sysinfo with the same HTTP credentials. EC2 health checks prove the virtual machine is running; this request proves the JetEncode API is responding.
After setup, open the UI on port 80 and confirm GET /v1/sysinfo responds before submitting production jobs.
7. Run and clean up a test job
Use an HTTP or S3 source and an S3 output prefix dedicated to the test. Confirm the output, cancellation path, failure diagnostics, and logs. Then remove test objects and stop or terminate EC2 resources you no longer need.