Skip to main content
Cloud connections are a preview. They stay off until the runtime setting cloud.connections_enabled is on. Cloud resources cost money: every cloud plan shows a cost estimate and needs an approval before it applies.
Levelrail never holds your admin login. It keeps one credential that can only manage compute, networking and buckets inside one compartment made for it.

Pick an option

Safest first. Neither Oracle Cloud nor AWS offers a “sign in with” consent screen for managing resources, so there is no sign in button here. Root or tenancy admin credentials are never accepted, and the tenancy root is never accepted as the compartment.

Option 1: guided bootstrap

Sign in once with a browser session, then review the plan. The default is a dry run: it only reads your session and prints every command it would run.
Run it when the plan looks right:
What it does, in order:
  1. Creates the compartment levelrail under the tenancy root (or --parent-compartment).
  2. Creates the group and the user levelrail-<name>, turns off the console password and every credential type except API keys, and adds the user to the group.
  3. Creates the policy levelrail-<name> with statements for that one compartment. It never grants anything tenancy wide and never grants IAM rights.
  4. Makes an RSA key pair on your machine, uploads only the public half and reads the fingerprint.
  5. Sends tenancy, region, compartment, user, fingerprint and the private key to Levelrail over the authenticated API (https, or plain http only to this machine), then wipes the local copy.
If a step fails it stops, lists what was already created and prints the oci commands to remove it. Nothing is deleted for you. If your session expired it tells you to run oci session authenticate again. Flags: --profile (default DEFAULT), --region, --tenancy, --compartment-name (default levelrail), --parent-compartment, --name, --dry-run, --yes.

Option 2: paste a scoped credential

Create a group and an API only user, then apply this policy in the parent compartment. Replace the group name and compartment OCID.
Then paste. The key comes from an environment variable or stdin, never from a flag. It is checked offline (OCID shapes, region, key size, fingerprint) before anything is sent.

After connecting

Every cloud plan shows a cost estimate and waits for approval before it applies. See How it works.
Last modified on November 17, 2026