Migrate from AMS CLI
Overview
The AMS CLI continues to work. The AGS CLI covers AMS fleet and image management, including server image upload with ags ams upload.
Sign in
See Install and sign in for the two login modes.
The AMS CLI accepted a client ID and client secret as per-command flags (-c and -s). With the AGS CLI you sign in once per session and subsequent commands use the stored token.
Command mapping
| AMS CLI | AGS CLI | Notes |
|---|---|---|
ams upload -H -c -s -n -p -e | ags ams upload | Archives the build directory, uploads it, and registers the image in one command. Example: ags ams upload --path ./build --executable server --image-name my-server-image. Requires the AMS:UPLOAD permission with Create and Update, entered un-namespaced. This is a different permission from AMS:IMAGE (used by ags ams images), so being able to list images is not enough. |
Fleet, image, and server management are also available as standard commands under ags ams: account, artifacts, dedicated-servers, dev-server-config, fleet-commander, fleets, images, info, qos, and watchdogs. See the Commands page for the full list.
The AMS Simulator (a separate binary for local dedicated server testing) has no counterpart in the AGS CLI. Continue using the AMS Simulator binary downloaded from Admin Portal > AMS > Download Resource.