It is recommened that you create an extra user that is not the 'Administrator' user, but with admin rights to install AMP.
The instance store path specified during setup must have full read/write access. It should not be placed inside "Program Files".
Tested with CentOS 6.x, Ubuntu 12.04 and Debian 7.
A non-root user is required. AMP will not run as root.
Under Windows AMP has no dependencies other than .Net Framework 4.5.1, which is installed as standard on most systems and is fetched automatically by the installer if it is missing.
A user other than Administrator is strongly recommended, but not required. Note however that running the instanace manager as Administrator means that only service instances can be created.
If you are installing the instance manager while running as Administrator, you should create a directory in a location where the 'NETWORK SERVICE' user can have full read and write access.
The first time you start the instance manager you will be prompted to create an instance.
If you intend to create lots of instances, it's recommend that the first instance you create uses the ADS module. This will give you the instance manager as a web interface that you can access remotely.
If after installation you need to change where AMP stores its instances, you can do so by editing the 'InstanceStore' registry entry key at the following path:
sudo yum install glibc.i686 libstdc++.i686 screen tmux socat unzip git wget
sudo apt-get install lib32gcc1 coreutils screen tmux socat unzip git wget
If you are planning to run Minecraft, you'll also need Java 7 or newer installed.
Note that these instructions may differ between distributions. You should check your Linux distributions documentation for more information.
By default AMP runs on port 8080. By default this port will be blocked, so it's necessary to open it if a firewall is installed (which most distributions include as standard)
iptables -A INPUT -p tcp -m tcp --dport 8080 -j ACCEPT /sbin/service iptables save
You will need to repeat the above steps, substituting 8080 for any additional ports used by the chosen game you are installing.
Future versions of AMP will handle this for you.
This is not an optional step. AMP will refuse to start if you try and run it as root.
First you will need to create an extra user to run AMP as. Perform the following as root:
useradd -d /home/AMP -m AMP passwd AMP
You'll then be prompted to specify a password for the new user.You now need to log out of root and login as the new AMP user, do not 'su' to it while logged in as root.
Once you are logged in as the new user, you're now ready to download the AMP instance manager. This is the tool that will help you create the initial AMP instance, and spawn extra instances if you need them.
mkdir ~/AMP cd ~/AMP wget http://cubecoders.com/Downloads/ampinstmgr.zip unzip ampinstmgr.zip rm -i ampinstmgr.zip
You're now ready to run the instance manager.
AMP is split into modules. Each module is responsible for being able to handle different types of application. For example there's one for creating Minecraft servers, another for StarBound, and another for AMPs own instance management.
You can get a list of available modules by running the following command:
If you have a full AMP licence, it's recommended that the first instance you create is the ADS module, this will allow you to create new instances via the web interface.
./ampinstmgr CreateInstance ADS ADSInstance 0.0.0.0 8080 [LicenceKey] [Password] +Core.Login.Username [Username] ./ampinstmgr StartInstance ADSInstance
For McMyAdmin 2 licences, you can create McMyAdmin 3 instances. The Minecraft and McMyAdmin modules are identical except for which licence type they take.
./ampinstmgr CreateInstance McMyAdmin MCMA 0.0.0.0 8080 [LicenceKey] [Password] +Core.Login.Username [Username] ./ampinstmgr StartInstance MCMA
[Password] with your AMP licence key, a username, and a password to login with. It's recommended that you use a relatively simple password during creation, and then change it to a more complex one after logging in.
This will create and start the deployment instance, which you can then log into on port 8080. Depending on your distribution you may have to add a firewall rule for port 8080 TCP. Consult your distributions documentation for information on how best to do this.
Note that if you need to use the instance manager command line again later on, you'll need to run
cd ~/AMP after logging in as the AMP user.
You can get a full list of commands for the AMP instance manager by running: