launch-admin
Provision and start the Admin service.
Syntax
rumi cloud aws launch-admin \
--profile <profile> \
--network <network> \
--key-pair <keypair> \
[options]Options
--profile
-p
AWS profile to use
Required
--region
-r
AWS region
us-east-1
--network
-n
Name of the Rumi network
Required
--key-pair
-k
The network's EC2 key pair
Required
--admin-proxy-server
-a
The admin proxy server (nginx server_name on the bastion)
null
--admin-proxy-port
-b
The admin proxy port the bastion's nginx listens on
0 (no proxy)
--discovery-proxy-server
-c
The discovery proxy server (nginx server_name on the bastion)
null
--discovery-proxy-port
-d
The discovery proxy port the bastion's nginx listens on
0 (no proxy)
--instance-profile
-I
The IAM instance profile (name or ARN) to attach; required (granting the SSM managed policy) when the network's access method is ssm-all
null
--proxy-bastion
-P
The name of the bastion that fronts the admin UI proxy; required in a multi-bastion network, omitted in a single-bastion network
none
Example
Notes
Proxy ports recorded here are opened later for specific source CIDRs with the whitelist command.
The admin server launches from the admin AMI baked for the Rumi Management release the CLI is built on. If that AMI is not available to your account and region (it is not baked yet, or not shared with your account), the CLI launches the newest admin AMI it was built with instead. Either way it prints which AMI it used, and why when it fell back.
See Also
Last updated

