Cloud Accounts connect AWS or Google once

Connect your AWS or Google Cloud account once, and your boxes and buckets there use it. lnk cloud connect connects a cloud account through an adapter, lnk cloud list lists accounts and lnk cloud disconnect removes a connection.

lnk cloud connect aws    # reuses ~/.aws, else asks for an access key
lnk cloud list           # your accounts, and who each signs in as

Connect a cloud account

Connecting makes nothing in the account. The same account and its one sign-in keep your buckets too.

lnk cloud connect aws                                     # reuses ~/.aws, else asks for an access key
lnk cloud connect aws --profile work --region eu-west-2   # another profile of your aws login
lnk cloud connect aws --name aws-work --key-id AKIAEXAMPLE   # an access key, asking for its secret
lnk cloud connect gcp --project my-project --zone europe-west1-b
lnk cloud connect gcp --name gcp-ci --credential-file key.json   # a service account, by its key
lnk cloud list                                            # your accounts, and who each signs in as

Google Cloud

A Google Cloud account uses gcloud's login and project, and signs you in to gcloud first if you aren't. It signs you in once more for buckets, because Google's libraries can't use gcloud's own login. A service account connects by its key instead, which you get from the Google Cloud console under IAM, Service accounts, Keys.

Without the cloud's CLI

connect offers to install it in Link's settings folder, with no administrator rights. If you say no, an AWS account, or a Google Cloud service account connected by its key, still works for buckets but not for boxes. A Google Cloud login can't connect without gcloud.

Accounts from a sign-in

An installed plugin can expose a cloud account from a sign-in it already holds. lnk cloud list and every command using that account discover it automatically, with no connect or saved duplicate. Sign out through the plugin that supplied it to remove that connection.

Disconnect an account

Disconnecting forgets the account and its key, and deletes nothing in it.

lnk cloud disconnect aws-work    # forgets the account and its key, and deletes nothing in it

What waits for it

Its boxes and buckets wait until you connect it again, and lnk bucket backend disconnect forgets its buckets. An access key keeps working until you delete it in the cloud's console.

How it runs

Each cloud's adapter runs as its own program, lnk-aws and lnk-gcp, and the commands exchange typed requests and replies with it (Interface).

Docs

  • Interface: What other programs can rely on from lnk cloud, and where the commands a cloud adapter, lnk-<kind>, answers are