Cloud Forge Launcher

Deployment guide

How to deploy Jellyfin on AWS with Cloud Forge

Deploy Jellyfin on AWS & ALIYUN from the browser. Media server for movies and TV. Includes CloudFormation/ROS templates, port 8096. No cloud credentials stored in browser.

This guide explains how to self-host Jellyfin on AWS with Cloud Forge. Cloud Forge does not host your app; resources are created in your cloud account.

Prerequisites

  • An AWS account with permission to create compute, EIP, and security groups
  • Access to the official AWS console
  • Understanding of: Media server for movies and TV

Step 1: Choose launch settings

Choose AWS, us-east-1, and the application version in Cloud Forge. Select the AWS instance type in the launcher.

Step 2: Continue to CloudFormation

The deploy button opens the official provider console with the template and launch parameters prefilled.

Step 3: Review and create resources

Select VPC, subnet, key-pair, and other account resources, review costs, and confirm creation. Cloud Forge never receives your cloud credentials.

Step 4: Verify

After the stack succeeds, get the application URL from its outputs. Default service port: 8096.

Estimated cost

ItemAWS (est.)Aliyun (est.)
ComputeQuoted by AWS for the selected instanceQuoted by ROS for a region-available instance
Public IPCurrent AWS rateCurrent Alibaba Cloud rate
Service port8096
Marketplace AMIRequired; see the subscribed offerN/A

The catalog and launch service are free. AWS Marketplace software fees and provider resource charges are separate; review the official quote before creation.

AWS vs Aliyun differences

AspectAWSAliyun
Default regionus-east-1cn-hongkong
IaC formatCloudFormationROS
First bootstrapPre-baked hardened AMI; total time varies by appPublic OS typically 8–15 min
Custom domainRoute53 parametersAlidns parameters
HTTPS without domainIP certificateIP certificate

Clean up

Delete the corresponding stack in the CloudFormation console to remove resources created by the template.

Related templates

Open Jellyfin config page