The template contained within this repository can be used to deploy a Factorio server to Amazon Web Services (AWS) in minutes. As the solution leverages "Spot Pricing", the server should cost less than a cent an hour to run, and you can even turn it off when you and your friends aren't playing - saving even more money.
- A basic understanding of Amazon Web Services, specifically CloudFormation.
- An AWS Account.
- Basic knowledge of Linux administration (no more than what would be required to just use the
factoriotools/factorioDocker image).
The solution builds upon the factoriotools/factorio Docker image, so generously curated by the folks over at FactorioTools (thank you!).
In a nutshell, the CloudFormation template launches an ephemeral instance which joins itself to an Elastic Container Service (ECS) Cluster. Within this ECS Cluster, an ECS Service is configured to run a Factorio Docker image. The ephemeral instance does not store any saves, mods, Factorio config, data etc. - all of this state is stored on a network file system (Elastic File System - EFS).
The CloudFormation template is configured to launch this ephemeral instance using spot pricing. What is spot pricing you might ask? It's a way to save up to 90% on regular "on demand" pricing in AWS. There are drawbacks however. You're effectively participating in an auction to get a cheap instance. If demand increases and someone else puts in a higher bid than you, your instance will terminate in a matter of minutes.
A few notes on the services we're using...
- EFS - Elastic File System is used to store Factorio config, save games, mods etc. None of this is stored on the server itself, as it may terminate at any time.
- Auto Scaling - An Auto Scaling Group is used to maintain a single instance via spot pricing.
- VPC - The template deploys a very basic VPC, purely for use by the Factorio server. This doesn't cost you a cent.
- Click the above link, you'll need to log into your AWS account if you haven't already.
- Ensure you've selected a suitable AWS Region (closest to you) via the selector at the top right.
- Click Next to proceed through the CloudFormation deployment, provide parameters on the following page. You'll need a Key Pair and your Public IP address if you want to access the instance remotely via SSH (recommended). Refer to the Remote Access section below. There should be no need to touch any other parameters unless you have reason to do so. Continue through the rest of the deployment.
All things going well, your Factorio server should be running in five minutes or so. Wait until CloudFormation reports the stack status as CREATE_COMPLETE. Go to the EC2 dashboard in the AWS console and you should see a Factorio server running. Take note of the public IP address. You should be able to fire up Factorio, and join via this IP address. No need to provide a port number, we're using Factorio's default. Bonus points - Public IP addresses are ugly. Refer to Custom Domain Name within Optional Features for a better solution.
At this point you should really configure remote access as per the below section, so that you can access the server and modify server-settings.json (e.g. add a password, add to the Factorio server browser, whitelist admins etc.).
If you know what you're doing, you might want to SSH onto the Linux instance to see what's going on / debug / make improvements. You might also want to do this to upload your existing save. For security, SSH should be locked down to a known IP address (i.e. you), preventing malicious users from trying to break in (or worse - succeeeding). You'll need to create a Key Pair in AWS, find your public IP address, and then provide both of the parameters in the Remote Access (SSH) Configuration (Optional) section.
Note that this assumes some familiarity with SSH. The Linux instance will have a user ec2-user which you may connect to via SSH. If you want to upload saves, it's easiest to upload them to /home/ec2-user via SCP as the ec2-user user (this is ec2-user's home directory), and then sudo mv these files to the right location in the factorio installation via SSH.
For remote access, you'll need to:
- Create a Key Pair (Services > EC2 > Key Pairs). You'll need to use this to connect to the instance for additional setup.
- Find your public IP address. You'll need this to connect to the instance for additional setup.
If you're creating a new Factorio deployment, provide these parameters when creating the stack. Otherwise, update your existing stack and provide these parameters.
Every time your Factorio server starts it'll have a new public IP address. This can be a pain to keep dishing out to your friends. If you're prepared to register a domain name (maybe you've already got one) and create a Route 53 hosted zone, this problem is easily fixed. You'll need to provide both of the parameters under the DNS Configuration (Optional) section. Whenever your instance is launched, a Lambda function fires off and creates / updates the record of your choosing. This way, you can have a custom domain name such as "factorio.mydomain.com". Note that it may take a few minutes for the new IP to propagate to your friends computers. Have patience. Failing that just go to the EC2 console, and give them the new public IP address of your instance.
Do I need a VPC, or Subnets, or other networking config in AWS?
Nope. The stack creates everything you need.
What if my server is terminated due to my Spot Request being outbid?
Everything is stored on EFS, so don't worry you won't lose anything (well, that's partially true - you might lose up to 5 minutes of gameplay depending on when the server last saved). There is every chance your instance will come back in a few minutes. If not you can either select a different instance type, increase your spot price, or completely disable spot pricing and revert to on demand pricing. All of these options can be performed by updating your CloudFormation stack parameters.
My server keeps getting terminated. I don't like Spot Pricing. Take me back to the good old days.
That's fine; update your CloudFormation stack and set the SpotPrice parameter to an empty value. Voila, you'll now be using On Demand pricing (and paying significantly more).
How do I change my instance type?
Update your CloudFormation stack. Enter a different instance type.
How do I change my spot price limit?
Update your CloudFormation stack. Enter a different limit.
I'm done for the night / week / month / year. How do I turn off my Factorio server?
Update your CloudFormation stack. Change the server state parameter from "Running" to "Stopped".
I'm done with Factorio, how do I delete this server?
Delete the CloudFormation stack. Done.
How can I upgrade the Factorio version?
Update your CloudFormation stack. Set the required tag value for FactorioImageTag. Use the tags specified here: https://hub.docker.com/r/factoriotools/factorio/. Your Factorio server will stop momentarily.
I'm running the "latest" version, and a new version has just been released. How do I update my server?
You can force a redeployment of the service via ECS. Update the service, and select Force new deployment.
How can I change map settings, server settings etc.
You'll need to have remote access to the server (refer to Optional Features). You can make whatever changes you want to the configuration in /opt/factorio/config. Once done, restart the container:
- Go to ECS (Elastic Container Service) in the AWS Console
- Click the factorio cluster
- Tick the factorio service, and select update
- Tick "Force new deployment"
- Click Next 3 times, and finally Update service
I can no longer connect to my instance via SSH?
Your public IP address has probably changed. Check your public IP address and update the stack, providing your new public IP address.
How do I load an existing save?
Be advised that whenever the Factorio container is terminated, it creates a new autosave just prior to terminating. For this reason, restarting the container directly on the host via SSH isn't advised.
In order to load an existing save, follow the below steps:
- Go to ECS (Elastic Container Service) in the AWS Console
- Click the factorio cluster
- Tick the factorio service, and select update
- Set Number of tasks to 0
- Click Next 3 times, and finally Update service
- Access the instance via SSH, placing your save in /opt/factorio/saves.
- Repeat steps above, setting the Number of tasks to 1.
- Scenarios - you can probably figure out a way to get this working... I've just never tried :-).
The two key components that will attract charges are:
- EC2 - If you're using spot pricing (and the m3.medium instance as per the default in the template), I doubt you would attract more than a cent an hour in fees for EC2. Even if you ran it 24 hours a day for a whole month, that's about 7 bucks.
- EFS - Charged per Gigabyte stored per month (GB-Month). Varies based on region, but typically less than 50c per gigabyte. My EFS file system for Factorio is only about 100MB (incl. mods and 5 saves), so maybe 5 cents per month?
AWS do charge for data egress (i.e. data being sent from your Factorio server to clients), but again this should be barely noticeable.
This has been tested in both the Sydney and Oregon AWS regions (verify your AWS region of choice includes m3.medium @ https://aws.amazon.com/ec2/spot/pricing and/or change as needed). Your mileage may vary. If you get stuck, create an issue and myself or someone else may come along and assist.
Be sure to check out factoriotools's repositories on Docker Hub and GitHub. Unless your question is specifically related to the AWS deployment, you may find the information you're after there:
- Docker Hub: https://hub.docker.com/r/factoriotools/factorio/
- GitHub: https://github.com/factoriotools/factorio-docker
It may be because the m3.medium instance is not available in your region. As a result of this, an auto-scaling group gets successfully created - however it never launches an instance. This means the ECS service cannot ever start, as it has nowhere to place the container. I would suggest going to the AWS Console > EC2 > Spot Requests > Pricing History, and find a suitable instance type that's cost effective and has little to no fluctuation in price.
In the below example (Paris), m5.large looks like a good option. Try to create the CloudFormation stack again, changing the InstanceType CloudFormation parameter to m5.large. See: m-chandler#10
Visit the ECS dashboard in the AWS Console.
- Clusters
- Click on the factorio Cluster
- Tick the factorio Service, click Update
- Tick the "Force new deployment" option
- Click Next step (three times)
- Click Update Service
If you SSH onto the server, you can run the following commands for debugging purposes:
sudo docker logs $(docker ps -q --filter ancestor=factoriotools/factorio)- Check Factorio container logs.
DO NOT restart the Factorio docker container via SSH. This will cause ECS to lose track of the container, and effectively kill the restarted container and create a new one. Refer to Restarting the Container above for the right method.
Thanks goes out to FactorioTools (and contributors) for maintaining the Factorio Docker images.