Unfortunately it's not quite as simple as clicking 'GO' and sitting back, waiting for it all to magically show up on the Internet. I'd decided on what I needed at a basic level, so it was time to start thinking about actually building them and deploying them in AWS. Considering just having an EC2 instance creates a default 8GB volume, I've only got 22GB left to play around with - 20 is a nice round number. Remember, I'm trying to stay within the limits of the free tier, so I'm not allowed any more than 30GB of EBS storage at any given time.

Volume Type: gp2 (a.k.a General Purpose SSD).

While that's nice, much like my home solution, I didn't want to mix up my application data with my static media data, so I decided I'd create my own: By default, creating an EC2 instance will automatically create an 8GB EBS volume and assign it as the root partition - quite handy. EBS - The StorageĪ running server isn't really any good if there's no storage assigned to it for my media, so I decided on EBS (Elastic Block Storage) as my solution. I could have used something more powerful but I figured this would be a good starting point. The only instance type I was allowed to use under the free tier was t2.micro so my hands were a bit tied. It also helps that installing Docker is a bit easier as the AWS repositories haven't caught up with Docker's change to Moby/Docker CE. I figured 'when in Rome' and opted for the Amazon-flavoured version of Linux for no reason other than it was the first option in the list. Image: Amazon Linux AMI 2017.03.1 (HVM), SSD Volume Type

There are quite a lot of options made available by Amazon, but I decided on the following: EC2 - The ServerĮC2 (Elastic Compute Cloud) is where the server will be deployed - it's in my eyes the heart of AWS. I tried my best to see what was possible while staying within the confines of the free tier for new AWS accounts.ĪWS is a veritable supermarket of tools, from databases to AI, but in my case all I needed was an EC2 instance and an EBS volume. Once I'd worked out that obvious list of requirements, I immediately signed up for an AWS account and checked out what the free tier would provide for me.

It really only boils down to those two components when it comes to Plex. Some form of storage for the media content.

A running virtual host, preferably Linux.So, here's what I did.įirstly, I had to understand what it was I needed in order to get my solution up and running. Still, I thought to myself if anything else, it'd make an interesting case-study to deploy an EC2 instance and fire up Plex. Netflix is, in my eyes, a world-leader in video delivery, so I figured if they can use AWS to serve their content, why can't I? I mean, sure, they're an international multi-billion dollar powerhouse, and I am but one man.

Plex media scanner location linux