Launch your first machine
This page takes you from nothing to a shell on a machine that stops itself when nobody is using it.
1. Sign in
Section titled “1. Sign in”Install the CLI and sign in. If you have not done that yet, get started with the CLI first.
2. Connect a cloud account
Section titled “2. Connect a cloud account”Machines are created in your account, not ours. Deployport assumes a role you write, and you can revoke that role whenever you like.
deployport machinery cloud connect awsThe command prints the role to create in your own account. Paste it there, copy the role ARN your cloud console gives back, and finish the connection with it:
deployport machinery cloud connect aws --role-arn <the role ARN>For Google Cloud the provider is gcp and the connection finishes with --project <project id>. Connect a cloud account has the whole flow.
3. Make a factory
Section titled “3. Make a factory”A factory is what a machine is built from. It carries the cloud account, the sizes it permits, the firewall rules and the setup steps.
deployport machinery machine-factories create --title "Dev" --cloud-account <cloud-account-id>4. Launch it
Section titled “4. Launch it”deployport machinery machines create --factory <factory-name>The command prints the machine id. Add --name to give it a name you will recognize in a list.
5. Open a shell
Section titled “5. Open a shell”deployport machinery ssh <machine-id>A stopped machine starts when you connect, so you do not have to check whether it is running first.
See what you have
Section titled “See what you have”deployport machinery machines listWhat happens when you walk away
Section titled “What happens when you walk away”A machine stops itself when it has been idle, and the bill stops with it. It warns you first, so you get a chance to keep it running:
deployport machinery machines autostop suppress <machine-id> 4hAn ssh session counts as use, so a machine you are working on is never stopped under you. Let a machine stop itself explains the timings.
Stop it, or destroy it
Section titled “Stop it, or destroy it”A stop keeps the disk and the next start brings the machine back:
deployport machinery machines stop <machine-id>deployport machinery machines start <machine-id>A terminate destroys the cloud instance. Nothing brings it back:
deployport machinery machines terminate <machine-id>