AMP 2.4 is a few months away, but we wanted to share with you all some of the cool new features that we’re working on.
Once these start making their way into AMP, we shall dub the release 2.4. Not all of the features below will be included in 2.4’s initial release and will be added over time.
Right now the Generic module can only accommodate a maximum of 3 ports. We’re working on changing this mechanism entirely so it can be any number of ports as needed, including the ability to have offset ports (where it is guarenteed that two ports have a fixed relationship to each other) and range ports (where it guarenteed that a range of ports are in a single group without gaps).
You’ll be able to create arbitrary groups for your instances, even across different machines so you can organise them in a way that makes sense for you - and quickly switch between group and host most.
We’ll also be introducing new ‘views’ to the instances screen to view instances as a list, smaller grid, etc.
You’ll be able to configure multiple datastore locations on the same machine, and move existing instances between them. As well as track your overall storage utilisation per-datastore and per-instance.
You’ll be able to have AMP automatically store your backups in S3 cloud storage. It can be used in a couple of ways. Either as simply a ‘redundant copy’ - or as a tiering system, only keeping your most recent backups locally while older ones remain remote as an archive and only downloaded when needed.
While you might want to take a backup every day, you don’t necessarily want to keep every single daily backup. Period tiering is a smarter way to use storage space by keeping a higher frequency of backups closer to the present, and dropping it off over time. For example, within the last week you might keep daily backups - but from 1 week to 1 month you might only keep one backup per week, and after that once per month up to 3 months.
You’ll be able to browse the Steam Workshop to download mods and addons for the current game server. We also plan to give AMP more tools to manage Workshop content so it can put it in the correct place for you automatically.
The following features are also planned for users of AMP Network and Enterprise Editions:
We hope to be able to offer logins and authentication via social login providers such Discord, Steam, Google and a few others. Admins will create a user in the backend and be given an invitation link to give to the new user, who will then link their accounts.
AMP will be getting support for a handful of commonly used databases (namely MariaDB, MongoDB and Redis). These are going to be part of a separate section within AMP called ‘Service Instances’.
Service instances are for services that support other applications rather than being user-facing applications in their own right in the way game servers are. So this will be especially useful for game servers that require a database to store their data.
Initially we expect this feature to only be available on Linux due to its dependency on Docker, as Windows Server does not support WSL2 and requires Hyper-V instead (which won’t work in some types of VMs).
Right now AMPs firewall handling consists pretty purely of ports being open or closed, but sometimes you want to do things like only allowing a certain host to access a service. Example of this might be with Minecraft proxies where the individual servers should only be accessible via the proxy and nothing else. This will also be useful in combination with service instances.