AMP Information

  • Last Post 3 weeks ago
Nick posted this 3 weeks ago

To whom it my concern,

Where can I find more documentation on the AMP API?

I'm very interested in learning how to create custom modules for games not supported and would like to read practical examples of deploying pre-configured instances for game hosting providers.

Let me know if anyone can help me find this information!


Order By: Standard | Newest | Votes
Mike posted this 3 weeks ago

The JSON API (required for things like using ADS to deploy instances for you) can be reached by just appending /API to your panel URL.

The module API is a little more in depth:

Nick posted this 3 weeks ago

I haven't had a chance to read all of the APIs functions & abilities so I'll ask you;

AMP Instance Manager - Can it act as a single user-point for administrators, and instead of creating 'local' server(s), configure agents like a remote-VPS, or remote-dedicated machines to target and install the servers on?

Also if you would, help me out with this hypothetical.

a. If I was a game server provider, and the answer to my above question was no. I would need to install the AMP Instance Manager on each of my dedicated machines, then use my own software to keep track of my machines and resource availability? If a user purchased a server from me (Minecraft), I could query my own software and determine which of my dedicated machines has the most available resources, then send a API request to the AMP Instance Manager running on that particular machine to create an instance, configure user name, password, IP, ram, port, etc? & Ensure that those values are locked so the user can't adjust them.

Mike posted this 3 weeks ago

For each server you want to deploy AMP on you need to create an ADS (Application Deployment Service) instance. ADS communicates with other ADS instances to create actual game server instances in different places (referred to as Controller/Target mode)

The AMP Instance Manager 'desktop' app is being retired and the setup process is being changed to just create an ADS instance from where everything is managed. If you create a controller instance then everything is done from there. It handles all of the network resource provisioning for you automatically.

AMP isn't quite ready for commercial usage like this yet (see the roadmap) as the permissions system is still in the process of being centralised to allow for things to be sufficiently locked down. You can do this right now but it's a bit fiddly and involves making huge numbers of API calls to configure the permissions in a sane way.