minecraft-spot

This repo contains some python code and a terraform module for the purpose of easily setting up the code and infrastructure to run minecraft (and other games) using spot instances in aws.

The instance can be brought up using an api endpoint, and will automatically tear itself down after the instance is inactive (with no players online) after a certain period of time.

It requires moderate experience with terraform and AWS

Currently only supports FTB modded versions of minecraft.

Supported Games

This project support a fairly modular architecture which means adding new game servers generally is pretty easy. Currently supported games are:

• Minecraft Java Edition
• Minecraft Java Edition with mods (FTB and curse/twitch)
• Factorio

Usage

WARNING: OUT OF DATE - NEEDS TO BE UPDATED FOR LATEST REFACTOR The easiest way to get going is to add this as a terraform module in your aws terraform infrastructure.

Below is an example of what this might look like:

module "minecraft-spot" {
  source = "github.com/Lemmons/minecraft-spot//terraform?ref=1.1"

  username = "<your desired login username>"
  pub_ssh_key = "<your public ssh key for logging in>"

  hosted_zone_id = "<your route53 hosted zone>"
  api_subdomain= "api"
  minecraft_subdomain= "minecraft"

  aws_region = "us-west-2"

  ftb_modpack_version = "https://www.feed-the-beast.com/projects/ftb-presents-direwolf20-1-12/files/2541246"

  spot_price = "0.035"
  instance_type = "m5.large"

  public_subnets = "<a list of public subnet ids in your infra>"

  bucket_name = "my-minecraft-data"
  api_passphrase = "something-clever"

  vpc_id = "<the vpc_id containing the above subnets>"

  auth_audience = "https://api.mysite.com"
  auth_jwks_uri = "https://mysite.auth0.com/.well-known/jwks.json"
  auth_token_issuer = "https://mysite.auth0.com/"
}

output "webapp-distribution-id" {
  value = "${module.minecraft-spot.webapp-distribution-id}"
}

Once the module has been applied and you have waited a few minutes for everything to stabilize, you can go to the route https://api.<your_domain>/minecraft/start to start the minecraft instance. The first run it might take 10-20 minutes to load, but subsequent start should only take around 5 mins. Once it's up and running, you can shutdown the server using https://api.<your_domain>/minecraft/stop, or the server will shutdown on it's own after 30 mins of inactivity (no users connected to the minecraft server).

Note: Since authentication has been added, to access the apis you will need to include proper auth headers. Examples of this can be found in the Auth0 docs referenced below.

Authentication

To setup authentication you will need to create an account with Auth0. You might be able to use another OAuth provider, but this is untested. You can follow the general steps for getting auth working using these Auth0 docs, but can skip any of the steps involving AWS. Instead, just set the auth_token_issuer, auth_jwks_uri and auth_audience terraform variables and you should be up and working. You will still need to setup Auth0 with proper scopes and hooks, which is beyond the scope of this document.

Webapp

This repo includes a control webapp which should be deployed to s3/cloudfront. The bucket is created for you as part of the terraform run, by default at app.<your_domain>.

There is a some amount of customization needed to the webapp to get it setup for your server:

Customization

1. Install docker if you don't alreay have it
2. Clone this repo
3. Copy webapp/src/config.js.example to webapp/src/config.js
4. Edit webapp/src/config.js, filling in the {AUTH_DOMAIN}, {CLIENT_ID}, {APP_DOMAIN}, and {API_FQDN}
5. AUTH_DOMAIN is the domain name of the authentication token issuer. In the example terraform config above this is mysite.auth0.com
6. CLIENT_ID is the client id of your Auth0 application which you setup above.
7. APP_DOMAIN is the domain your webapp is deployed at: app.<your_domain> by default
8. API_DOMAIN is the domain your api is deployed at: api.<your_domain> by default

You should also ensure that the callbackUrl in the config is also listed in the "Allowed Callback URLs" section of your Auth0 application.

After completing the above, you can build and deploy your webapp.

Build

Building simply requires running make build-content from the webapp/ directory.

Deploy

To deploy, from the webapp/ directory run ./deploy.sh app.<your_domain> <webapp-distribution-id> where <webapp-distribution-id> will be output by your terraform apply if you include the output as show in the above example.

Testing

You can run locally with make run. This will bring up a development webserver at http://localhost on your machine. You can use this to test changes as needed. Keep in mind you will need to modify the callbackUrl in webapp/src/config.js to point to http://localhost/callback to fully work.

Upgrading modpack version

To upgrade the version of the FTB modpack running, simply update the ftb_modpack_version and apply your new changes. If the server is running when you do this, you will have to shut it down fully, using the Stop Server button in the UI. Once the server is stopped and your terraform change has been applied, you can start the server again, and it will be upgraded.

Troubleshooting

You can ssh into your instance using your username and ssh key provided in the module config. Depending on how far through it's start it got, you might be able to ssh to the instance using minecraft.<your_domain>. If that doesn't work, you will have to get the instance's public ip address from the aws console or CLI.

Additionally you can look at the cloudwatch logs for the lambdas running for potential issues.

Future plans

• Enhance status page:
  • latest backup time
  • start backup command
  • minecraft server address:port
  • players online
  • modpack version info
  • allow upgrade of modpack (text field to input modpack url, button to set the REMOVE_OLD_MODS="TRUE" flag?)
• Add back in option to use api password instead of Auth0