## Settings for instance

## The module that this instance is based on has been retired. You should re-create this instance as soon as possible to continue using this application in AMP.
Support Article: Retiring AMP legacy modules

toggle_on Instance Information
deployed_code Container Settings
lan Network and Ports
database Storage

#### Friendly Name

#### Display Group

#### Description

#### Welcome Message

#### Start on Boot

Whether this instance should start automatically when the system boots.

#### Suspended

Suspended instances cannot be accessed and prompt the user to contact the administrator.

#### Run in Container

Instances in containers are isolated from other instances and the rest of the system, at the expense of a minor performance impact.

#### Container Image

For advanced users only - which specific Docker image the instance should be started with. Note that only images specifically designed for use with AMP can be used here.

#### Container Packages

Add Package
Extra Debian packages to be installed in this instances container upon initialization.

#### Container CPUs

The maximum number of CPU shares that this container may access using `--cpus`. Roughly matches up with the number of CPU cores/threads the container can use but non-multithreaded applications may not see performance increases from higher values. Setting to 0 results in no limit.

#### CPU Set

Pin this container to specific CPU cores using `--cpuset-cpus`. Accepts a range (0-3), a list (0,1,3), or a combination (0-1,3). Leave blank for no pinning.

#### Container Memory Policy

If the memory policy is 'reserve', how much memory should be set aside for this container as a minimum. If the memory policy is 'restrict', how much memory and swap space this container may use maximum.

#### Container Memory

Set to 0 for unlimited.

#### Container Swap Space

Setting to 0 results in no swap space. Set to -1 for unlimited.

#### Exclude From Firewall

If set, this instance will not have firewall rules generated for it.

#### Use Host-Mode Networking

Binds the containers network directly to the host. Allows servers inside the container to be aware of connecting users real IP addresses.

#### Application IP Binding

##### This instance is not multi-IP aware and cannot be rebound.

The primary address used to listen for incomming connections. 0.0.0.0 listens on all available addresses.

#### Advertised Connection Address

The address shown to players to connect to this server (host, or host:port for NAT/reverse-proxy port remaps). Leave blank to use the global default, or the address used to reach AMP.

#### Append Port to Advertised Address

Append the game port to the Advertised Connection Address (e.g. play.example.com:25565 or 1.2.3.4:25565). Uncheck if a reverse proxy / SRV record routes the port for you (players connect with just the host). Ignored when the advertised address already includes a port.

Description | Port Number | Protocol |
|  |  | delete
#### Add Custom Port
|  |  | add_circle

#### Container Path Bindings

When running inside a container, these directories will be passed through to the running instance. It's important to make sure that the host user running AMP has full read/write access to any added directories. This setting does not do anything within instances that don't run in containers.

Physical Path | Virtual Path | Read Only |