Connect from the Atlas CLI (original) (raw)

When you connect to an existing Atlas account from the Atlas CLI, you can authenticate with one of the following commands:

Command Authentication Method Use Case
atlas auth login Atlas login credentials and an authentication token Best for non-programmatic use
atlas config init API keys Best for programmatic use

Important

API keys are stored in plaintext in the Atlas CLI configuration file. Your API keys are like passwords. Ensure that you secure the configuration file appropriately.

To create a new Atlas account or onboard an existing account that doesn't have any clusters, see Get Started with Atlas.

Select a use case below to learn more about the available connection options:

Use the atlas auth login command to authenticate with your Atlaslogin credentials and a one-time authentication token. atlas auth login requires manual login and verification of an authentication token, which is valid for 12 hours. API keys are optional when connecting with atlas auth login.

After you run atlas auth login, you can:

You must configure API keys to authenticate with this command.

When you run theatlas config init command, the Atlas CLI prompts you to provide your API keys and automatically creates a profile that stores the API keys. atlas config init is best for programmatic use because it doesn't require manual login or token verification.

When you use connect with atlas config init, you can:

Select a use case and follow the steps to connect from the Atlas CLI with minimum required settings.

Select a use case and follow the procedure to quickly connect from the Atlas CLI.

Run the atlas auth login command in your terminal.

The command opens a browser window and returns a one-time activation code. This code expires after 10 minutes.

If you aren't signed in already, sign into your Atlas account in the browser.

Paste your activation code into the browser and clickConfirm Authorization.

Return to the terminal. If you connect successfully, you see a message:

Successfully logged in as {Your Email Address}.

Accept the default profile configuration by pressing Enter if the following options display:

Important

If you previously set up any profiles with API keys for MongoCLI, your profiles migrate automatically. Some migrated profiles might cause Atlas CLI commands to fail when authenticating with atlas auth login. The following message displays when you run atlas auth login if there is a conflict:


There was an error fetching your organizations: Global user is

from outside access listed subnets.

To fix the conflict, open the configuration file, remove the default profile, and run atlas auth login again.

When you run Atlas CLI commands for the duration of your Atlas CLI session, specify your Project ID and Org ID using the --projectId and --orgId flags.

Example


atlas alerts list --projectId 60b3c81153cf986293e2608b

Run the atlas config init command in your terminal.

Enter your public and private keys when prompted.

Accept the remaining default profile options by pressing Enterwhen the following options display:

When you run Atlas CLI commands for the duration of your Atlas CLI session, specify your Project ID and Org ID using the --projectId and --orgId flags.

Example


atlas alerts list --projectId 60b3c81153cf986293e2608b

Start using theAtlas CLI commands.

To save connection settings by modifying the default profile or create a different profile, see Save Connection Settings.